AtomicWiki is entirely based on the Atom Publishing Protocol and syndication format. All entries are stored as Atom feeds. The Atom Publishing Protocol is used to create and manipulate feeds and entries. The entire system is implemented in XQuery and XSLT with the help of some Javascript for the AJAX goodies (like in-page comment editing). What makes the software really powerful is its tight integration with XQuery and XML databases. Macros and extensions to the wiki syntax are implemented as XQuery functions. XQuery code can also be directly embedded into an Atom entry to generate dynamic content. The eXist weblog is powered by AtomicWiki.
PierCMS content management system that aims at allowing users to manage their content from the browser. The central concept in Pier is the one of Structure. For example, the current page is a structure. The blog is also a structure, but it is slightly different than a page. A file is also a structure. Commands can be executed on a Structure. For example, a Structure can be edited, and once in edit mode, you can use the Pier syntax. In the original setup the commands appear in the footer, and are accessible after logging in. To make life easier, Pier also offers access to commands via Browser shortcuts. Any Structure can be Viewed. The default View is the one that renders the structure for normal usage. Another example, is the Browse View which offers a file system like view on the Pier structures. Any Structure has an environment which defines the template. To set the environment to be a different page use the Settings command. To edit the environment use the Edit Design comman
keep my life in a subversion repository. For the past five years, every file I've created and worked on, every email I've sent or received, and every config file I've tweaked have all been checked into revision control. Five years ago when I started doing this, using CVS, people thought I was nuts to use revision control in this way. Unlike CVS, subversion has reasonable handling of directories and file renaming, which is more than sufficient reason to switch to it if you're already using CVS, and most of CVS's other misfeatures are also fixed. But subversion still has its warts, such as an inability to store some file permissions and its need for twice as much disk space as you'd expect thanks to the copies of everything in those .svn directories. These problems can be quite annoying when you're keeping your whole home directory in svn.