Not to be contrary but:
# Must be platform independent (at least Linux/Win)
# MySQL may be a requirement, but I'd be just as happy with flatfile
What for?
Extensible & easy to use are reasonable requirements, but who cares what kind of database or OS you need to run it on, as long as it's not hideously expensive or unstable. Why not run it on ruby/freebsd/postgres (just as an example)?.
I can't really give you an answer to your general question though, since every single generic CMS I've looked at sucks in more than a few ways (anything from generating hideous markup and being hard to work with as an end user to being far too inflexible and/or difficult to upgrade with custom patches/changes). And I don't really care about the implementation language (as long as the language doesn't preclude it from being reasonably cheap and easy to deploy and extend).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
