This is a static site built using Eleventy. The build files are located in the docs folder, as required for deployment on GitHub Pages.
- Static Site Generator: Uses Eleventy for flexible, fast static site generation.
- Customizable Build Directory: Outputs build files to
docs/for compatibility with GitHub Pages. - Easy Development Workflow: Includes scripts for development and building.
Before getting started, ensure you have Node.js installed on your system.
-
Clone the repository:
git clone https://github.com/Brick-Force-Aurora/Website.git cd Website -
Install dependencies:
npm install
Run the development server with live reloading:
npm startThis will start a local server and watch for changes. The site will be accessible at http://localhost:8080/Website/ by default.
Generate the static files for production:
npm run buildThe build files will be output to the docs/ directory.
To deploy to GitHub Pages:
- Ensure the
docsfolder is included in your repository. - Push changes to the
mainbranch:git add . git commit -m "Build and deploy" git push origin main
- Go to your repository’s Settings > Pages on GitHub.
- Set the source to
mainand the folder to/docs.
The site is available at https://brick-force-aurora.github.io/Website/.
.
├── docs/ # Output folder for build files (GitHub Pages source)
├── src/ # Source files
│ ├── _includes/ # Layouts and partials
│ ├── css/ # CSS files
│ ├── js/ # JavaScript files
│ ├── index.html # Homepage
│ └── about.html # About page
├── .eleventy.js # Eleventy configuration
├── package.json # Project metadata and scripts
├── README.md # Project documentation
└── .gitignore # Ignored files
npm start: Start the development server with live reloading.npm run build: Build the project for production.npm run deploy: Deploy the project to GitHub Pages (if configured withgh-pages).
- Eleventy Configuration: Modify
.eleventy.jsto customize input/output directories or plugins. - CSS/JS: Add or modify styles and scripts in the
src/cssandsrc/jsfolders.
This project is licensed under the MIT License. See the LICENSE file for details.