A cookiecutter template for Wagtail CMS was built using Zurb Foundation front-end framework. A demo of a default project generated from this cookiecutter is available at https://wagtail.chrisdev.com.
Read the Docs: http://wagtail-cookiecutter-foundation.readthedocs.org/en/latest/
A Django project with Wagtail CMS pre-installed with support for all the Zurb Foundation components.
- For Django 1.10
- Renders Django projects with 100% starting test coverage
- Zurb Foundation
- 12-Factor based settings via django-environ
- Optimized development and production settings
- Built with Let's Encrypt
- Comes with a number of handy Custom Page models and templates (blog, photo_gallery, FAQ, events and so on..) to kickstart your site
- Uses Grunt for image compression and livereload
- Ansible for provisioning to and deployment to services like Digital Ocean and Linode
- Works with Python 2.7.x or 3.5.x
Here is how we create a new Django project quickly while letting cookiecutter to do all the work.
To get started we assume the following dependencies
pip virtualenv/pyvenv/virtualenvwrapper PostgreSQL Bower
Get Cookiecutter
$ pip install cookiecutter
Now run it against this repo:
$ cookiecutter https://github.com/chrisdev/wagtail-cookiecutter-foundation.git
You'll be prompted for some values. Provide them, then a Django project will be created for you
Cloning into 'wagtail-cookiecutter-foundation'... remote: Counting objects: 5849, done. remote: Compressing objects: 100% (129/129), done. remote: Total 5849 (delta 47), reused 0 (delta 0), pack-reused 5718 Receiving objects: 100% (5849/5849), 12.43 MiB | 2.64 MiB/s, done. Resolving deltas: 100% (3291/3291), done. Checking connectivity... done. project_name [Wagtail Project]: project_slug [wagtail_project]: Select version_control_system: 1 - git 2 - hg Choose from 1, 2 [1]: Select vcs_host: 1 - bitbucket.org 2 - github.com Choose from 1, 2 [1]: your_bitbucket_or_github_user_name [chrisdev]: author_name [Christopher Clarke]: email [[email protected]]: description [A short description of the project.]: timezone [UTC]: production_host_name [wagtail.chrisdev.com]: version [0.1.0]: use_letsencrypt [y]: use_celery [y]: use_opbeat [n]: use_django_cachalot [n]: use_wagalytics_app [n]: staging_host_name [wagtail-staging.chrisdev.com]: use_vagrant_staging [True]: deploy_user_name [django]: database_user_name [django]: django_admin_user [my_wagtail_admin]: Select open_source_license: 1 - MIT 2 - BSD 3 - Apache Software License 2.0 4 - Not open source Choose from 1, 2, 3, 4 [1]:
Enter the project
$ cd wagtail_project/
Create a git repo and push it there:
$ git init $ git add . $ git commit -m "first awesome commit" $ git remote add origin [email protected]:cclarke/my_site.git $ git push -u origin master
To create your project's virtual environment, install all pip dependencies, create the development database, run migrations and load initial data to database, install front-end dependencies and finally start the development server for you run
make all
You can access your site at http://localhost:8000
. The Admin back-end is available at http://localhost:8000/admin/
.The default Admin username is admin and The default Admin password is admin123.
We provide a comprehensive suite of apps to use for building your site. We take a modular approach so that can pick and choose the functionality you want to include. We provide separate modules for:
pages
- Different pages including Homepage, Standard & Faqs Page etc.blog
- Blog or site newscontact
- Contact Page with included contact us formdocuments_gallery
- Organize documents in folders using wagtail tagsevents
- Eventspeople
- For the people in your organization or team.photo_gallery
- Create photo galleries using wagtail tagsproducts
- Ideal for a product or portfolio showcasefaq
- FAQ and answers.utils
- Various utility functions, templatetags and filters
Contributions are always welcome to improve this project. If you think you've found a bug or are interested in contributing fork this project and send the pull request. After review, your pull request will be merged. We are always happy to receive pull requests. If you identify any issue, please raise it in the issues section.