Design Philosophy Behind Weblog Tool

Creating for the web can be boiled down to three elements coming together for any given web page.

Content
Format(s)
Publishing Method

These come together in a staggering array of combinations and different forms but most of them boil down to just these three things. Sometimes the content is combined directly with its format, for example most people type text for pages and mingle HTML formatting tags directly into that text. Then they publish the result by copying the resulting files or FTP them to an HTTP server that is the final destination people connect to.
In other cases people start with XML or databases or who knows what else, combine it with XSL or JSP or ASP or some other formatting technology, and then they send the end result directly to the end user from the web server. In those cases the pages are built on the fly and every user who visits may see a different page than the last one to visit.
What I want now is a web logging tool that lets you edit data of a variety of different types. The initial type would be a simple one that I’m already quite familiar with (i.e. news/logs). The data would be stored for the user, combined with one or more format templates, and then published using one or more different publishing mechanisms.
So after thinking about the different parts and how they combine I’ve arrived at the following mix of parts that I think make up a good minimal system.
Content

  • News/Log items

Format(s)

  • HTML
  • RSS 0.91/0.92/1.0
  • AvantGo

Publishing Method(s)

  • The null publisher
  • The FTP publisher

And some ideas for a more fully fleshed out system.
Content

  • News/Log items
  • Picture catalogs
  • Link catalogs
  • Third party RSS channels

Format(s)

  • HTML
  • RSS 0.91/0.92/1.0
  • AvantGo

Publishing Method(s)

  • The null publisher
  • The FTP publisher
  • The Freenet publisher
  • The file copy publisher
  • The FrontPage publisher
  • etc.
Advertisements