Deployment steps
Fork or clone the repository
Fork rampatra/wedding-website to your GitHub account, or clone it locally and push to a new repo.
Install dependencies and build
Install npm dependencies, then run The build pipeline (defined in
gulp to compile SCSS to CSS and minify JavaScript.gulpfile.js) produces two output files:css/styles.min.css— compiled and compressed stylesheetjs/scripts.min.js— minified JavaScript
Commit all compiled assets
The compiled files must be committed to the repository. GitHub Pages serves files directly from your repo — it does not run a build step.
node_modules/ is listed in .gitignore and must not be committed. Compiled CSS and JS files, however, must be committed so GitHub Pages can serve them.Enable GitHub Pages
In your GitHub repository, go to Settings → Pages.
- Under Source, select Deploy from a branch.
- Choose the
mainbranch (ormaster, depending on your repo) and the/ (root)folder. - Click Save.
The .nojekyll file
The repository includes an empty .nojekyll file at the root. This file tells GitHub Pages to skip Jekyll processing.
Without it, Jekyll would ignore any file or directory whose name starts with an underscore (_). The SCSS partials in sass/partials/ use the _ prefix convention (e.g. _colors.scss, _typography.scss), so while they are compiled before deployment, the .nojekyll file is a safeguard that prevents GitHub’s build environment from stripping those files if they are ever served directly.
URL format
| Setup | URL |
|---|---|
| Default GitHub Pages | https://<username>.github.io/<repo-name> |
| Custom domain | https://yourweddingdomain.com |
