Deneb Jekyll documentation

Pages and sections

How pages are built from sections, every section type with its fields, and the data files behind them.

Home, About, Services, Pricing and Contact are made of sections. Each page lists its sections in its front matter, in order.

---
layout: page
permalink: /about/
title: About
eyebrow: About us
intro: A short line under the page title.
description: One sentence for search engines.
sections:
  - type: about
    title: We started Deneb to make agency work *simpler*
  - type: stats
    tone: alt
  - type: cta
    title: Want to work with *us*?
---

Page fields

Field What it does
layout home (sections only) or page (title band, then your text, then sections).
permalink The address of the page.
title The page title.
eyebrow Small text above the title in the title band.
intro The line under the title.
description The description for search engines.
hide_header true hides the title band on a page layout.
sections The list of sections.

Text you write below the front matter in a page layout shows between the title band and the sections.

Fields every section has

Field What it does
type The section type. Required.
tone alt for a soft grey background, dark for a navy panel. Leave out for the normal background.
id Adds an anchor, so a link can point to /page/#id.

Most sections also take eyebrow (small text above), title and text (a lead paragraph). Wrap words in the title in *stars* to give them the soft second colour: Services that help you *grow*.

Section types

hero

The home page opening, with a rolling word.

Field What it does
chip A small label above the title.
title The words before the rolling word.
roll A list of word and tone (blue, sky, green or coral). The first word shows without JavaScript.
text The paragraph under the title.
button, button2 Each has label and url.

logos

Client names from _data/clients.yml. Field: label.

services

Cards from the _services collection, sorted by order.

Field What it does
eyebrow, title, text The heading.
limit How many cards to show.
link label and url of the link below the cards. link: false hides it. The default goes to /services/.

about

A picture and text.

Field What it does
eyebrow, title, text The heading.
image, image_alt, image_label The picture, its description and the text on the placeholder.
checklist A list of short points.
button label and url.
reverse true puts the picture last.

stats

Up to four numbers from _data/stats.yml. Fields: eyebrow, title, text.

process

Up to four numbered steps from _data/process.yml. Fields: eyebrow, title, text.

projects

Cards from the _portfolio collection, sorted by order. Same fields as services: eyebrow, title, text, limit and link. The default link goes to /portfolio/.

testimonials

Quotes from _data/testimonials.yml.

Field What it does
layout featured (one big quote and a stack, the default) or grid.
limit How many quotes. Default 3.
eyebrow, title, text The heading.

pricing

Up to three plans from _data/pricing.yml. Fields: eyebrow, title, text, and flag (the text on the featured plan, default “Most popular”).

team

Up to four people from _data/team.yml. Fields: eyebrow, title, text.

faq

An accordion from _data/faq.yml, with FAQ markup for search engines.

Field What it does
limit How many questions.
id Needed if you use two FAQ sections on one page. The default is faq.
schema false leaves out the search engine markup. Use it when the same questions already appear on another section of the page.
eyebrow, title, text The heading.

cta

A dark band with a call to action.

Field What it does
title, text The heading and a line below it.
button, button2 Each has label and url.

contact

Your details and the contact form. The details come from the deneb: block in _config.yml. See Contact form. Fields: eyebrow, title, text.

posts

The latest blog posts.

Field What it does
limit How many posts. Default 3.
link_label The text of the link to the blog. Default “All posts”.
eyebrow, title, text The heading.

Use a section twice

You can use the same type more than once on a page. Give each copy its own id, so the anchors do not clash. For faq this is required.

Data files

Several sections read their content from _data/. Edit these files, and every page that uses the section changes.

File Fields of each item
team.yml name, role, image, image_alt, bio. The team section shows name, role and the picture.
testimonials.yml quote, name, role, company, rating (default 5).
pricing.yml A plans: list. Each plan has name, price, period, text, features, missing, featured and cta (label and url).
faq.yml q and a. The answer can use Markdown.
stats.yml value, suffix, label. The number counts up when it scrolls into view.
process.yml title and text.
clients.yml name.

In pricing.yml, features are listed with a tick, missing are listed as not included, and featured: true marks the highlighted plan.

Add a new page

  1. Copy about.md to a new file, for example studio.md.
  2. Change permalink, title, eyebrow, intro and description.
  3. Change the sections: list.
  4. Add the page to _data/navigation.yml. See Navigation.

Pages that are not built from sections

portfolio.md and blog/index.html list items from a collection, so they have no sections:. privacy.md is a plain page: write Markdown below its front matter.

The wording under service and project pages

Each service page ends with a “how we work” section and a call to action. Each project page ends with a call to action. Their wording is in _data/layout_sections.yml, under service_process, service_cta and project_cta.