The
other part is the rendering engines that will show the content to end users, which Chapter 8 will
mostly cover.
I??™ve decided to divide the content management tasks into several different parts, and these
parts will mesh nicely with the different models in the system. The tasks will be divided into
administrating the styles of the system, where styles can be Extensible Stylesheet Language
Transformations (XSLT) style sheets that transform XML, or Cascading Style Sheets (CSS) styles
that will change the user interface for the end user. The next tasks are administrating layouts
(where a layout is an ordered collection of styles), administrating paths (a path is a subdomain
within the system), and writing articles. Further, there will be a separate part for handling users
authenticated to the system.
CoMpoSe won??™t have any authorization; every administrator can do anything in the system.
Authorization would be easy to add, though, and should be implemented in a real
application. Although we won??™t have authorization, we??™ll add a simple authentication system,
much like in the last project, so that the administration parts of CoMpoSe aren??™t open to the
whole world.
CoMpoSe will render content in different stages, where the text of an article can be styled
with either Textile (through RedCloth), Markdown (through BlueCloth), or just as plain text.
The end result of rendering the article will then be processed with the layout associated with
the article, or with the path this article is part of.
Pages:
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207