Table of Contents
- Prerequisites
- Stack
- Running locally
- Adding new content
- Previewing the production build
- Styling with TailwindCSS
- Eleventy for templates and site generation
- Tailwindcss for a utility first CSS workflow
# install the project dependencies
npm install
# run the build and server locally
npm run watch
Add a new markdown file to src/site/blog
. Make sure it has the
following metadata at the top of the file. To make things easy on yourself, duplicate an existing post.
---
title: 'Post title'
subtitle: 'Post subtitle (if any)'
date: 2020-02-03T23:00:00
tags: ['post', 'announcements']
authors: ["first-last", "first-last", "first-last"]
description: |
A description that is used in snippets.
---
The authors field can hold more than one author and is the name of the json
file for the specific author in _data/team
.
Make sure to add a description
to your post for the main pages as well as social
media cards.
Add a json file to _data/team
in the following format:
{
"weight": 1,
"name": "Jessie Frazelle",
"title": "CPO",
"twitter": "jessfraz",
"github": "jessfraz",
"linkedin": "https://www.linkedin.com/in/jessie-frazelle/",
"blog": "https://jess.dev"
}
Then add an entry to the ordered list in _data/team/members.json
.
When building for production, an extra build step will strip out all CSS classes not used in the site. This step is not performed during the automatic rebuilds which take place during dev.
# run the production build
npm run build
This site uses TailwindCSS to offer utility CSS classes and provide a rapid means to styling the site. This means that most styling can be done without writing any additional CSS. Instead, utility classes can be added directly to the HTML. This may not be to everyone's tastes, but it can provide some very rapid development and also offer surprising levels of familiarity for those used to working in this way (since the conventions and classes are not per site.)
While running/developing locally, the npm run start
command will recompile the site as files are saved and this includes the CSS pipeline from Tailwind.
A small number of bespoke CSS rules are provided for efficiency of repeated or global classes. These reside in src/site/_includes/css/tailwind.css