Skip to content
All insights

Why underperformance is almost never a revenue problem

1 min read

This is a sample article, here so you can see how writing appears on the site. Delete this file and the Spanish one in content/insights/es/ once you publish something real.

To add an article, create a Markdown file in content/insights/en/ (or /es/). The filename becomes the web address, so opening-a-building-late.md becomes /en/insights/opening-a-building-late.

The header at the top of the file

Every article needs the block between the two --- lines:

  • title — what appears as the headline
  • summary — the sentence shown on the Insights index page
  • date — in YYYY-MM-DD form; the list sorts newest first

Writing the body

Ordinary Markdown works throughout. A ## line makes a section heading, a - makes a bullet, and text between ** comes out bold.

A pull quote looks like this, which is useful when you want one line to carry weight.

Links are written as text in square brackets followed by the address in round ones.

The two languages are independent

An article in content/insights/en/ appears only in the English section. There is no automatic translation — to publish in both, write both files. They do not need matching filenames, and you are free to publish something in one language only.

Have something that isn't working?