#midgard

Some interesting ideas (that I can still remember):

• Remote component controllers called via Gearman async calls that populate their output to page via COMET (so page rendering doesn't block while they're still working)
• Reporting issues (or setting tasks) straight from the CMS interface, synchronization to our issue tracker or some corporate bug tracker
• Components installable and editable straight from the CMS interface
• Scaffolding new components or data types just by using them in a template (displaying "title" property ensures such property is added to the object definition)

You should produce light version of midgard that wouldn't require root access to server. And decent documentation. My 5p for next steps.

@mtarvainen there used to be Midgard Lite, a pure-PHP implementation of Midgard APIs. Especially now that the Midgard2 API is a lot simpler (old API was some 300 PHP functions) that could be something interesting to revive.

@bergie There are ~500 functions/methods now in core IIRC.

@mtarvainen There are many things we invent from scratch for Midgard. Good ideas are always welcome if you consider documentation :)