Skip to content

Three landing page directions to compare (draft, do not merge) - #24

Closed
drmowinckels wants to merge 1 commit into
mainfrom
landing-options
Closed

drmowinckels wants to merge 1 commit into
mainfrom
landing-options

Conversation

@drmowinckels

@drmowinckels drmowinckels commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

What this is

Not a proposal — a set of options to pick from. Three drafts of the landing page, each answering "people don't get what we are / what we do / how they can use us" differently in what the page leads with, not in styling.

Branched from main, so the preview also shows the current site for comparison. PR #23 (capability grid) is effectively a fourth option.

Leads with Best if
A — What are you stuck on? The visitor's problem, in their own words People arrive knowing their symptom, not our vocabulary
B — We have already done this Delivered work + researchers' own quotes Credibility is the blocker more than comprehension
C — One sentence One sentence, one action, one screen "Strip it to the essentials" is meant literally
PR #23 Six capability cards People want to scan the service menu

Index at /options/. Every page carries a bar linking the others and the current site, with its premise behind a "Why this one" disclosure.

Notes on each

A is the most direct answer to the actual complaint. Six first-person statements — "My analysis is too big for my laptop", "I'm writing a grant and need a data management plan" — each routing to the relevant service. No cards, no icons; the content is the interface. The risk: it only works if those six really are the ways people arrive. Worth checking against what you actually get asked.

B leans on the strongest asset the site already has and barely uses: the testimonials are specific and quantified ("thousands of brain MRI data sets", "over 27 000 respondents", "15 years of longitudinal collection"). Far better evidence than the counter cards were.

C is the literal reading of Markus's "strip the first page down to the essentials". One screen, four verbs, one booking link. The risk is the opposite of A's: it may be too little for someone deciding whether to spend budget.

Honesty note on B

My first draft paired the DRCMR and Barcelona quotes with the ggseg and Nettskjemar logos — projects those researchers have nothing to do with. That invents an association, so I rebuilt it: only the two cases with genuinely matching imagery get full treatment, the rest are plain quotes. If you want four image-led cases, we need four real images.

These are drafts

noindex, not in the nav or sitemap, no Norwegian yet. Copy is mine and unreviewed. Pick a direction first; polish and translation follow.

What I'd like back

  1. Which direction, or which parts of which.
  2. For A: are those six the real ways people arrive?
  3. Whether B's evidence-first framing fits how a UiO core facility should present itself.

🤖 Generated with Claude Code

Draft-only pages under /options/, noindex, not linked from the nav.
They exist to pick a direction, not to merge as-is.

Each answers the "people don't get what we do" problem differently, in
what the page leads with rather than in styling:

  A /options/a-stuck/     Lead with the visitor's problem in their own
                          words; six first-person statements that
                          self-route to the relevant service.
  B /options/b-receipts/  Lead with delivered work and the researchers'
                          own quotes, which are specific and quantified.
  C /options/c-sentence/  One screen, one sentence, one action. The
                          literal reading of "minimalistic".

Each page carries a bar linking the others plus the current site, with
its premise in a disclosure, so they can be compared in one sitting.

Only two of the quoted projects have imagery that genuinely belongs to
them, so B shows those two as full cases and the rest as plain quotes
rather than pairing quotes with unrelated project logos.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

✅ Preview deployed at https://24--capro-uio.netlify.app
Please check it looks ok before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant