Here is the list of features and I'd like to know which of them are planned, when, and which are not. It would be cool if Oliver posted his own 'to-do' list with rough time estimates.
1. STRUCTURE
1.1 Cross-structures. For example one structure is:
About
Documents
Downloads
Articles
Links
Then other structures for
Developers (which contains documents, downloads, articles, links for developers)
Designers (contains templates, articles - everything for designers)
Project managers – likewise.
2. NAVIGATION
2.1 Menu based on cross-structures
2.2 Level based menu (it is in progress, right?)
2.3 DHTML menus (drop down, expanding)
2.4 Sitemap
3. DESIGN
3.1 Template inheritance (if not set a level inherits default or parent level's template). Possibility to apply a template to multiple sections.
3.2 Import/export site as a file. Option to choose importing/exporting layout&tempaltes and/or content.
4. CONTENT
4.1 Hierarchical catalogue with static and javascript tree.
4.2 News. Can be put on front page or into sections. Can be as a single item or linked to article. In the latter case article should contain News attribute and text area for teaser.
4.3 FE user areas.
4.4 Article search.
4.5 Use of the same content in different places.
5. CONTENT MANAGEMENT
5.1 Customised BE. Content types filter per user, simple workflow, languages, users (editors) are able to see and edit only their content.
6. DEVELOPMENT
6.1 Simple API to build and integrate extensions into Content Types.
cheers,
Marius.
Features request
Yes...
Cross structures would be a good idea, but the dependencies would have to require almost every other single thing you listed, like user areas and so forth.
DHTML menues would actually be pretty easy to implement, perhaps this is when CSV files need to come into play to seperate the menu items, such as:
and so on...
OR you could use a menu.array.php file:
Of course this would take forever to create the code to modify these.
Just some ideas.
Cross structures would be a good idea, but the dependencies would have to require almost every other single thing you listed, like user areas and so forth.
DHTML menues would actually be pretty easy to implement, perhaps this is when CSV files need to come into play to seperate the menu items, such as:
Code: Select all
CSV (Comma Separated Values) Navigation File:
1:Test,test.php+
1.1:Test One,testone.php+
1.2:Test Two,testtwo.php+
1.2.1:Test Three,testthree.php;
2:Downloads,downloads.php+
OR you could use a menu.array.php file:
Code: Select all
<?
$dhtml_menu = array(
'Test' => 'test.php',
array(
'Test One' => 'testone.php',
'Test Two' => 'testtwo.php',
array(
'Test Three' => 'testthree.php'
);
);
'Downloads' => 'downloads.php',
);
Just some ideas.
- Oliver Georgi
- Site Admin
- Posts: 9892
- Joined: Fri 3. Oct 2003, 22:22
- Contact: