|
Thursday 25 February 2010 12:41:07 pm
I most likely need some feedback from experienced users, since this is a fairly tricky thing to do.
The website will have content that is extensible. Take the following example:
Website has profile of user and cars.
Initially the profile stores: Name
Cars
For some reason, after a while we would also like to store the wife of the user and info about his pets. So the fields become: Name
- first name
- last name
- age
- married to
Cars
pet
After a while... and so on.
This thus tends to become fairly complicated as such, with fields being added along the way. Provided that there is something like a CCK, I initially thought that CCK would be very good, since it allows a user with not a lot of tech background to easily create fields and reorganize the whole list as such. However, I believe that when creating fields +100, the performance will go down rapidly. In other words, maybe that's not such a good idea.
I'm very new to eZ, so I might have overlooked some options. One vague option I heart of was to create different nodes for each of these fields and link them together (using e.g. ID's or whatever) and present them to the end-user.
So the main question is: with content that will be expanded with sub-tables and sub-sub-tables and so on, is CCK a viable solution or have I been overlooking what is a core feature of eZ?
|