skip to main content

kiesler.at
FutureOfPhpWebSite
Back to Page | Back to History

Difference between revisions

Version 9, 2005-04-07 14:49 Version 15, 2008-07-16 12:19
Lines 70 - 76 Lines 70 - 76
- if an earlier version is selected, all new stuff would be embeded within ins-tags, all removed stuff within del-tags - if an earlier version is selected, all new stuff would be embeded within ins-tags, all removed stuff within del-tags
- there would be meta-infos on some place of the screen (who changed what and when) - there would be meta-infos on some place of the screen (who changed what and when)
   
(Typo3 does [http://www.carnet.hr/CUC/cuc2004/program/papers/list/b5_milovan_absbio.html not] do that) (Typo3 does [http://www.carnet.hr/CUC/cuc2004/program/papers/list/b5_milovan_absbio.html not] do that, But Article Manager Does)
   
+++ distribute content to different branches +++ distribute content to different branches
   
Lines 137 - 140 Lines 137 - 149
   
Development should always keep the end user in mind. Sometimes it is better to take a few steps back to see the larger picture. Since 9.2, there has not been a major change in the way content has been handled. (It could be even longer, but I started with 9.2.) Many of the management questions seen in forums about phpWebsite deal with the lack of intuitiveness concerning menus, categories, blocks etc. This results not in new modules being developed, but rather hacking existing modules to make them more intuitive not only to the content editor/manager, but to the viewer of the site. Development should always keep the end user in mind. Sometimes it is better to take a few steps back to see the larger picture. Since 9.2, there has not been a major change in the way content has been handled. (It could be even longer, but I started with 9.2.) Many of the management questions seen in forums about phpWebsite deal with the lack of intuitiveness concerning menus, categories, blocks etc. This results not in new modules being developed, but rather hacking existing modules to make them more intuitive not only to the content editor/manager, but to the viewer of the site.
   
Menus should be category driven. Link manager sould be as well, but in a way that interacts with the content in a way other than just whats related. A menu should be links within the site driven by category. Linkmanager could be associated with a specific category, or even a specific page only. Every group would have access to link manager because it is a repository of links. You should be able to add categories to a link, without removing an existing category. In other words, no dropdown menu with multiple select. More like dropdown, select, submit. It could work that way when you delete a category as well. Menus should be category driven. Link manager sould be as well, but in a way that interacts with the content in a way other than just whats related. A menu should be links within the site driven by category. Linkmanager could be associated with a specific category, or even a specific page only. Every group would have access to link manager because it is a repository of links. You should be able to add categories to a link, without removing an existing category. In other words, no dropdown menu with multiple select. More like dropdown, select, submit. It could work that way when you delete a category for any piece of content as well.
   
  +++ Webpages
   
  We have already seen the success of Article Manager. PhpWebsite should either adopt it into the core, or add the features of announcements to web pages. Do not continue to run a module out there that is inferior in every way to a module designed by a third party.
   
  +++ Link Manager
   
  I still need this one explained. How do I associate Linkmanager with the rest of my content? How is it displayed? Why are categories assigned to it, when there doesn't seem to be a reason why? Really rather confusing.