Gondola is a hosted CMS that gives designers a powerful and easy platform to create amazing geo-enabled Websites.
The purpose of this document is to introduce site designers to the Gondola platform, including how to manage the templates and media for a Gondola site.
Gondola is a hosted content management system (CMS). We manage all of the “back-end” code on our servers, while providing full access of the “front-end” code for customization of the look and feel of the site. Gondola is written using the Django Web framework.
Gondola provides remote access to templates and static media files via the WebDAV protocol. Since Gondola is a hosted service, all your development must be done against our remote system. You will have access to a development site where changes can be tested prior to pushing to production. Assuming you are working on mysite.com, you will be setup with the following URLs on our system:
The administration interface is used to manage content on the site. It can be accessed via http://[mysite].gondolacms.com/admin/. In addition to site administration, you will see a set of links in the upper-right:
The site documentation provides links to documentation for all of the features available to you as a site designer. Probably the best place to start is the Views documentation which will show you every page available on the site, what its function is, what template it uses, and what variables are available within that template.
We regularly update Gondola to add features, make it easier to use, and fix bugs. Any major changes are documented here.
After poking around the admin a bit, you’re probably ready to start customizing your site. The first step is to connect to your files via WebDAV. All the major operating systems have WebDAV support built-in so the remote files can be edited as if they were on your local machine. If you are unsure of how to connect via WebDAV, consult your operating systems help files or simply look it up on Google. Once connected, you will see two folders:
Within each folder, you will find 3 directories:
When serving your site, the dev or production folders will be used first. If the file needed is not in those folders, Gondola will fallback to the files in your default folder. If the file does not exist there, an error or 404 Not Found will be returned. In this way, it is not necessary to re-write every file used by your site, only the ones you would like to customize.
Gondola uses the Django template engine which should be relatively easy for anyone who has written HTML templates before to pick up. The documentation at the link above is an excellent start.
In order to minimize the possibility of breaking the production site, we recommend the following workflow:
When your site is ready to launch, you’ll probably want to serve it from your own domain. This can easily be done at your domain registrar. You’ll want to take two steps:
We have a Google group setup for designer questions at http://groups.google.com/group/gondola-cms. For general questions about the Django template system, lots of help can be found simply by searching Google or asking via the recommended channels.