Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/theme-bulletin/llms.txt

Use this file to discover all available pages before exploring further.

Every theme in the ThemeBulletin gallery is a standalone static website pre-configured for deployment on GitHub Pages. There is no build step, no CI pipeline to configure, and no environment variables to set. The entire deployment process — from picking a theme to having a live URL — can be completed in under five minutes.
All ThemeBulletin themes are pre-configured for GitHub Pages. The HTML, CSS, and JavaScript files use relative paths and require no server-side processing, so GitHub Pages serves them exactly as they are without any additional setup.

​
Deployment Steps

1

Browse ThemeBulletin and Pick a Theme

Open ThemeBulletin and browse the category boards. When you find a theme you like, open its detail page and click Open Live Demo to see the full interactive experience. When you are ready to proceed, note the theme’s GitHub repository URL from the detail page.
2

Open the Theme's GitHub Repository

Click the View GitHub Repository link on the theme’s detail page, or navigate directly to https://github.com/apursley2012/<theme-id>. You will land on the repository’s main page on GitHub.
3

Fork the Repository to Your Account

Click the Fork button in the top-right corner of the repository page. GitHub will ask you to confirm the fork destination — select your personal account. Leave the repository name as-is for now (you can rename it after forking). Click Create fork to proceed.
If you want your portfolio to be served at https://yourusername.github.io/ (the root domain, without a subdirectory), rename the repository to yourusername.github.io during or after the fork. GitHub Pages automatically recognizes this naming pattern and serves the repository at the root URL.
4

Go to Repository Settings > Pages

In your forked repository, click the Settings tab (the gear icon at the top of the repo). In the left sidebar, scroll down to the Pages section under the “Code and automation” group and click it.
5

Set the Source to the Main Branch

Under the Build and deployment section, ensure the Source is set to Deploy from a branch. Set the branch to main (or master if your repository uses that name) and set the folder to / (root). Click Save.GitHub Pages will begin building your site immediately. The first deployment typically completes within one to two minutes.
6

Your Site Is Live

Once the deployment completes, GitHub Pages will display your live URL at the top of the Pages settings panel. It will be in the format:
https://yourusername.github.io/repo-name/
Click the URL to confirm your portfolio is live. You can now share this URL, add it to your GitHub profile, and start customizing the theme content.

​
Serving at Your Root Domain

By default, a forked repository named developer-dossier (for example) will be served at https://yourusername.github.io/developer-dossier/. If you want your portfolio served at https://yourusername.github.io/ with no subdirectory path, rename the repository to match your GitHub username exactly:
  1. Go to Settings in your forked repository.
  2. Under General, find the Repository name field.
  3. Change it to yourusername.github.io (replacing yourusername with your actual GitHub username).
  4. Click Rename.
GitHub Pages will automatically detect this special repository name and serve it at the root domain.

​
Using a Custom Domain

If you own a custom domain (for example, yourname.dev), you can point it to your GitHub Pages portfolio:
  1. In your repository’s Settings > Pages panel, enter your custom domain in the Custom domain field and click Save.
  2. GitHub will create a CNAME file in your repository root containing your domain name.
  3. At your domain registrar, create a CNAME DNS record pointing your domain to yourusername.github.io.
  4. Wait for DNS propagation (this can take up to 48 hours, though it is usually much faster).
  5. Once propagation completes, enable Enforce HTTPS in the Pages settings panel.
For apex domains (e.g. yourname.dev without a www subdomain), you will need to configure A records instead of a CNAME. See the GitHub Pages custom domain documentation for the current IP addresses to point to.

​
What to Do Next

Once your theme is deployed, you will want to personalize it with your own name, bio, project links, and color preferences.

Customize Your Theme

Learn how to update HTML content, override CSS custom properties, and swap fonts.

Fork and Adapt

Go deeper — add new sections, set a custom domain with a CNAME file, and run the theme locally.

Build docs developers (and LLMs) love

Get started for freeTalk to us