Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/geotrev/airleventy-jetpack
An 11ty template with lots of useful presets.
https://github.com/geotrev/airleventy-jetpack
11ty bootstrap css eleventy javascript netlify sass static-site-generator template
Last synced: 4 days ago
JSON representation
An 11ty template with lots of useful presets.
- Host: GitHub
- URL: https://github.com/geotrev/airleventy-jetpack
- Owner: geotrev
- Created: 2021-04-03T17:14:14.000Z (almost 4 years ago)
- Default Branch: develop
- Last Pushed: 2021-05-18T23:54:09.000Z (over 3 years ago)
- Last Synced: 2024-12-06T23:43:20.696Z (2 months ago)
- Topics: 11ty, bootstrap, css, eleventy, javascript, netlify, sass, static-site-generator, template
- Language: JavaScript
- Homepage:
- Size: 409 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Airleventy Jetpack
A moderate extension of the [Airleventy](https://github.com/geotrev/airleventy) static site template. Includes extended tooling:
- prettier
- stylelint
- eslint
- autoprefixing for css
- bootstrap sass## Increase your power levels
1. [Add favicons/device icons](https://www.favicon-generator.org/)
2. [Add a sitemap](https://developers.google.com/search/docs/advanced/sitemaps/build-sitemap)
3. [Configure eleventy](https://www.11ty.dev/docs/watch-serve/)## Setup
```shell
$ npm i
```## Commands
### Develop
```sh
$ npm run watch
```### Build
```sh
$ npm run build
```Or build production ready assets:
```sh
$ npm run build-prod
```There are also a slew of individual commands to run individual build processes such as styles, scripts, etc.
## Netlify
First, enable your airleventy fork on Netlify's interface.
When prompted, clear the `build` and `publish` fields (that's what your `netlify.toml` is for). Then set your deploy branch (e.g., `main`).
Now each time you push to your deploy branch you'll also deploy your most recent changes. 🎉
## JavaScript
Adding JS is pretty straightforward, but has prescriptions on file structure & naming:
- All JS is processed through rollup with a basic Babel configuration using `preset-env`. Configure this and the accompanying `.browserslistrc` as you please.
- Any JS file _without_ an underscore prefix is treated as an asset (included in file output). Its file path is mirrored in the output.
- Any JS file _with_ an underscore prefix is treated as a non-asset module (no output file).