Build with Jekyll
Create a Jekyll site from an Azion template or with the Azion CLI, and deploy it to an Azion domain.
You can deploy a Jekyll site on Azion from a template in Azion Console or with the Azion CLI. Both routes give you a Jekyll site that runs on Azion and answers on an Azion domain.
Azion serves a Jekyll site as a static application. The project configuration uploads the ./_site folder to a storage bucket, and an application serves the files from that bucket. For the other frameworks Azion builds, refer to Frameworks compatibility.
Prerequisites
Console
- An Azion account. To create one, refer to Create an account.
- Access to Azion Console. To sign in, refer to How to access Azion Console.
- A GitHub account. The template deploy asks you to connect it.
Jekyll templates
Each template is a Jekyll project that Azion deploys for you. The Console route starts from one of these templates:
| Template | Use |
|---|---|
| Jekyll Boilerplate | Starter project |
| Jekyll Cart | Shopping cart |
| Supply | E-commerce |
Jekyll Cart and Supply share one guide. For more information on templates, refer to Azion Marketplace. In the CLI route, the template picker of azion init lists the same three templates.
Deploy the site
Each route builds the Jekyll project and creates the resources that serve it on Azion. Use the panel of your route:
Console
To deploy a Jekyll template from Azion Console:
Access Azion Console > Create > Templates.
In Search by name, framework, or keyword, enter Jekyll.
When the form shows GitHub Connection, select Connect with GitHub. Then install the Azion GitHub App.
In Git Scope, select the scope of the template.
The deploy page opens and shows the Deploy Log during the build. After a successful deploy, the page shows Successfully created!, the domain URL, and a Manage button that opens the application.
Check the site
The deploy gives you the URL of the site’s Azion domain, in the form https://xxxxxxxxxx.map.azionedge.net. The Console deploy page shows the URL, and azion deploy prints it at the end. Open the URL in a browser to see the Jekyll site.
The first deploy can take several minutes to answer from every location; later deploys take about two minutes. A location that does not have the site yet answers with a 404 page that reads There's nothing here yet. If you get this response, wait and request the URL again.