From 309e3b43df7faa5713c2648c36ce237ac84edc9f Mon Sep 17 00:00:00 2001 From: Bendik Aagaard Lynghaug Date: Wed, 12 Aug 2026 23:26:10 +0200 Subject: [PATCH] Voice: bold statements, argued alternatives, no questions below the title - The page title is the only question anywhere; alternative and feature names are now statements in our voice. Where we need input we say why (the reply is personal, software lands somewhere, a proposal is a stance), then hand over the field. - The opening question's alternatives become the statements we'd like visitors to get behind: "Good software begins with a clear argument", "Attention is earned", "Capital needs reasons", "Work happens through dialogue, not tickets". - followup: true on the five post-submission pages keeps them out of the question nav until the visitor actually carries a chain. Co-Authored-By: Claude Sonnet 5 --- questions/applied.yaml | 1 + questions/develop-proposal.yaml | 10 ++++--- questions/index.yaml | 48 ++++++++++++++++++--------------- questions/invest.yaml | 12 +++++---- questions/invested.yaml | 1 + questions/project.yaml | 1 + questions/proposed.yaml | 3 ++- questions/subscribed.yaml | 1 + 8 files changed, 46 insertions(+), 31 deletions(-) diff --git a/questions/applied.yaml b/questions/applied.yaml index 109cc1e..8ff67ec 100644 --- a/questions/applied.yaml +++ b/questions/applied.yaml @@ -1,5 +1,6 @@ id: /applied route: ^/applied +followup: true name: What happens now that you've applied? description: > We're not filling a seat — we're looking for exactly what you bring diff --git a/questions/develop-proposal.yaml b/questions/develop-proposal.yaml index 0b8e49b..99e05bc 100644 --- a/questions/develop-proposal.yaml +++ b/questions/develop-proposal.yaml @@ -7,7 +7,7 @@ description: > should change and why; an owner reviews every proposal, and approved ones become real commits. alternatives: - - name: What should change? + - name: The change you propose description: > The proposed content replaces (or creates) one file in the questions repo, verbatim — so it has to be complete, valid YAML @@ -18,8 +18,10 @@ alternatives: encouragements: - Every proposal gets read by a person before anything moves. features: - - name: Who's proposing? - description: "" + - name: Sign it + description: > + A proposal is a stance — it carries a name, and an address + if you want the outcome to reach you. requirements: - name: submitted_by label: Name (or what to call you) @@ -34,7 +36,7 @@ alternatives: label: File path placeholder: questions/example.yaml - name: rationale - label: Why this change? + label: The rationale type: textarea - name: proposed_yaml label: Proposed file content (complete YAML) diff --git a/questions/index.yaml b/questions/index.yaml index f718013..9704677 100644 --- a/questions/index.yaml +++ b/questions/index.yaml @@ -6,10 +6,10 @@ responsible: name: bl contact: bl@uhhm.no alternatives: - - name: I want something built + - name: Good software begins with a clear argument description: > - Infrastructure, tools, or a product — we read the whole brief - before answering. + Infrastructure, tools, or a product — bring the problem, and we + read the whole brief before answering. action: /project consequence: [Tell us what you're after] record_as: projects @@ -26,8 +26,11 @@ alternatives: jq: > .[] | {name: .name, description: .description, url: .html_url, stars: .stargazers_count} - - name: What are you after? - description: A few lines are enough to begin a conversation. + - name: Your brief + description: > + A few lines are enough to begin a conversation — we need a + name and an address because the reply is personal, and the + organization because software always lands somewhere. requirements: - name: name label: Name @@ -35,17 +38,16 @@ alternatives: label: Email type: email - name: project - label: What do you need built? + label: The build type: textarea placeholder: Just the shape of it — we'll ask the right questions. - name: organization label: Organization - placeholder: Who's this for? - name: org_contact - label: Best way to reach them, if not you + label: Their contact, if not you optional: true - - name: Keep me posted + - name: Attention is earned description: > Considered notes on what we're building, and why — sent only when there's something worth saying. @@ -64,36 +66,40 @@ alternatives: label: Email type: email - - name: Managing capital? + - name: Capital needs reasons description: > - Then you're accountable for reasons, not enthusiasm. Ours are - written down — qualities you can test against your own. + Whoever manages it is accountable for them — enthusiasm doesn't + qualify. Ours are written down, as qualities you can test + against your own. action: /invest - consequence: [How do we invest in uhhm?] + consequence: [Read our reasons] - - name: I want in + - name: Work happens through dialogue, not tickets description: > - We onboard collaborators the same deliberate way we build — - by hand, through a real conversation. + What you bring shapes what gets built. We onboard collaborators + the same deliberate way we build — by hand, through a real + conversation. action: /applied consequence: [Apply] record_as: applicants encouragements: - Knock — we actually answer. features: - - name: Who are you? - description: "" + - name: A way to reach you + description: The reply is personal — it needs a name and an address. requirements: - name: name label: Name - name: email label: Email type: email - - name: What draws you here? - description: "" + - name: Your angle + description: > + We build around what each person actually brings — say what + that is, in your own words. requirements: - name: interest - label: What do you want to work on? + label: The work you're drawn to type: textarea - name: note label: Anything else worth knowing diff --git a/questions/invest.yaml b/questions/invest.yaml index cb4a282..5789f9d 100644 --- a/questions/invest.yaml +++ b/questions/invest.yaml @@ -39,17 +39,19 @@ alternatives: encouragements: - Serious inquiries get a serious answer. features: - - name: Who are you? - description: "" + - name: A way to reach you + description: Dialogue needs a counterpart — the reply is personal. requirements: - name: name label: Name - name: email label: Email type: email - - name: What brings you here? - description: "" + - name: Your criteria + description: > + We answer against what you're actually accountable for — so + state it plainly. requirements: - name: motivation - label: What are you looking for in an investment? + label: Your criteria for a good investment type: textarea diff --git a/questions/invested.yaml b/questions/invested.yaml index 3bea5df..0197e8b 100644 --- a/questions/invested.yaml +++ b/questions/invested.yaml @@ -1,5 +1,6 @@ id: /invested route: ^/invested +followup: true name: What happens now? description: > Your interest is on its way to a real inbox. Expect a considered, diff --git a/questions/project.yaml b/questions/project.yaml index 81b1615..cb3ce10 100644 --- a/questions/project.yaml +++ b/questions/project.yaml @@ -1,5 +1,6 @@ id: /project route: ^/project +followup: true name: So, what happens now? description: > That's on its way to a real inbox. Expect a considered reply within a diff --git a/questions/proposed.yaml b/questions/proposed.yaml index 058254a..ebb6eef 100644 --- a/questions/proposed.yaml +++ b/questions/proposed.yaml @@ -1,12 +1,13 @@ id: /proposed route: ^/proposed +followup: true name: Proposal received description: > It's in the queue. An owner reads every proposal in full — approved ones open a real pull request, and the same checks every human commit passes gate the merge. alternatives: - - name: What happens now + - name: The path from here description: "" features: - name: A person decides diff --git a/questions/subscribed.yaml b/questions/subscribed.yaml index 4b18b4e..4927821 100644 --- a/questions/subscribed.yaml +++ b/questions/subscribed.yaml @@ -1,5 +1,6 @@ id: /subscribed route: ^/subscribed +followup: true name: What should you expect? description: > We'll write when there's something worth your time — that's the