4 Apr
2008
4 Apr
'08
4:37 p.m.
I'm reviewing java, open source CMS and wikis for a project we're soon to begin.
The project will mirror some of wikipedias functionality in allowing
collaboration on content to a set of authorized users, content discussion and
versioning. There are a couple of items that are driving me to CMSs vs Wikis
and I'm curious of xwiki might fit the bill.
1. I need more control of how the content is presented, i.e. strong
programmaticly enforced templates and 2. I need something that will store
portions of the content in separate database fields for more focused queries.
Some of these fields would be text while others would be numerics, dates, etc.
Something like a wikipedia country page but storing the Climate and Geology
sections of geography in their own DB fields and also storing metrics such as
GDP and Population as numbers in a relational database.
4 Apr
4 Apr
5:20 p.m.
New subject: [xwiki-users] xWiki functionality / Would it work for our project?
Hi Jeff,
I'm reviewing java, open source CMS and wikis for a project we're soon to
begin.
The project will mirror some of wikipedias functionality in allowing
collaboration on content to a set of authorized users, content discussion
and
versioning. There are a couple of items that are driving me to CMSs vs
Wikis
and I'm curious of xwiki might fit the bill.
Thanks for giving XWiki a look :-) From your short description I'm almost
sure it will fit. Let's see how :
1. I need more control of how the content is presented, i.e. strong
programmaticly enforced templates
XWiki was _meant_ to provide power user with ways to create templates that
can be used to define exactly how the content should be displayed on a page.
For instance, create an account on XWiki.org, log-in, go to this page :
http://www.xwiki.org/xwiki/bin/view/References/Alenty and click on edit :
you've got in-place edition that follows the defined template. (Please click
on "Cancel" afterwards rather than on "Save").
2. I need something that will store
portions of the content in separate database fields for more focused
queries.
Some of these fields would be text while others would be numerics, dates,
etc.
Something like a wikipedia country page but storing the Climate and
Geology
sections of geography in their own DB fields and also storing metrics such
as
GDP and Population as numbers in a relational database.
XWiki givs you the ability to define classes. A class is basically made of a
set of properties (I want a "country" class where countryname will be a
string property, countrypopulation will be a number property, countrycities
will be a databaseSimpleList property...) Then you can create new pages that
instanciate objects of this class : you create a page and add a "country"
object to it -> now you can store data in your page in a structured manner
using the object's fields.
From your description, that's what I'd call a
perfect match. :-)
The best way to understand the potential of XWiki is to check it out by
yourself. Check out
http://platform.xwiki.org/xwiki/bin/view/DevGuide/Tutorials and specifically
this one : http://platform.xwiki.org/xwiki/bin/view/DevGuide/FAQTutorial to
see how you could leverage XWiki's feature set for your project.
Hope this helps,
Guillaume
5 Apr
5 Apr
7:47 p.m.
New subject: [xwiki-users] xWiki functionality / Would it work for our project?
Look at this quick example
http://www.ludovic.org/xwiki/bin/view/Cities/
You won't have the rights to add a city but it's fully dynamic and build
on top of standard XWiki
Ludovic
Guillaume Lerouge wrote:
Hi Jeff,
I'm reviewing java, open source CMS and wikis for a project we're soon to
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
begin.
The project will mirror some of wikipedias functionality in allowing
collaboration on content to a set of authorized users, content discussion
and
versioning. There are a couple of items that are driving me to CMSs vs
Wikis
and I'm curious of xwiki might fit the bill.
Thanks for giving XWiki a look :-) From your short description I'm almost
sure it will fit. Let's see how :
1. I need more control of how the content is
presented, i.e. strong
programmaticly enforced templates
XWiki was _meant_ to provide power user with ways to create templates that
can be used to define exactly how the content should be displayed on a page.
For instance, create an account on XWiki.org, log-in, go to this page :
http://www.xwiki.org/xwiki/bin/view/References/Alenty and click on edit :
you've got in-place edition that follows the defined template. (Please click
on "Cancel" afterwards rather than on "Save").
2. I need something that will store
portions of the content in separate database fields for more focused
queries.
Some of these fields would be text while others would be numerics, dates,
etc.
Something like a wikipedia country page but storing the Climate and
Geology
sections of geography in their own DB fields and also storing metrics such
as
GDP and Population as numbers in a relational database.
XWiki givs you the ability to define classes. A class is basically made of a
set of properties (I want a "country" class where countryname will be a
string property, countrypopulation will be a number property, countrycities
will be a databaseSimpleList property...) Then you can create new pages that
instanciate objects of this class : you create a page and add a "country"
object to it -> now you can store data in your page in a structured manner
using the object's fields.
From your description, that's what I'd
call a perfect match. :-)
The best way to understand the potential of XWiki is to check it out by
yourself. Check out
http://platform.xwiki.org/xwiki/bin/view/DevGuide/Tutorials and specifically
this one : http://platform.xwiki.org/xwiki/bin/view/DevGuide/FAQTutorial to
see how you could leverage XWiki's feature set for your project.
Hope this helps,
Guillaume
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
6011
days inactive
6012
days old
2 comments
3 participants
participants (3)
-
Guillaume Lerouge -
jeff gerbracht -
Ludovic Dubost