|
|
Posted by Susanne West on 02/13/07 09:46
Rik wrote:
>
> Bigger project -> go for a database.
>
> Specify in the database what modes require what scripts, what pages
> have what content (possibly storing flat HTML directly in the database
> for easy maintainability). Make an interface for it, and presto, with u
> few buttonclicks most of the pages adapt directly to how you want
> them, without fiddling about in tons of files.
>
> I usually define one or several layouts, store a page-tree in the
> database and link layout-id's to the pages as desired. Create content
> (where 'content' can be flat HTML, the name of a (php-)file to include,
> some custom wrapper around a certain database-queries, etc.), and again
> link that to the pages. Voilà, the beginnings of your own custom build
> CMS.
>
hi.
i know what you're heading after. the point is, that a raw db with data
exists, and i don't want to build a page-based db besides. all i need is
already in a relational structure and i only have to pull it out in
different ways. that can easily be done with identifyable modules and
routines which is much faster than to build a whole page-system on top.
what you describe makes maily sense if you have tons of manually-
maintained pages. then i'd opt for a page-db also. also, i don't have
'different' layouts with modules that are turned on/off depending of the
page. it's really just a framework with the same components around
all the time...
greets.
Navigation:
[Reply to this message]
|