[Wiki] changed: Project/Hydra

chuck  Mon, 02 Nov 2009 13:20:31 -0500

Modified page: http://wiki.horde.org/Project/Hydra
New Revision:  1.33
Change log:  dummy text generation

@@ -1,84 +1,53 @@
  [[toc]]
-


  + Hydra
-
-

  Hydra is the new CMS/wiki-like app being created for ((Project/HordeWeb))
-


  ++ Bugs
-
-
-


  ++ Source
-
-

  Hydra is being developed in the [http://horde.org/source/git.php  
Horde hatchery]
-


  ++ People
-
-

  ChuckHagenbuch and RalfLang are working on Hydra.
-


  ++ Description



  +++ Draft specification
-
-

  We need some sort of CMS to manage the content of the site and to  
make some areas user-editable like the current wiki. We may adopt an  
existing CMS, or we may adapt some of our own existing code. I propose  
that we create a new app similar to Wicked and the old Giapeto app,  
with the following feature list:
-


  * **Must** have a solid API for plugins, external access, embedding, etc.
-
  * Support for different page content-types (wiki, HTML, textile)
-
  * a GUI HTML editor for html content pages
-
   * loki and fckeditor seem most promising so far for this; I want  
something that supports h1-h6, p, and tables at least - no <font>,  
mostly semantic markup.
-
  * inline preview (instead of wicked's popup - can just be an  
overlay). only necessary for non-HTML
-
  * permissions like Wicked
-
  * implicit or explicit hierarchies based on / as a separator
-
  * use Horde_Routes for URL management
-
  * use Rdo for data classes
-
  * store versions of content like wicked does
-
  * Good search based on Horde_Content_Index
-
  * generate feeds of edit activity across the site/sites; good  
storage of when and by whom content was last edited
-
  * hierarchical navigation of content  
(http://twiki.org/cgi-bin/view/Plugins/TreePlugin)
-


  ++++ Layouts

  * use @ instead of $this-> for shorthand?
-
  * look at rails layouts
-


  Page Object

@@ -86,58 +55,39 @@

   - how to return block from driver, inherit Block methods, but also  
inherit Rdo_Base

  Mapper! Mappers are the drivers
-


  ++++ Horde_Text_Transformer
-
-

  * text_to_html
-
  * html_to_text
-
  * wiki_to_html
-
  * wiki_to_?
-
  * textile_to_html
-
-

  Horde_Text_Transformer::transform($text, $from, $to = 'html');

  * finds the best transformer
-
  * if there's no exact match, sees if there's an intermediate through  
'text' (i.e., textile_to_text goes from textile_to_html through  
html_to_text)
-


  ++++ Usage Roles

  First guess

  * (anonymous) visitors
-
  * (logged in or anonymous) users that interact with application  
widgets (shop, wiki, whatever) on the front-end website side
-
  * (logged in) users/editors that generate content by direct  
interaction with the "horde desktop" and its applications like jonah,  
wicked in the traditional way
-
  * (logged in) site operators that can edit layouts, style sheets etc
-
  * (logged in) hydra application admins that can add new Websites etc
-


  chuck suggested that the "horde desktop" role should be solely a  
content administration role.
-
  End users should see a website that doesn't necessarily look like an  
application.

  --Ralf Lang
-
-



  ++++ Old requirements list from the rampage cms project
@@ -298,8 +248,9 @@

  * http://ego-app.com/

  * http://gridder.andreehansson.se/
+* http://www.blindtextgenerator.com/






-- 
To unsubscribe, mail: [email protected]