Concepts

In this place we put all concepts, variations & ideas

When writing concept pages:

• Provide short summary of what the page is about surrounded with {excerpt} macro to make it appear in TOC
• Mark each page on top with the {status} to clearly inform others about the status of the given concept.

List of pages:

• Concepts - drafts and proposals
  • 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.
• Concepts - planned
  • Concept taglib cleanup, extraction, rewrite — In progress for 4.x - Simplification of our current tag library. See MAGNOLIA-2993@jira.
• Concepts - implemented
  • Concept Backup — Implemented in 3.6 - Implemented solution is JR specific. Backup also includes all versions of all documents.
    • Backup UI Proposal
    • JR BackupTool
    • PersistenceManager based Backup
  • 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 Groovy Support — Implemented in 4.3 -
  • Concept i18n next steps — Implemented in 4.3 -
  • Concept Link Resolving — Implemented in 4.0 - Describing the problem.
  • Concept mixin versionable — Implemented in 3.6 - Solved by using Solution C
  • Concept - multi site support — Implemented in 4.3 -
  • 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 - Rendering Engine — Implemented in 4.3 - Implemented without using a rendering context. The context will be introduced later.
  • Concept - Requests to Content Snippets (like Paragraphs or Areas) — Implemented in 4.3 - Uri to paragraphs will return the rendered paragraph/snipped
  • 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.
    • WebDAV notes
    • WebDAV support matrix
      • webdav & windows vista
      • WebDAV - mapping with WebDrive
  • Imaging module — Implemented in 4.1 - Needs docu ! Refactoring/rewriting of the image-filtering module.
  • Magnolia Data Module Extensions - Mixed type hierarchies
  • Module store — Implemented in 4.3 - First steps done. The store is accessible via the AdminCentral
  • 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.
  • UTF-8 page names — Implemented in 4.3 - If the property magnolia.utf8.enabled is set to true UTF8 page names are accepted
• 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 (Design) - Analysis
    • GenUIne (Design) - Concept
      • Genuine Dialogs
      • Genuine Feature - Structural Components
      • Genuine Feature - Toolbar
      • Genuine Feature - Virtual Website Hierarchy
      • Genuine Interaction - Creating Content
    • GenUIne (Design) - Design and Prototyping
      • Photoshop Files Guide
    • GenUIne (Design) - Specification
    • GenUIne (Design) - Implementation
  • GenUIne Technical Trail
    • GenUIne (Technical) - Concept
    • GenUIne (Technical) Focus Week
      • GWT 2.0
      • SmartGWT Findings
      • Using the GWT compiler at runtime
    • GenUIne (Technical) - Technology Discussion
      • GenUIne (Technical) - Sling
      • Genuine Technology Discussion (1st round)
      • Genuine Technology Discussion (2nd round)
    • GenUIne (Technical) - Server-Side Technologies Decision Table
    • GenUIne (Technical) - Prototyping
      • GenUIne (Technical) - Prototyping - Code Generation
      • GenUIne (Technical) - Prototyping - Maven Build
      • GenUIne (Technical) - Prototyping - Modularization
      • GenUIne (Technical) - Prototyping - UI
      • GenUIne (Technical) - Prototyping - JSON
  • GenUIne (General) - Blog Posts
    • Serving Different Users Needs (Draft)
    • Usability Principles Explained (Draft)
  • 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.