Please log any issues.
Any editorial questions: Laura Gill or Simon Tennant can help
Contributing new content and updates
- Fork the code to your own git repository.
- Make your changes in
/content/pagesor directly in GitHub.
- When you are happy with your updates, submit a pull request describing the changes.
- IMPORTANT :- Before sending a Pull Request make sure that your forked repo is in sync with the base repo.
- The updates will be reviewed and merged in.
Please use firstname.lastname@example.org for discussions about the site, content, generation etc.
- Commits to the master branch generate a new build.
- Builds are visible at https://travis-ci.org/xsf/xmpp.org/builds
- New content is deployed to gh-pages branch
- and visible on http://new.xmpp.org
Gentle introduction to Pelican
Pelican's QUICKSTART page is a good place to learn about the basics of Pelican (installation, project skeleton, development cycle, etc.).
git clone ssh://email@example.com/xsf/xmpp.org.git # install Pelican and dependencies cd xmpp.org
- Pelican 3.3
- Markdown 2.3.1
Runing the server in development mode
If you want the server to autoreload whenever a file change, you can instead do:
<repo> fabfile.py develop_server.sh Makefile README.md pelicanconf.py (development configuration) publishconf.py (production configuration) output <generated files - published to gh-pages branch> content pages <website page files> pelican-bootstrap3 <website theme>
To just generate a new version (without starting up a local webserver) just do:
You can modify the theme (layout and styling) in the xmpp.org-theme directory.
Make changes to Sass files, not compiled CSS.
npm i then run
grunt to compile Sass.