ijc-website

Code for the International Jugger Council (IJC) website.

Points of Contact

If you have a question related to the IJC website, try contacting one of these people:

Note that the IJC is volunteer-run; we have no dedicated support staff, our members are across various timezones, and the people working on this website have day jobs! We'll try to respond within a few days - and sooner if the matter is urgent - but we can't make any guarantees.

Get Involved!

Development is coordinated in two places: Discord and GitHub.

Discussion with the rest of IJC takes place via #ijc-web (and sometimes other channels, depending on the topic) on the Jugger Worldwide Discord server. That's the best place for non-technical discussions: content strategy, branding, working with other groups in IJC, etc. If you want to be involved in the what and why of IJC's website, get involved on Discord!

Specific issues, features, etc. are logged on the IJC Website Issues page on GitHub. That's the best place for technical discussions: tools, frameworks, hosting, etc. If you want to be involved in the how of IJC's website, pick up an issue or two on GitHub!

To contribute to IJC website development, you will need to become a part of the international-jugger-council GitHub organization.

Tech Stack

ijc-website is a static site, built using a couple of simple tools:

• eleventy, a static site generator that supports modular templates and layouts (e.g. if you want the same look-and-feel, navigation bar, etc. on each page);
• nunjucks, a templating language by Mozilla;
• bulma, a flexbox-based CSS framework that provides simple utilities for building clean, responsive interfaces.

Develop!

To run a copy of the IJC website locally, you will need git and npm. You can then:

1. git clone this repo on your favourite computer;
2. npm install;
3. npm run serve;
4. Visit the site;
5. Edit files in src, and see changes instantly in your browser.

For submitting changes to the IJC website, we use the feature branch workflow in git. This works as follows:

1. assign an existing issue to yourself, or create a new one if no relevant issue exists;
2. note the issue number (e.g. #42);
3. create a feature branch for that issue number (e.g. git checkout -b gh42-meaning-of-everything);
4. do your work on that feature branch;
5. eventually, push that work to GitHub (e.g. git push -u origin gh42-meaning-of-everything);
6. submit a pull request;
7. get that pull request merged.

Ideally the pull request should be reviewed by someone else. That said: getting new content out there is more important than strictly following a process! If a reviewer isn't available, at least take a quick read over your changes, and make sure you test that they don't break the site. Feel free to merge after that's done!

Deploy!

The site is automatically deployed every time the master branch is updated.