| 
	
 | 
 Posted by Ming on 12/31/07 06:31 
On Dec 30, 6:08 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote: 
> Ming wrote: 
> > On Dec 30, 5:24 pm, NC <n...@iname.com> wrote: 
> >> On Dec 30, 12:05 am, Ming <minghu...@gmail.com> wrote: 
> 
> >>> I am looking for a PHP based CMS (or blog system) that supports: 
> >>> 1) static output (like Movable Type) 
> >> You can stop looking right there.  Static output has long since gone 
> >> out of fashion.  Some Perl applications (MovableType, Discus, and a 
> >> few others) still use it only because they were initially designed 
> >> that way back when MySQL 3 wasn't around, so they stored their data in 
> >> flat files rather than databases.  The rest of the world has moved on 
> >> to a combination of dynamic output and caching...  Some systems (such 
> >> as Drupal) also have granular cache control (the administrator can 
> >> select which components' output it to be cached and which is to be 
> >> always generated dynamically) and throttling (certain components may 
> >> be designated as non-critical and not executed during peak-load 
> >> periods). 
> 
> >>> 2) remote publishing through FTP, SFTP or SSH (like Blogger) 
> >> I may be wrong on this, but as far as I know, Blogger is the only 
> >> application that does it... 
> 
> >>> 3) Different templates for different parts of the system (ie: 
> >>>    category template, main index template, search template, 
> >>>    like Movable Type does; Blogger seems to just have one 
> >>>    template) 
> >>> 4) Free (or low price for multiple installations) 
> >>> 5) One central installation for multiple sites 
> >> WordPress MU seems to fit the bill on these... 
> 
> >> Cheers, 
> >> NC 
> 
> > Hi NC and all folks, 
> 
> > Thanks for suggestion. 
> 
> > Static output is critical for me because many users, college students, 
> > do not have access to either PHP or MySQL in their college campus/ 
> > department personal webspace. Most universities only permit pure 
> > static content (HTML, image, flash, etc) for student web space. 
> 
> > FTP/SFTP/SSH access is a MUST-HAVE  feature. Since we want a central 
> > installation that supports students from all departments. 
> 
> You aren't going to find a CMS which doesn't depend on dynamic content. 
>   That isn't how they work. 
> 
> If you want static output, have them use ftp/sftp, etc. 
> 
> -- 
> ================== 
> Remove the "x" from my email address 
> Jerry Stuckle 
> JDS Computer Training Corp. 
> jstuck...@attglobal.net 
> ================== 
 
Sure. But the DB shall only be used in generating content,ideally.
 
  
Navigation:
[Reply to this message] 
 |