Selenium Site and Documentation

This is the repository used to build and publish the official Selenium website.

Quick start

We use Hugo and the Docsy theme to build and render the site. You will need the extended Sass/SCSS version of the Hugo binary to work on this site. We recommend to use Hugo 0.169.0

Steps needed to have this working locally and work on it:

• Install Hugo and follow the Get Started instructions from Docsy
• Install go
• Install Node.js (LTS 24)
• Clone this repository
• Run cd website_and_docs
• Run npm install
• Run hugo server

npm install is required, not optional: since Docsy 0.16.0 the theme's Bootstrap and Font Awesome assets are npm packages rather than Hugo modules. Skipping it makes the build fail with SCSS import errors. If you ever change the Docsy version, run hugo mod npm pack first to refresh packages/hugoautogen/, then npm install again.

A full contribution guideline can be seen at contributing

How to get involved?

Please check all the information available at https://selenium.dev/getinvolved/

Do not want to clone the repository to contribute? Use GitPod

For Selenium Site and Documentation maintainers

How does the site and docs get build?

GitHub actions runs for every commit on each PR and protected branch. The regular CI execution will build the site with Hugo to verify that the commit works. The description of these steps can be seen at the actions configuration file, one for testing a PR, and one for deploying the site

How are the site and docs deployed?

After each CI execution that happens in the trunk branch, the script build-site.sh is executed for deployment. This script checks for the string [deploy site] in the commit message.

If the commit message contains that string, and the commit is in trunk, a GitHub action is triggered to build and deploy the site. The site and docs will be built, and the changes will be committed to the branch publish by the user Selenium-CI.

What is important to take into account is that the source files for the site are in the trunk branch, and the files that get deployed are pushed to the publish branch.

The site is deployed using GitHub pages, and the configuration for this can be seen at the repo settings (if you are a maintainer you should be able to access the link).

The selenium. domain is managed at https://www.gandi.net/en, if you need access to it, reach out to any of the PLC or TLC members, who can help you with that.

If for any reason, you need to setup the domain redirection again, we followed this guide, but any tutorial/guide showing how to redirect a domain to GitHub pages should do.