Using Wiki's as a model for SMB Web Sites
Wiki's have a very simple and powerful model for content management that seems to follow Tim Berner Lee's orginial concept for the world wide web where all content is linked via a url. Wiki's allow you to create new pages by inserting a link into an existing page. A "navigator" then uses a search or a url to pick a"landing-point" in this content space and explores the links from there.
Wiki's also use the pattern of "view-edit-save" thru the browser - so there is no separate step for transferring information from a "composer" program to the web server.
As most web sites are a collection of web pages anyway ,why are not all web sites done this way? Some common reasons with my thoughts on resolving them.
A) Preventing Grafiti
Solution: A "Lock" on pages - to ensure only authorized people can edit it
B) A "nice" aesthetic look to the pages
Solution: A Use-Template type command line at the top of the page
C) Images
Wikis ,like weblogs, tend to be text oriented; But company websites are online brochures and advertisements, so pictures are a must. Wiki pages do allow images but these images must be locatable via a url.
Solution: Images can be linked-to image catalogs at portals or other image web service providers ;These image banks can permit small business to upload private images to company specific folders. Basically the SMB subscribes and links to a url addressable file directory
D) Catalog Pages
Solution: Use-CatalogPage template with text markup like..
item, sku, picture, price
Conclusion
It appears that we are suggesting an extension of the wikitext markup templates ; Now if we take that step, why not just make the wiki page an XML page that is editable thru the web? is that not CompeteSmart's design for the Office Portal solution ?
Wiki's also use the pattern of "view-edit-save" thru the browser - so there is no separate step for transferring information from a "composer" program to the web server.
As most web sites are a collection of web pages anyway ,why are not all web sites done this way? Some common reasons with my thoughts on resolving them.
A) Preventing Grafiti
Solution: A "Lock" on pages - to ensure only authorized people can edit it
B) A "nice" aesthetic look to the pages
Solution: A Use-Template type command line at the top of the page
C) Images
Wikis ,like weblogs, tend to be text oriented; But company websites are online brochures and advertisements, so pictures are a must. Wiki pages do allow images but these images must be locatable via a url.
Solution: Images can be linked-to image catalogs at portals or other image web service providers ;These image banks can permit small business to upload private images to company specific folders. Basically the SMB subscribes and links to a url addressable file directory
D) Catalog Pages
Solution: Use-CatalogPage template with text markup like..
item, sku, picture, price
Conclusion
It appears that we are suggesting an extension of the wikitext markup templates ; Now if we take that step, why not just make the wiki page an XML page that is editable thru the web? is that not CompeteSmart's design for the Office Portal solution ?
Comments