I made some more back-end changes here, but these you might actually be able<\/p>\n
to see. I am laying the groundwork for an experimental [[content management|CMS]]<\/p>\n
of my own for use in our projects. I am a long way from having time to implement<\/p>\n
it, but I have been having some good luck prototyping some of the features with<\/p>\n
the stuff we are using here. <\/p>\n
This phase of the test is looking at simple macro expansion like the stuff<\/p>\n
they use at Everything2. In this type of system a special set of markup triggers<\/p>\n
engine features. In the case of Everything2 they use [ and ] to denote a lookup<\/p>\n
phrase. So if you say [frog] in an entry it turns into a link looking up frogs.<\/p>\n
This type of markup has gone a long way to making the interlinking of entries<\/p>\n
over at [[E2]].<\/p>\n
Anyway, I have decided here to use a double [[ ]] to mark my<\/p>\n
custom entries. So far it is running right along and I have a number of them set<\/p>\n
up. For instance [[Girl2]] will result in this: Girl2. The basic<\/p>\n
concept of what I am working on is a topic for another time, but it is worth<\/p>\n
noting here that it is intended to allow a database of replacement entries like<\/p>\n
the one for Girl2 and also to provide a search function for entries that<\/p>\n
might have no obvious links.<\/p>\n
For the moment, [[E2]] is providing my source of fallback information. If I<\/p>\n
use a term the system doesn’t know [[don’t panic]], it will try and find <\/p>\n
something<\/b><\/i> to link to. <\/i>Eventually it will search my local <\/p>\n
information and provide fallback searches to a number of sources. Remember, this<\/p>\n
is just a prototyping experiment, not even a full prototype.<\/p>\n
A short list of software related to this entry<\/u>:<\/p>\n