On Sat, October 7, 2006 4:24 pm, sit1way wrote:
> I would dearly love to have a base CMS repository that all sites would
> draw
> on, extending the base CMS in the event that a particular client has
> need of
> customization. Some combo of Linux and Apache would do the trick;
> e.g. PHP
> requests
Le samedi 07 octobre 2006 à 17:24 -0400, sit1way a écrit :
> Hey all.
Hi Noah,
> I've built a simple, yet effective PHP based CMS, one that I use in all
> sites I develop.
[...]
> I've often heard the mantra, "separate code from HTML", but it seems
> ridiculous at times to include tiny HTML s
I dont think its so bad.
What I do is keep the PHP and HTML seperate, but in the same file: php on
top, html in a here document at the bottom. I COULD go one step farther and
have the HTML in a seperate file, but I just dont see the point.
td
On 10/7/06, Thiago Silva <[EMAIL PROTECTED]> wrot
On 10/7/06, sit1way <[EMAIL PROTECTED]> wrote:
Hey all.
This presents problems in that any updates I make to the CMS only affect
the
site I'm working on. So, while working on one site I may make changes to
the CMS, changes that improve the app., but other older sites do not get
updated -- it's
Hey all.
I've built a simple, yet effective PHP based CMS, one that I use in all
sites I develop.
Unfortunately, from site-to-site, functionality may be different; i.e. I
often have to extend the original CMS to account for custom client needs,
which means grabbing the most recent version of m
5 matches
Mail list logo
