Home

Welcome! This wiki is for anyone who wants to maintain or contribute to the PWindows website. You do not need to be an expert in web development.

The guide is divided into sections so you can read only what applies to your task.

Start here

Use Getting Started to prepare your computer and learn the normal workflow. Repository Structure explains where pages, images, shared information, styles, and scripts are stored.

Edit content

Use this section when changing information visitors read:

• Creating and Editing Pages - add or update a normal website page.
• Localization - understand language routes and translate pages, data, and news.
• Publishing News - write and publish a news article.
• Managing Site Data - choose the correct guide for games, departments, staff, or shared links.

Design and code

Use Styling and Interactions when changing how the site looks or how an interactive control behaves. It links to separate guides for responsive CSS and accessible interactions.

Test and release

Use Testing and Deployment after making a change. It separates the checks you run yourself from the process that publishes the website.

Contribute

Before submitting work, complete the Contributing Checklist. Then follow Making a Pull Request to ask for a review on GitHub.

How the website is published

The website uses Jekyll, a tool that turns the files in the repository into a static website. GitHub Pages hosts the finished site.

Note

GitHub Pages currently publishes the redesign branch while the new version is being tested. When the redesign is considered stable, main will become the publishing branch again.

Rules that apply everywhere

• Keep existing public links working.
• Keep default-language pages at unprefixed routes and follow Localization for translated content.
• Store shared information in _data/ instead of copying it into several pages.
• Make the site usable with a keyboard, mouse, touchscreen, and screen reader.
• Run the relevant checks before asking for a review.
• Never edit or commit generated _site/ or .jekyll-cache/ files.

Tip

A route is a public address such as /about or /games. If you intentionally add or remove one, update tools/verify-site.rb and check the site's /sitemap page too.