CMS Revolution (Part 2)
Web 1.0: Static publication
The next question is why does the adjustment
model in this browser not freeze? The short answer is that it was not given the
opportunity, because WorldWideWeb is only available for the mysterious NeXT
system of Steve Jobs. They are Macintosh and Windows which have been developed
prosperously and Mosaic and Netscape Navigator browser are read-only.
As a matter of fact that content circulation
is our focus; design has been transfered to the center stage. Berners-Lee's
method will be effective if you happy with your site looking just like the
others, and it would be connected and accessed via a single link, but the first
generation of the web content creators want those websites with recognizable
identity, not just a collection of indistinguishable page.
This can be done with HTML by using tag
<img> for graphics and navigation graphics, tag <table> for multiple
columns layout, and tag <font> to control printing in rough, but that is
too much to wait on a browser editor, or even Notepad. A solution in the form
of dedicated HTML authoring applications such as CyberStudio / GoLive,
FrontPage and Dreamweaver of course. These tools make publishing model based on
familiar static pages, and professional web designers dominate as well as being
the center of the booming of Web 1.0.
However, a publishing model focusing on
design like that comes at a high price. HTML tried to avoid performing and
forcing it to be against the tendency to become a designing tool, which is not
easy at all. Even worse, performing control were transfered to the browser and
the set of end users; therefore, trying to make the page look the same as
everyone system became a real headache.
Static publication has another basic problem,
which is makeing, your content more accessible. Authoring in Berners-Lee's
browser is based on the simplicity of a single link between pages. You can
navigate the connected site by using the Back button, but when the websites
develop, designers want to provide instant access to many pages; if not, it
could lose visitor. This means that every time you post a new page, you need to
update links to and from many others, and sacrificing scalability. With large
sites, the management of navigation soon became bigger than the page design.
Once attached to the rich-in-content page
design and complex navigation, page-based publishing model suddenly lost its
simplicity and inherent efficiency. Specialized authoring tools as Dreamweaver
can offer another way by providing templates, shared libraries, and CSS
support. However, advances like high require further knowledge, and to ensure
that web design became the job for only professional experts. This is the
reality of publishing static web pages, instead of being simple and open to
all, the creation of pages is complex and limited to skilled professionals,
wholeheartedly by using expensive and dedicated software.
This situation seems to be acceptable when
establishing the new website at the beginning but the bottleneck’s getting
stuck become apparent once the site owner wants to add new content, or even
just update a page and find the only way to do that is to go back to the
designers (assuming they are still there) . Again, there are other solutions,
such as Contribute, a dedicated content processing software of Dreamweaver, but
this is just tape. The key point is that static web publishing is simple,
versatile and popular to some extents. It's good enough to start web 1.0, but
it is unable to be scalable and its limitations started to hamper web
development.
Web 1.5: Non-static publication
The solution is a publication model which is
totally different, not static but dynamic. Here, a website is no longer a
combination of fixed pages but a database. Pages provided to browsers do not
really exist as separated HTML files but they are quickly created from document
records in a database - the URL is interpreted as a query request.
Database publishing seems to have gone far
away from the original vision of Berners-Lee; but in fact, it has always
focused on his views. Indeed, publication is led by data which keeps the noble
position in addition to being innovative in browser in the method list
originally proposed by him. As his original plan specifies: a W3 server
"port" that can run on your current system, making the information in
it available to the world. "Publishing is led by the original data is very
basic. Over time, the scripting language like PHP and ASP would be developed.
They allow developers to embed multiple advanced database queries in the
webpage’s HTML structure. Meanwhile, techniques such as URL rewriting,
permalink and page caching breaks the distinction between real and virtual
sites.
Being released from having to provide
contents to web designers, many users currently can update the database,
ensuring that people can receive the contents and updates at best. The content
is driven by data which directly changes the web, and opens a new generation of
businesses such as Amazon, where the website is the company.
Web 3.0
Websites led by database are created with
content management systems which provide other advantages compared to static
pages: they are ready to work with the next RIA generation.
