Postlight's Liftoff is a nifty tool that lets you easily create a static website that displays content in Airtable base and style it with custom CSS. Read all about it in this handy introduction.
This README goes pretty in depth with how to set up this project on your computer. Here are the basics in case you want to jump right in. You'll likely want to skim through other parts of this document as you go, but this will get you started!
- Create an Airtable base if you haven't already.
- Clone this repo:
git clone git@github.com:postlight/liftoff.git. - Run
yarn installto install dependencies. - Run
yarn setupfor a walkthrough on setting environment variables. - Run
yarn run start:devto start up the webpack dev server. - Make changes to your Airtable base.
- Style your site.
- Deploy your site.
- Getting Started
- Setting up your Airtable base
- Development
- Styling
- Pagination
- Custom renderers
- Build
- Deploying your site
- Example sites
If you're familiar with git, you can go ahead and clone this repo the normal way.
If not, you can download a Zip file of this repo by clicking on the button shown here near the top of this page:
This project uses Yarn to download and manage copies of the third party code we used to build it. If you already have Yarn installed, you can skip to the next section. Otherwise, you can follow the instructions here to install it for macOS or here to install it for Windows.
If you're a Mac user, you may want to install Homebrew if you haven't already. Homebrew is a package manager that will allow you to easily download, install, and manage software such as Yarn. You can follow the instructions on the Homebrew website or you can install it from the command line by:
- Opening up a terminal window via the "Terminal" application
- Copy and pasting the following into the terminal window and hitting Enter/Return
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
After the installation completes, you can then open a new terminal window (Cmd+T works) and run brew install yarn to install Yarn.
When that's done, open up another terminal window and run yarn install. This will download the 3rd party code this project needs in order to work.
This project uses environment variables to store credentials such as your Airtable API key, so we'll need to set those up before we can move onto more exciting things. Luckily, setting them up is simple.
All of the environment variables we need to set up can be found by going to the right place on the Airtable website.
From your terminal, run:
yarn setupThis script will walk you through each step of the process. Simply follow the instructions, enter the value the prompts ask you for, and press enter to move on to the next step. If you want to change an environment variable after the fact, you can directly edit the .env file in the root directory of your project, or you can run yarn setup again.
This project currently supports most but not all Airtable field types. The only field types it doesn't currently support are "Link to another record", "Barcode", and "Collaborator". For "Attachment" types, it currently only supports image files.
You have two options for determining which rows are published. By default, all rows visible to an Airtable view will be published. If you want, however, you can add a Published checkbox column to your table. Any row that doesn't have a checkmark in that field will not be displayed on your site. This makes it easy to create drafts of your rows before publishing. Remember: If you don't include this field, every row will be displayed by default.
A slug is a unique ID that represents a resource in a URL. If you have a website called website.com with an article on it called "What Is a Website?", for instance, you might want that article's page to look something like website.com/what-is-a-website.html to make it readable and easy to remember. You can specify slugs in your site by adding a Slug column to your Airtable table and populating it in each row with your desired slug. Note that slugs cannot contain spaces, so you must use - or _ to separate words. You don't need to include .html in your slug—that will be handled automatically.
Entering yarn run start:dev into a terminal window will fire up a server that will allow you to view your site and style it in real time. Each time you save after editing CSS or custom renderers (more on these below), your work will be automatically reflected in the browser.
Any CSS put in the styles.css file at /custom/styles.css will be injected into your site for styling purposes.
Your field names will always be added as classes in the corresponding HTML. So for example, a field called "Title" will generate an HTML element with the class .Title. There are other classes that are put in by default, detailed below. You can make use of these classes to style the site to your liking.
Out of the box, we've provided some boilerplate styling that we hope will help ease the styling process - to remove, simply remove the unwanted css from /public/default.css. To view the boilerplate designs, click here.
Pagination is automatically implemented on any site with more than 10 posts. This makes back + next buttons available on the homepage of your site for navigating between different pages of posts.
.attachments: placed on attachment-type fields.field-name: placed on the element containing the name of each field; by default, field names are hidden.field-value: placed on the element containing the value of each field.row-link: placed on each row on the homepage.row: placed on each row.header: placed on the header.index-pageplaced on an element that wraps the homepage.nav-buttonplaced on back/next navigation buttons
Using a combination of the classes defined by your table's fields and these default classes, you should be able to accomplish just about any styling needs you have.
You can include a favicon for your website by putting a favicon.ico image file in the /custom directory. It must conform to favicon specifications, meaning it should be a .ico file and should be 16x16 or 32x32 pixels in size.
If you're comfortable writing React, you may find yourself wanting to write a custom component to render one of your fields. Luckily this is easy to do!
To add a custom renderer for one of your fields, create a React component that accepts name and value as props in the custom/renderers folder, then import and export it in custom/renderers/index.js. The name of the file and component must match the name of the column you would like it to serve as renderer for. If the name of your column includes spaces, do not include the spaces in the name of the corresponding file and component. So a custom renderer for a column called "Body Text" should be a React component called BodyText in a file called custom/renderers/BodyText.js and exported from custom/renderers/index.js as such.
For example:
// in ./custom/renderers/BodyText.js
import React from "react";
const BodyText = ({ name, value }) => {
return (
<div>
The name of this field is {name}; its value is {value}
</div>
);
};
export default BodyText;Running yarn build in a terminal window will execute a build script that will generate your site. The generated site will live in the /dist folder.
After you build your site, you can deploy it anywhere that you can serve static HTML.
One service we often use at Postlight is Netlify. You can follow instructions on their site to get your site up and running—the main things you need to remember for this process are that the folder you want to deploy is /dist and the command you need to run to build the site is yarn build.
To set your environment variables on Netlify, you will have to input them manually by going to the Setting tabs from the Netlify page for your website and clicking on "Build & deploy" in the sidebar. Now scroll down a little to the "Build environment variables" section and copy in your environment variables from your .env file as set up above. When you've finished, it should look something like the following:
We've prepared two example sites for you to get an idea of what this tool makes possible. The first is a reimagining of Postlight's blog site, Track Changes, which you can see at https://track-changes-demo.netlify.com. This site showcases pagination, a lot of custom CSS, and markdown support, as you can see in the body of some of the articles. The second site is a fake blog for pizza enthusiasts, located at https://roni-rony-rone.netlify.com. This site highlights more custom CSS as well as custom React renderers, including one that lets you copy and paste a Google Maps embed code into your Airtable row and see it on your webpage, and another that does the same for Spotify playlist links.
You can see the code we wrote for the Track Changes site here, and you can see the code we wrote for the pizza blog site here.
Licensed under either of the below, at your preference:
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
For details on how to contribute, see CONTRIBUTING.md
Unless it is explicitly stated otherwise, any contribution intentionally submitted for inclusion in the work, as defined in the Apache-2.0 license, shall be dual licensed as above without any additional terms or conditions.
🔬 A Labs project from your friends at Postlight. Happy coding!