History of ReleaseThree
Version 10 | Current version | |||||||
---|---|---|---|---|---|---|---|---|
This is a work in progress and contains only proposals for new features Add new features if you think they would benefit the bitweaver Features proposed here are not guaranteed to make it to any release Proposed FeaturesStandardize functions across features.All main content features in CMS (wiki, article, blog, side module) should have the same core functions - view/edit/history and with the same wiki syntax, and wysiwyg editor.In other words, from the user's/webmaster's perspective the cms should all be wiki under the hood with many different templates. Example views
Make editing templates wysiwyg too:Do you want to have a standardized look to some or all of your wiki driven content? I sure do. Rather than have users fumble with formatting and trying to imitate style manuals, have a wysiwyg editor that creates a CSS template for a user definable category of objects. User story: I have a local band site that i invite local bands to feature themselves in - like a local myspace for bands. I want everyone to be able to wiki themselves a page, but i want all the pages to have similar content in a similar layout. So I define a category "band page and use bitweaver to create a "band page" template (it looks like a web form when they fill it in) which puts their photo, list of band members, upcoming gigs, band history, musical influences all in a nicely laid out page with cool formatting and images. So all the band has to do now is go wiki-->create new-->band page, fill in the form and bingo - its done. see also: Ultimate wiki cms Standardize Content AddressingBased on the standard and extended views/actions, packages should refer to content in foreign packages using universal code syntax.Portal Type PagesAllow pages to be created either (nominally) as the start page or as the user page that:
Custom blocks can be created and passed though the smarty parser Liberty Service EnhancementsEnhance Liberty Services so that:
In Place EditAllow any output generated by the Liberty parsers to be edited in place.Linkshttp://tool-man.org/examples/edit-in-place.htmlGreater JavaScript/XML/AJAX supportPut in the foundations to bitweaver for Javascript, AJAX, and JSON support at the content level.
Liberty
HTTP Content Contract ComplianceMake bitweaver behave like good web content
Installer Enhancements
Layout/Design
| This is a work in progress and has not been released yet Features proposed here are not guaranteed to make it to any release Upgrade Notes
Package UpdatesNewslettersPackage
Administrator Notes
Developer Notes
|