\documentclass{article}
\usepackage{ulem}
\usepackage{graphicx}
\usepackage{hyperref}
\pagestyle{headings}
\begin{document}
\part{<a href="https://wiki.horde.org/RampageFramework">RampageFramework</a> CMS component}
Steps from Giapeto:

\begin{itemize}
\item Templates have been moved into the VFS. A default template is loaded if none are present. Now we need a template manager for editing templates.


\item Simplify configuration as much as possible.


\item Allow for hosting multiple sites from one giapeto config. Need a way to differentiate. Perhaps have a small set of files that host a giapeto site? Problem is then you wouldn't be able to create them through the web.


\item Probably want to keep php4 compatibility for now


\item Need some sort of workflow


\item Versioning: At least one previous version should be kept to facilitate rollback


\item Default config should result in a reasonable site that looks like a web site, not a Horde app


\item Ease of use all over


\item Rely on Horde\_Template blocks integration, instead of "main" content area with confusing block splitting?


\item If so, need some sort of a "compositeblock" functionality to allow users to put custom content into an area without editing a template


\item Provide a standard blog template with Jonah integration?


\item How to handle user-supplied images? Not galleries - do that through Ansel - but page design images - borders, etc.


\item Should sites be able to lock themselves to a specific theme? Probably...


\item Give a theme selector widget for sites that want to allow variation


\item If possible, make the CMS link in the Horde sidebar go to an admin screen, while having /horde/giapeto/ still be the root user-facing site


\end{itemize}
\end{document}
