This space hosts concepts, the roadmap and the backlog. It is not meant for content related to developing projects with Magnolia. For this kind of information the community space should be used.

• Backlog
• Concepts
  • Concepts - drafts and proposals
    • Proposal - merging of URI2RepositoryMapping and VirtualURIMappings — * URI2RepositoryMapping and VirtualURIMapping have very similar goal and functionality (i.e determine which repository node to use based on a URI)
    • Proposal - overhaul and refactoring of AggregationState — * AggregationState is a very rough 1:1 copy of Resource and Aggregator, and improving this area would take templating improvements of 3.7 even further.
    • Proposal - prefixing or namespacing of certain properties in paragraphs — There are a number of properties we currently use which could be "standardized". In order to avoid conflicts with user defined (custom) properties, these would need to be prefixed or namespaced(*). This would particularly apply to properties used outside of templates, i.e in actions or tags, for example the infamous hideInNav property.
    • Project definition concept
    • Concept Public Versioning — Draft for 3.7 - Summary of finding and ideas identified while looking at possible ways to implement MGNLDMS-137@jira
    • Concept Page Locking — Page locking alerts you if someone else is already editing a page you wish to edit.
    • Concept Static Publishing — Static publishing provides a way to publish to static html instead of dynamically publishing from a public Magnolia server.
    • Concept C2BDoc — Draft for 4.0 - prototype is in svn, +/- working, needs refinement - currently a manual procedure, not integrated in maven build. See MAGNOLIA-2491@jira.
    • Proposal - core packages — Draft for 4.x or 5.0 ? - ...
    • Concept IOC in Magnolia — Draft for Magnolia 4.2+ - Introducing IOC in Magnolia
    • Concept Module downloader updater — Draft for Magnolia 4.1+ - Simplify the updates of Magnolia instances
    • Concept Standalone bundles — Draft for Magnolia 4.2+ - Better/simpler bundling. See MAGNOLIA-2686@jira for status.
    • Concept Diagnostics — Draft for 4.2? - A tool in the AdminCentral that provides a all-in-one zip file for reporting issues.
    • OSGi notes
    • Concept Synchronization — Draft for Magnolia 4.1 - Synchronize two instances based on the activation status by using activation. Writing a first script for a customer
    • Concept Form Handler — Draft for 4.0.1+ or 5 - for discussion, soliciting more ideas. Needs correction/comparison with current Form Module
    • Spam handling
    • Concept Caching In Clustered Env — Draft for 4.1 - Considering options for advaning cache implementation to behave correctly in clustered env.
    • Simplified Cache Configuration — Draft for 4.2? - Since Magnolia 3.6, the cache configuration is extremely versatile but also very complex. We should "hide" that complexity behind "meta" voters or something similar. (MAGNOLIA-2557@jira)
    • Google AppEngine and Magnolia+JCR
    • Concept License Mechanism — Draft for 4.2? - Current license mechanism is not flexible enough
    • Concept Recovery — Draft for ? - While we have implemented a full backup & restore tool (EE only) we have not yet a solution for partial backups and partial recovery of instances
    • Concept - Serving content based on recency decay bias — Draft for 4.x - Serving content based on recency decay bias.
    • Social publishing
    • Concept Import Handler — Draft for x.y - Refactoring/rewriting of the {{ImportHandler}}s in Data module.
    • Concept Activation — Draft for 4.x - Rewriting of the existing activation.
    • Unicode support status
    • Apache Solr - Magnolia integration
    • Module Descriptor Generator (maven plugin)
    • Parallel Activation — Draft for 5.x - Ideas for improvement of publishing experience for big sites. Increase the speed of activation for big trees.
  • Concepts - planned
    • Concept Groovy Support — Draft for 4.3 -
    • Concept i18n next steps
    • Concept - multi site support — In progress for 4.3 -
    • Concept taglib cleanup, extraction, rewrite — Draft for 4.3 - Simplification of our current tag library. See MAGNOLIA-2993@jira
    • some bits for 4.3
  • Concepts - implemented
    • Concept Backup — Implemented in 3.6 - Implemented solution is JR specific. Backup also includes all versions of all documents.
    • Concept Caching — Implemented in 3.6 - Eager re-caching part is still open to implementation. Biggest obstacle is need to hit the server with http request to generate fresch cache entry.
    • Concept Commenting — In progress for Magnolia 4.0/Forum 1.0 - Evaluating usage of forum module for page commenting.
    • Concept Content API review or rewrite — Implemented in 4.3 - Some major steps have been taken. We have also created a jira ticket(MAGNOLIA-3015@jira) which is split into several subtasks.
    • Concept Link Resolving — Implemented in 4.0 - Describing the problem.
    • Concept mixin versionable — Implemented in 3.6 - Solved by using Solution C
    • Concept Multi-value — Implemented in 3.7 - This page contains a summary of what would be needed to implement multi-value properties. See MAGNOLIA-2363@jira outstanding for this module is edition in the tree, feature not planned at the moment. Included sample in sample module
    • Concept Observation module
    • Concept Short-urls — Implemented in 3.6 ee - This page contains a summary of what does this module and modifystream module do. This module would be used to shorten the images urls in a, img tags. See MGNLSHORTURLS@jira MGNLMODSTR@jira
    • Concept Transactional Activation — Implemented in 3.6 - Ideas for improvement of publishing experience for big sites with multiple public instances.
    • Concept WebDAV — In progress for 4.x - WebDAV protocol allows clients to map resources of compliant server as remote directories, thus greatly simplifying resource update and manipulation.
    • Imaging module — Implemented in 4.1 - Needs docu ! Refactoring/rewriting of the image-filtering module.
    • Magnolia Data Module Extensions - Mixed type hierarchies
    • Node builder API — Implemented in 4.2 - We've had the need several times for a simple node building api - especially in version handlers - to construct relatively simple nodes (couple of nodes, couple of properties) without having to maintain complex bootstrap or properties file, and verbose/long code. I'd like to propose a simple DSL/API similar to the one used to build tasks and deltas for this.
  • Concept field based saveHandler — Implemented in 3.6.1 - Implemented but not documented.
  • Concept - simplified content config updates — Draft for 4.2 - (!)see NodeBuilder API concept page - Writing and maintaining update tasks is a error-prone and also boring task.
  • Concept Demo-Content — Draft for STK1.2/Magnolia 4.2? -
  • Concept Deployment
  • Concept Google-Analytics — Draft for STK1.2/Magnolia 4.2 -
  • Concept provided users roles and groups
  • Concept Security and ACLs — Draft for ? - Collecting security related issues and improvements
  • Concept Tags & TagClouds
  • GenUIne Overview
    • GenUIne Design Trail
    • GenUIne Technical Trail
    • GenUIne (General) - Blog Posts
    • GenUIne (General) - Links
    • GenUIne (General) - Meeting 2008-01-23
    • GenUIne (General) - Meeting 2008-02-18
    • GenUIne (General) - Meeting 2008-02-20
    • GenUIne (General) - Meeting 2008-02-22
    • GenUIne (Technical-Misc) - Javascript Tools
  • Jaas and UserManagers — Draft for ? - Review and cleanup of our JAAS usage.
