comment on

Blosxom is a great project - but it's not a solution suitable for my purpose. I do not want to make adding content easier for myself. I want to provide a simple tool for the users. With Blosxom, they would have to create a structured text file in a specified location, then run the generator, then run something that syncs the generated content and the website. Even using "Save As..." is not a simple task, not for everybody. Navigating the directory tree is not simple as well - for some users, "it's on my computer" equals "it's on the desktop".

This could all be simplified by writing a script that automates the process - it could be placed on the client's desktop, but still - the script would have to be written, Blosxom would have to be configured, and some problems would have to be resolved (even with basic instructions like "put the title in the first line of the text file, the author name in the second line..." - some validation would have to be provided, with two or more users - there will be problems with sync, and so on).

I love the idea behind Blosxom, and tools like vee, and if I had a personal site, or a weblog, this would be my choice for content management. But those are not tools for this task, not for my users. Adapting them for this purpose would be at least as much work as writing an "Add-a-News-Item app". Again - this is not a question of managing a whole website, it's just about adding text-only news items.

regards,
Luke Jefferson

In reply to Re^4: Adding content blocks to a static website by blindluke
in thread Adding content blocks to a static website by blindluke

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.


laziness, impatience, and hubris
	PerlMonks