Allow me to help Puppian get your views about the CMS that we will use. "CMS" was already discussed in the "out for a walk" sections of the forum.
CMSimple has great outlining feature and WYSIWYG editors, but appears limited as to collaboration (maintaining groups with members keeping individual access).
PHP-fusion will be the next simple CMS, though I am not yet sure about its support for groups in the way I described. Here is a thread about the CMS.
Cheers!
CMS
What I use
Raffy,
A tool I use at work that is a Wiki is PmWiki. Advantages:
- No database required. All content is handled as a series of flat files. But there is code to use DBs to store data if desired.
- Fully customizable using what are called 'Recipies' similiar in nature to 'Dot Pups'.
- It expands the idea of a single Wiki to a farm so that a single instance of code can run multiple wikis if desired.
- Has skins for different looks. The CSS is exposed so if desired a skin can be modifed or an entirely new skin can be created.
- Project teams for PmWiki are now working on embedded HTML forms.
- Can develop a Wiki that can have authentication against a page, series of pages or entire site. Or none at all if desired.
- The PmWiki team has very much a flavor very much like the Puppy folks here. A tight core of contributors with a benevelent dictator moving things forward as to core design. It works.
Downsides? -
- Search is not as fast as a DB based Wiki but at only 5secs to search the entire PmWiki.org site I don't think that is a problem.
- Some Wiki functions are implemented differently. Not missing just not done like WikiWiki, MediaWiki or MoinMoin.
- Initial learning curve can be somewhat steep. But the returns are great.
PmWiki has a great future. Take a look. I have developed my own CMS based on Recipies that fit my need. By the way take a look at the PITS system that has been developed. A good simple tool to manage bugs. Seems to work for them.
Url -- http://www.pmwiki.org
A tool I use at work that is a Wiki is PmWiki. Advantages:
- No database required. All content is handled as a series of flat files. But there is code to use DBs to store data if desired.
- Fully customizable using what are called 'Recipies' similiar in nature to 'Dot Pups'.
- It expands the idea of a single Wiki to a farm so that a single instance of code can run multiple wikis if desired.
- Has skins for different looks. The CSS is exposed so if desired a skin can be modifed or an entirely new skin can be created.
- Project teams for PmWiki are now working on embedded HTML forms.
- Can develop a Wiki that can have authentication against a page, series of pages or entire site. Or none at all if desired.
- The PmWiki team has very much a flavor very much like the Puppy folks here. A tight core of contributors with a benevelent dictator moving things forward as to core design. It works.
Downsides? -
- Search is not as fast as a DB based Wiki but at only 5secs to search the entire PmWiki.org site I don't think that is a problem.
- Some Wiki functions are implemented differently. Not missing just not done like WikiWiki, MediaWiki or MoinMoin.
- Initial learning curve can be somewhat steep. But the returns are great.
PmWiki has a great future. Take a look. I have developed my own CMS based on Recipies that fit my need. By the way take a look at the PITS system that has been developed. A good simple tool to manage bugs. Seems to work for them.
Url -- http://www.pmwiki.org
Joomla
We have been evaluating Joomla recently, and can see how it has won so many awards. It can also integrate with phpbb, so the users of the forum automatically become users of the Joomla system.
Puppy Linux's [url=http://www.murga-linux.com/puppy/viewtopic.php?p=296352#296352]Mission[/url]
Sorry, my server is down atm!
Sorry, my server is down atm!
- lickthefrog2
- Posts: 57
- Joined: Wed 22 Nov 2006, 18:30
I originally used the predecessor to Joomla, and then moved to Xoops2, then Drupal. These are all fairly complex CMS. Easy to install, but heavy. When I gave others access they found it difficult to use the admin sections. Okay for geeks, but not the average user.
If you want to keep it simple and don't need exotic modules, then I think a light Wiki might be what serve your purpose.
If you want to keep it simple and don't need exotic modules, then I think a light Wiki might be what serve your purpose.