Hi guys, while Aiki Markup is not ideal, I cleaned up the documentation. In making comments on the code, I've noticed many undocumented markup and have been adding them to this page.
http://www.aikiframework.org/wiki/Aikimarkup For Aiki Markup 2, I'm wavering between nuking current markup all the way to abstracting it so that older sites stay compatible and we can work on something better and *actually* logical. If you have a better idea, see what jcubic, myself and others have started talking about: https://blueprints.launchpad.net/aikiframework/+spec/fix-aikimarkup However, there are far more pressing issues to fix on the codebase first. As a goal for simplicity, I would like to see us have a more complete API first at the code level and keep support where possible. Jon -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
