mbrukman / xmpp.org

xmpp.org website (builds: https://travis-ci.org/xsf/xmpp.org/builds)

xmpp.org

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/pages or 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.

Communication forum

Please use [email protected] for discussions about the site, content, generation etc.

Site generation

• 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.).

Installation instructions

git clone ssh://[email protected]/xsf/xmpp.org.git
# install Pelican and dependencies
cd xmpp.org

Requirements

• Pelican 3.3
• ghp-import
• Markdown 2.3.1

Runing the server in development mode

make serve

If you want the server to autoreload whenever a file change, you can instead do:

make devserver

View at http://localhost:8000

Configuration

<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>

Site generation

To just generate a new version (without starting up a local webserver) just do:

make html

Theme development

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.