Humbly upgraded 11ty starter
https://aloxe.codeberg.page/huwindty/
- Nunjucks 53.8%
- HTML 33.7%
- CSS 8.7%
- JavaScript 3.8%
|
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Bumps the npm_and_yarn group with 1 update in the / directory: [minimatch](https://github.com/isaacs/minimatch). Updates `minimatch` from 3.1.2 to 3.1.5 - [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md) - [Commits](https://github.com/isaacs/minimatch/compare/v3.1.2...v3.1.5) Updates `minimatch` from 10.2.0 to 10.2.4 - [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md) - [Commits](https://github.com/isaacs/minimatch/compare/v3.1.2...v3.1.5) --- updated-dependencies: - dependency-name: minimatch dependency-version: 3.1.5 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: minimatch dependency-version: 10.2.4 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|---|---|---|
| .github | ||
| src | ||
| .editorconfig | ||
| .eleventy.js | ||
| .gitignore | ||
| .woodpecker.yml | ||
| LICENSE | ||
| lighthouserc.js | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
huwindty 🌬️
A simple 11ty starter project to create a static site using Eleventy and Sveltia CMS with Tailwind CSS. It handles automatic navigation menus, SEO meta tags, and responsive images.
Introduction
I wanted to use Windty for my next eleventy project before I realised I need more than just a single page with Tailwindcss. So I kept the good work and added more.
What was added
Continuous Integration
- Publication to GitHub or Codeberg Pages
- Deployment to standalone server via SSH (manual action)
Styles
- Tailwind CSS is processed directly by 11ty
Navigation
- The navigation menu is generated from the page structure
Site output
- Render markdown with styles
- Process images to make them responsive
- Render "SEO" meta tags on all pages
Content Management System
- Installed Sveltia CMS for online editions
- Possibility to use Decap CMS with the same config
- Manage metadata and images on a per-page basis
Documentation
- Documentation comes with the starter as an example
- Explains how features are developed
Installation
with Codeberg
- Fork huwindty onto your account. Use links or type
git clone git@codeberg.org:aloxe/huwindty.git - Install dependencies:
npm install - Start development:
npm start - Check your website at http://localhost:8080/
- Build the release version with
npm run buildand check the result in_site. - When ready, push your changes to your repo on Codeberg and the action will publish it to Codeberg pages.
- Sveltia CMS needs specific configuration for editor authentication.
With github
- Create a new repository from huwindty’s template, or clone huwindty on your account. Use links or type
git clone git@github.com:aloxe/huwindty.git - Install dependencies:
npm install - Start development:
npm start - Check your website at http://localhost:8080/
- Build the release version with
npm run buildand check the result in_site. - When ready, push your changes to GitHub and the action will build and publish your site to GitHub Pages or the server of your choice via SSH (needs configuration).
- Sveltia CMS needs specific configuration for editor authentication.