Skip to content
VendorFinder

Collections

Articles

Vendor-written thought leadership, guides, and industry analysis published at /articles/[slug].

Articles are long-form analysis, guides, and opinion pieces written by vendors and service providers for business buyers. Credit the company with organizations: [company-slug] so the piece appears on its profile.

Files live in content/articles/. The filename becomes the URL in lowercase: Digital-Platforms-Reshape-Sports-Fandom.md → /articles/digital-platforms-reshape-sports-fandom.


How an article page is laid out

  1. Category, title, subtitle, byline, date, and reading time
  2. Portrait image — or, when there is none, a generated VendorFinder card
  3. Idea in short box (prologue)
  4. Frequently asked questions (faq)
  5. The article body
  6. Summary box (epilogue)
  7. Sources — the citations written as <footnotes> in the body
  8. Author box and share links

Frontmatter Fields

Field Type Required Notes
title string Yes Max 100 characters.
subtitle string Recommended Shown under the headline. Also the meta description for search results, unless description is set. Max 200.
summary string Recommended Short excerpt shown on article listing cards and used as the image alt text. Max 300. At least one of subtitle, summary, or description is required.
description string No Overrides the meta description. Max 200.
prologue string No Text of the Idea in short box above the body. Separate paragraphs with a blank line.
epilogue string No Text of the Summary box after the body.
publishedAt date Yes DD-MM-YYYY hh:mm AM in Europe/Berlin time, e.g. "22-09-2026 08:00 AM". ISO dates (2026-09-22) also work. Shown on the site as DD-MM-YYYY.
updatedAt date No Same format as publishedAt.
status yes / no No yes publishes the article, no keeps it as a draft. Overrides draft.
portrait string No Filename of the hero image in public/images/articles/, e.g. "My-Article.webp". When missing (or the file doesn’t exist), a generated VendorFinder card is used. Also used as the social share image.
portraitAlt string No Alt text for the portrait. Defaults to summary.
authors slug[] Yes People from content/authors/, e.g. editorial-team.
organizations slug[] No Companies credited on the article; it then appears on their profiles.
category string Recommended One of the names in content/taxonomy/article-categories.md (case-insensitive). A new name is added to that file automatically on the next build or dev-server start.
tags string[] No Topic tags. Also used as structured-data keywords.
type Product / Service Recommended What the article is about: Product for software, hardware and tools; Service for agencies, advisors, lenders, brokers and programmes.
gated yes / no No yes asks readers to confirm they are 18 or older before the article is shown. Use for content that may not be suitable for minors. Default no.
featured yes / no No yes pins the article to the featured section of /articles. Default no.
faq Markdown No Questions as ## headings, each followed by its answer (see the template). Rendered after the Idea in short box and published as FAQPage structured data for search and AI engines.
toc boolean No false hides the table of contents.
locale en No Default en; English is the only supported language.
uid string No Stable id for <PostLink uid="...">.

Citations

Cite a source inline by wrapping a link in <footnotes> right after the sentence it supports:

...nearly matches live viewing itself.<footnotes>[Nielsen: Consumer behavior shifts](https://www.nielsen.com/...)</footnotes>

Each citation becomes a small numbered reference, and the links are listed in order under Sources at the end of the article. Citing the same URL twice reuses its number.


FAQ guidelines

The FAQ is written for search engines and AI assistants as much as for readers, so:

  • Phrase each heading as the question a reader would actually type or ask.
  • Answer in the first sentence, then add one or two sentences of context. Keep answers self-contained — they are often quoted on their own.
  • Keep figures consistent with the article body and its sources.
  • 5–10 questions is plenty.

Template

---
title: ""
subtitle: ""
summary: ""
prologue: ""
epilogue: ""
publishedAt: "DD-MM-YYYY 08:00 AM"
status: yes
portrait: "Article-Title.webp"
authors:
  - author-slug
category: ""
tags: []
type: "Service"
gated: no
featured: no
faq: >
  ## First question a reader would ask?

  Direct answer in the first sentence, then brief context.

  ## Second question?

  Answer.
---

Opening paragraph.

## First section

Body text with a citation.<footnotes>[Source title](https://example.com/source)</footnotes>

## Second section

Body text.