| Getting Started |
| Content Type Management | |||
| Written by Ercan Özkaya | |||
|
Now we are approaching to the end of community bonding period and there's only a little time left before coding starts. So before getting started, I wanted to make a more detailed explanation of my project and *hopefully* get some feedback from the community. In my opinion, different content types are one of the most common needs for a CMS. This feature would result in reducing the number of components by combining most of them with a single content component and also allow flexibility with little effort. So, if anything goes as expected, I'll implement this functionality this summer with the guiding of my great, helpful mentor Jason Kendall. But although the project is about content types, my component will also be a content component just like com_content. So the first thing I'm doing is to fork com_content and chop it cruelly. In my version, there won't be any sections and categorization will be based on nested categories. I'll also take out some features like voting, frontpage view (to replace with a different implementation that allows multiple frontpages at a later point) If we continue talking about content types, they will be based on fields like textarea, checkbox, radio button etc. By combining the needed fields, you'll be able to create what you want. For example, you can create an image gallery by adding an input box for image link, a text area for image description and some fields for image metadata. Then by creating a template, you'll be able to show it the way you want in your site. To add a new content item, you'll be prompted to select the content type you want among a list of your existing types. Then a form will be generated with all the fields for that type. So once you set up your content type and create your template (which may require a developer hand) any user in your site will be able to create new items easily. Above is the skeleton for what I'm building. But not only me, our community -which means you- will use this component. So your feedback is more than important. If you have any ideas, wishes, criticism, bad words please shoot them in comments. They are greatly appreciated.
|




Monday, 08 December 2008
What are the implications of these fundamental changes for Joomla upgrades?
Monday, 26 May 2008
Thanks again. For your comment and for your support through the whole period for GSoC.
@Mati
Originally I was only planning to make the fields a plugin. But I think that your idea is also brilliant. I noted it and even though it'll be in a later phase, I'll sooner or later implement it. It's good to hear those brilliant ideas in the beginning. So I'll keep them in mind when coding. Thanks for your feedback.
Wednesday, 21 May 2008
I was wondering if you could implement an import/export mechanism for content-type structure (not the actual contents)?
this will allow to create pre-defined packages for a gallery (as you said) or many other well-known structures...
I'm not sure if this is part of you project scope, but if you create room for this in your framework - it could be more than great!!!
I hope you'll have as much fun as we'll have once your done with this project...
Monday, 19 May 2008