- Concept - Improvements on Form Module, PUR and Commenting — Draft for 4.x/STK 2.0 - The current Form, Public User Registration and Commenting modules must get improved and streamlined.
- Concept - Rendering Context — Draft for ? -
- Concept - Separation of repository implementation from core — Draft for ? -
- Concept - uuid or permanent links — Draft for ? -
- Module's localization process — Draft for ? -
- OpenId
- STK Blog Template
- 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.
- Concept - Cache Improvements — Draft for ? - The locking was solved in 4.3, other improvements are pending
- 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.