When I started on this road over two years ago
, Mouser told me I would go insane
, but would I listen? Nah...
And now my wife needs a nice, clean business site
too, so as the purpose of my pursuit doubled, so did the pace of my head-first launch into cuckoo-land. Now, a sadder and a wiser idiot, at least I've begun to know what it is that I'm looking for. Here;s my WANTED notice, plastered to a telephone pole along the electronic highway (excuse the platitudes). The musts are what I cannot live without; the shoulds are highly desirable:
- MUST be Php/MySQL, because this is what my host supports best, and this is where I have some experience. Though given a compelling reason, I'd trade php for python. It's OK if it uses local files instead of a database, though this is quite rare (DokuWiki).
- MUST be clean, valid xhtml/css, also when using custom themes.
- MUST have an easy way to maintain static pages (it's OK if they are called something else or aren't distinguished from dynamic content, as in Joomla).
- MUST support tags (keywords) for articles. Ideally, out of the box (like WordPress) - or through a plugin. MUST be able to show tag catalogs (as clouds or otherwise) and tags MUST be links.
- MUST have a flexible categorization system. SHOULD support assigning multiple taxonomies to individual articles (e.g. more than 1 category/section/etc)
- MUST provide some method to predefine templates (layout, not css stylings) for articles. SHOULD be able to associate templates with taxonomies (e.g. assign a different predefined article layout with each category. TextPattern can do this; too bad it's about the only thing it does).
- MUST support clean ("nice") URLs.
- MUST have an easy way of linking to articles internal to the site. This could be in the form of wikified links, or some other human-readable form. Allowing only for full URLs such as http://www.example.c...;id=26&Itemid=40
is unacceptable. Fully-formed clean URLs (http://www.example.c...foo/bar/this-article
) are also
unacceptable, because it's still tedious, error-prone, and the link will become stale if the article is later reassigned to a different category.
- MUST have a code (non-WYSIWYG) editor: using Textile, BBCode or similar approach, or just plain html. (Though some of those are quite evil too. Using six apostrophes
to get bold
as in MediaWiki is a bit on the absurd side, but I could live with it.)
- MUST allow raw html in articles. SHOULD allow raw php in articles.
- MUST allow inlining images. (TextPattern allows only 1 image per article - now try to make a page of screenshots).
- MUST generate RSS feeds for internal content.
- MUST have a reasonably good search engine built in.
- MUST have a systematized method of uploading files of all types and linking to them in articles. (WordPress does well here.) SHOULD be able to display download counts.
- MUST be translatable and able to switch languages on the fly; it it's not, I'll just rip it apart and make it.
- Creating themes (styles, templates) MUST be relatively painless. I don't expect to find a template better than this
for my personal site, or one that my wife will prefer to this
for her company. Joomla templates both, so I'll likely be buying those and adapting them for our sites. That will not be a pleasant process, but at least it SHOULD not be torture
- SHOULD have a basic versioning system that is at least able to retain old versions of articles. Diffing is not required.
- SHOULD be able to syntax highlight code (via a plugin or otherwise).
- SHOULD really have some smarts! When I add an inline image (and *especially* if there is a WYSIWYG editor with a UI dedicated to that purpose), then it SHOULD generate the width and height parameters for the img tag. Putting a big dialog box in my face with an Upload button *and* empty text fields to fill out the image dimensions is just lame. Every HTML editor since HomeSite 1.0 would do this automatically.Hello cmsmatrix