An open API service indexing awesome lists of open source software.

https://github.com/terezaif/tereza-coaching

Landing page
https://github.com/terezaif/tereza-coaching

coaching landingpage website

Last synced: 5 months ago
JSON representation

Landing page

Awesome Lists containing this project

README

          

# T's Landing page

A simple landing page built with 11ty and Tailwind CSS.

> Port of the [Hugo Version](https://github.com/ttntm/hugo-landing-page)

[Template](https://github.com/ttntm/11ty-landing-page)

## Improving site response time

- Converting images to webp format with [https://convertio.co/](https://convertio.co/)
- Checking site response time with [https://pagespeed.web.dev/](https://pagespeed.web.dev/)
- Check if site is green hosted and report [https://ecograder.com/report/oj0ARJZa4zczobd8yhtAAzY3](https://ecograder.com/report/oj0ARJZa4zczobd8yhtAAzY3)
- All about favicons [https://evilmartians.com/chronicles/how-to-favicon-in-2021-six-files-that-fit-most-needs](https://evilmartians.com/chronicles/how-to-favicon-in-2021-six-files-that-fit-most-needs)
- More on site sustainability [https://sustainablewebdesign.org/is-the-content-easy-to-find/](https://sustainablewebdesign.org/is-the-content-easy-to-find/)

## How to use this template

**Requirements:**

1. Eleventy (developed and tested with version 0.12.1)
2. Tailwind CSS

All other dependencies are either linked from a CDN or included in this repository.

**Setup:**

1. Fork, clone or download
2. `cd` into the root folder
3. run `npm install`
4. run `npm run serve`
5. open a browser and go to `http://localhost:8080`

**Basic configuration:**

1. Eleventy -> `./.eleventy.js`
2. Tailwind -> `./tailwind.config.js`
3. Netlify -> `./netlify.toml`

CSS is built via PostCSS and based on `./src/_includes/css/_page.css`. Building CSS gets triggered by `./src/css/page.11ty.js` and Tailwind's config is set to JIT (see: [Tailwind docs](https://tailwindcss.com/docs/just-in-time-mode))

Please note that this CSS build _does not_ include the `normalize.css` file used for the 2 regular pages (imprint, privacy) - a minified production version is stored in `./src/static/css` and gets included in the build by default.

**Change Content:**

Page content is stored in

- `./src/`
- `imprint.md`
- `privacy.md`
- `./src/sections/`
- `./src/_data/features.json`

**Change Templates/Layout:**

Page structure and templates are stored in `./src/_layouts/` and can be edited there.

Best have a look at `./layouts/base.njk` first to understand how it all comes together - the page itself is constructed from partial templates stored in `./src/includes/` and each section has a corresponding template file (`section.**.njk`) stored there.

`index.njk` in `./src/` arranges everything, meaning that sections can be added/re-ordered/remzoved/... there.

**Change images:**

Images are stored in `./static/img/`; everything in there can be considered a placeholder that should eventually be replaced with your actual production images.