Author / E-E-A-T pages with verifiable credentials

[rubenvdlinde]

Part of #75 (SEO epic).

What

Create author pages for the Conduction team at https://www.conduction.nl/about/team/<slug> with named authors, LinkedIn links, GitHub profiles, role descriptions, and (where applicable) named municipal customer engagements. Wire author bylines into per-app docs site frontmatter so the TechArticle JSON-LD ships real authors instead of the "Conduction Organization" fallback.

Why

The March 2026 Google core update amplified the "Experience" E in E-E-A-T. Content with named human authors, real credentials, and verifiable customer stories outranks generic technical writing for the same keywords. For Conduction's audience (Dutch municipalities, government procurement), this means: case studies with named municipalities, named team members who deployed there, named DPIA processes you've completed.

The preset's TechArticle swizzle already accepts frontmatter.author: per docs page; today most pages have no author set so the schema falls back to {"@type": "Organization", "name": "Conduction"}. Hand-crafted author objects with url (LinkedIn or team page) + jobTitle would activate the Experience signal.

Scope

1. Build /about/team/ on conduction-website. List + per-person detail pages. Estimate 8–12 team members.
2. Per-person page content: name, role, photo, LinkedIn, GitHub, areas of expertise, named deployments / contributions (where consent + privacy allow).
3. Wire per-doc author bylines on at least the top 5 pages of each per-app docs site (those that the team actually wrote).

Approach

• One Person schema per team member, with sameAs: [LinkedIn URL, GitHub URL, ORCID if any]
• Cross-link from each per-app docs site to the relevant author page on conduction.nl
• Docs frontmatter: author: { name: "Ruben van der Linde", url: "https://www.conduction.nl/about/team/ruben" }

Acceptance

• /about/team/ list page exists
• At least 8 named team members with detail pages
• At least one verifiable credential per person (LinkedIn URL minimum)
• At least 5 docs pages per app site carry a named author byline
• Validator: docs/structuredData/TechArticle has author.@type === 'Person' on at least one page per site