Blogging systems have their roots in simple content
management operations: Create a post, persist
it in stable storage such as a filesystem or database,
and display the formatted output based on some
set of temporal or keyword criteria. As the richness
and types of content presented in blog pages
expanded, and the requirements for sorting,
searching, selecting, and presenting content grew to
include metadata and content taxonomies, the line
between vanilla, single-user–targeted blogging
software and enterprise-grade content management
systems blurred.
A robust CMS is measured by the utility
of its content. Even the richest content types
and most wellmanaged processes are of low
return if nobody actually consumes the outputs.
It’s not sufficient to install blogging software,
write a few posts, and hope the world shows
up on your virtual doorstep
Installing WordPress Files
If you download the WordPress code from
wordpress.org, you’ll get a zip or tarball archive that
expands into a directory called wordpress.
The first part of a WordPress installation is to get the
code into your web server’s directory structure;
ensuring you have it in the right place is a critical
step. Gloss over this part and you’ll find your
website ends up with a URL like http://test.com
wordpressand you’ll either have to start over or
e-mail ugly URLs to your friends and family. If
that’s what you want — to distinguish your
WordPress site from other content on your
website or to isolate multiple sections — choosing
the filesystem layout is equally important.
management operations: Create a post, persist
it in stable storage such as a filesystem or database,
and display the formatted output based on some
set of temporal or keyword criteria. As the richness
and types of content presented in blog pages
expanded, and the requirements for sorting,
searching, selecting, and presenting content grew to
include metadata and content taxonomies, the line
between vanilla, single-user–targeted blogging
software and enterprise-grade content management
systems blurred.
A robust CMS is measured by the utility
of its content. Even the richest content types
and most wellmanaged processes are of low
return if nobody actually consumes the outputs.
It’s not sufficient to install blogging software,
write a few posts, and hope the world shows
up on your virtual doorstep
Installing WordPress Files
If you download the WordPress code from
wordpress.org, you’ll get a zip or tarball archive that
expands into a directory called wordpress.
The first part of a WordPress installation is to get the
code into your web server’s directory structure;
ensuring you have it in the right place is a critical
step. Gloss over this part and you’ll find your
website ends up with a URL like http://test.com
wordpressand you’ll either have to start over or
e-mail ugly URLs to your friends and family. If
that’s what you want — to distinguish your
WordPress site from other content on your
website or to isolate multiple sections — choosing
the filesystem layout is equally important.