• Conference notes
  • Clustering
  • conference - caching session
  • conference - i18n session
  • User Generated Content
  • Versioning
• Developer information
  • Code style
  • Jira usage
  • Links for developers
  • Releases
  • Svn structure
    • Previous SVN structure
• Development Tips & Tricks
  • Create a New Module
  • Customer Project Setup
  • Eclipse
  • Intellij IDEA
  • New Developer Primer
  • Testing Magnolia
  • URI encoding in Tomcat
• Performance
  • Performance Magnolia 4.2.1
    • resource download breakdown
• Presentations
• Roadmap
  • Roadmap 3.6
  • Roadmap 4.0
    • 4.0 Templating notes
    • Dev Samples Module
    • Form module
    • Mail Module
    • Newsletter Module
    • Other API breaking changes for 4.0 — – moved to documentation site
    • Statistics module
  • Roadmap 4.1
  • Roadmap 4.1.1
  • Roadmap 4.2
  • Roadmap 4.3
    • API changes in 4.3
  • Roadmap 5.0
• Standard Templating Kit
  • Commenting
  • Dynamic Asset Management (DAM Support)
  • Features Screen Cast
  • FreeMarker and STK
  • FreeMarker Primer — moved to http://documentation.magnolia-cms.com/reference/freemarker.html
  • Javascripts used in STK
  • Renderer, Model and Template Definition
  • STK 1.2 Maintenance
  • STK Book
    • STK Project Best Practice
    • STK References
    • STK Configuration
    • STK CSS concept
    • STK Installation
    • STK Introduction
    • STK HTML structure
    • STK Templating
  • STK Documentation Material
  • STK Training Outline
  • STK User Training Outline
    • Exercises
  • Themes

Blog

Magnolia team members are blogging (contributors in alphabetical order):

Boris

BetterFasterBigger (life is now)
Getting serious
ModeShape - a unified content bus for Magnolia?
Happy Old Year, Happy New Year for Magnolia CMS
Magnolia Conference Keynote
Dynamic Redirects

Greg

Greg's ramblings (about Magnolia and other stuff)
Going agile, one burndown chart at a time
Build updates
Winstoned !
Growing and shrinking
IE6 on OSX

Jan

rah003's blog
Multi-site support in Magnolia
Not so damned DAM handlers
Magnolia Conference
How many backup solutions is too many?
Magnolia Cache in clustered environment

Philipp

http://philipp-baerfuss-magnolia.blogspot.com

Philipp Bärfuss (Magnolia) (Magnolia CMS and beyond.)
Configuration Inheritance (Magnolia 4.3)
i18n support in dialogs (Magnolia 4.3)
STK Book
STK 1.1, next level
STK: HTML and CSS structure

Vivian