InfoGlue CMS

Projects

Roadmap

This area will give users and other interested parties an idea of where InfoGlue is heading and what features to expect in the future.

It is important for readers to understand that these list only are rough plans and no guarante are made that the updates will be released at the proposed dates. The community allways set quality first so we will release when we feel the platform is ready and tested. This sometimes mean we will release earlier or later and sometimes we add/substract functionality from a release. Join the community if you want to be able to influence the decisions on this point.

Rough plans for version 2.9 (release date Q2-2008):

  • Minor performance and security updates and stability enhancements mainly in the admin tools.
  • Better support for Opera and Safari browsers.

Rough plans for version 3.0 (release date Q3-2008):

  1. A new GUI design with a new menu system and a new advanced tree with rightclick and draggable features. This is big but perhaps we could manage it.
  2. A good form-designer with backend storage support.
  3. A translation GUI which lets you have two languages between each other so you can read the original as you translate. A fun feature would be to include a translate through babelfish or similar
  4. A validate html-feature from the structure view and from content version view.
  5. A label system that can be managed from management tool and where you can add new languages as modules dynamically. Would also like all images containing text to be replaced with css-controlled classes or dynamic rendering to simplify language handling.
  6. A lot more usability features that makes it easier for end users and developers.
  7. A trashcan feature.
  8. On my part, I'd like to see a more lightweight admin UI based on full CSS, frameset is just a pain, we can't bookmark any pages.
  9. The most important issue for InfoGlue is to widen its user base. For 3.0 we would therefore like to see improvments concerning usability issues. Improving usability is something I consider cruscuíal for widening the InfoGlue user base. I would be happy to provide any developer with a list of usability issues collected from ”my” users.
  10. On another note I would also like to suggest that InfoGlue.org is developed. What I miss is documentation. I also miss a road map for the next release. Maybe examples of best practice, etc.
  11. Export/import: for our purpose, we have to work on that part. We want to move structures versions, contents versions, etc from db to db, with replacement/merge system. Maybe, we couldn't do that with the actual
    functionality. We plan to work on this. We clearly prefer to do this inside a global community plan to improve IG. To not disturb the head development, we could work on specific CVS branch?
  12. Ordering site nodes: we have developed a functionality to manually order site nodes (structures). It's working and we can submit it to community.
  13. Repository fallback. A repository can be parent of another (this feature exists). To fulfil our specific integration of IG in our system, we are working and implementing structure and content inheritance between repositories.
  14. Also, we agree that these points would be useful:
  15. Upgrade and cleanup all library. For example: castor 1.0, Servlet 2.4, JSP 2.0 + taglib 1.2 (current taglib implementation is 1.1 style), hibernate3, etc
  16. Change persistent framework to Hibernate
  17. Impove cache update system
  18. Intergrate Search engine to both CMS and deliver
  19. user self-registration
  20. delete/update portlets
  21. JSR-170
  22. some built-in Lucene support
  23. Spring
  24. recursive copy : copying an entire folder, with its sub contents and subfolders
  25. recursive copy of pages
     
  26. provide PostgreSQL, SAP DB functionality (more scalable DBMSs than MySQL);
  27. Generation of static content (for highly-loaded servers with simple pages);
  28. Support for visualization of published/unpublished content and sitenodes. Perhaps content/sitenodes with green labels are working and red labels are published (hence not editable)
  29. A "manual installation" readme document to facilitate installing in other servlet containers, such as JBoss+Tomcat.
  30. Installer packages as warfiles, and setup in the webapp.
  31. Support for more appservers (the above could manage that, jetty for example)
  32. support for more db's lite postgres.
  33. Clean up all properties and configurations (on a good way with 2.3 and the db properties)
  34. What about integrating a spell-checking facility?
  35. Why not using the persistence part of JSR 220 on top of Hibernate?