Block A: the landing surface, before any more outreach — six frameworks work and four are named, and the home page is still histoire's

[50rayn]

Poveste has been on npm for 25 days and, until 10:29 UTC this morning, had never been mentioned anywhere outside this repository. This issue is the sequence that changes that, and the evidence for why it comes before more features.

The download data says what you would expect, and it is worth stating plainly

Daily downloads since the first publish on 3 August:

day		day
08-03 first publish	134	08-19	31
08-04	446	08-20	156
08-05	63	08-23	4
08-09	2	08-24	4
08-12	797	08-25 0.6.1	329
08-17	2	08-26 0.7.0 0.8.0	353

Every peak lands on a release day. The floor on a quiet day is 2–11, and that floor is the only external signal in the series — the rest is our own CI: the smoke test, test:starters, example installs.

This is not an adoption failure. Adoption has not been attempted. One act of outreach exists in the project's history and it is five hours old (histoire#105). The number to draw conclusions from does not exist yet.

What the data does establish is that we spent the last two days making the release machinery excellent — three releases, a gate correct in all three directions it can be wrong — while the project remained impossible to evaluate. That is the thing to fix, and none of it needs a release.

The sequence

Ordered by what a stranger hits first, not by size.

1. #402 — the organisation. No name, no description, no website. Someone arriving from an upstream thread checks the org to decide whether this is a real project or one person's weekend. Cheapest item here and the first impression.

2. #403 — say which frameworks work. Six have an example book, a CI job and a required check. The repo description, the topics, the docs framework chooser and the starter count name four. Quasar is missing from all of them, five hours after ten people were pointed at it by name. SvelteKit is missing too.

3. #291 — the docs home page is histoire's. Identical tagline, identical meta description, identical five feature bullets. The literal front door says nothing about what this project is or why it exists.

4. #390 — the docs front door. An indexed orphan page, a framework chooser that omits SvelteKit, and a feature list still inherited.

Why this order and not another

It reaches people without a release. Repository settings, organisation settings and the docs site all take effect on merge to main — no version, no changelog, no publish. Every other block on the board waits for a release to matter.

It is the precondition for the outreach that is already earned. #372 has found four upstream threads asking "is this maintained?" carrying 43 upvotes between them, none ever answered by a maintainer. That is the largest concentrated audience for poveste anywhere. Posting to them before the landing surface is fixed spends the audience on a page that does not say what this is.

And it is falsifiable. Check downloads again in a week, not tomorrow. If the floor is still 2–11 after the landing surface is fixed and the threads are answered, the problem is the product and not its presentation — and that is worth knowing.

Not in scope

The rest of The public face, and everything in What the docs claim and The way in. Those matter and they are not what a first-time visitor hits.

[50rayn]

Added A5 — #449: a public roadmap board that maintains itself.

It sits after A1–A4 deliberately. A public board pointing at a repository with no description, no topics and histoire's home page does not help — it just makes the gap visible from one more angle.

Two things the investigation turned up that change the framing:

The existing board is not abandoned, it is finished. Poveste Launch holds issues #1–#15, fourteen closed and one open. It was a launch board for a launch that happened, left private afterwards. So the task is to close it out and build the thing it was never trying to be — not to revive it.

It belongs in Block A on the same logic as #402 and #291. The four threads in #372 ask is this maintained? and carry 43 upvotes. A board showing eleven issues closed in the last two days answers that structurally; a sentence claiming the project is active is exactly what a reader discounts.

The issue also records two non-goals with reasons — no milestone due dates (they would recreate the churn that made us strip version numbers), and no reproducing the reasoning on the board (state and judgment drifting apart is a failure this repo has already hit twice).

[50rayn]

Step 3 (#291) and step 4 (#390) are done, with the docs half of step 2 (#403), in #450 — green, unmerged. The home page leads with the position the repo description already commits to, the chooser names all five frameworks, and docs/new.md is gone.

The rest of this block is account settings rather than code, so it wants a person's hand. Exact text, ready to paste.

Repo description (#403)

Currently:

📖 Fast and beautiful interactive component playgrounds — a maintained, drop-in successor to histoire. Vue, Svelte, Nuxt.

Proposed — the only change is the framework list, which is missing two that have books, jobs and plugins:

📖 Fast and beautiful interactive component playgrounds — a maintained, drop-in successor to histoire. Vue, Nuxt, Svelte, SvelteKit, Quasar.

Repo topics (#403)

Currently eight: component-explorer histoire nuxt stories storybook svelte vite vue

Add: sveltekit, quasar. Both are searched by name by exactly the people this project is for, and both are supported targets today.

Org profile (#402)

Every field is null, so github.com/poveste-dev renders as a bare slug — the page reached from the repo's owner link and from every npm package page.

field	value
name	Poveste
description	Interactive component playgrounds for Vue, Nuxt, Svelte, SvelteKit and Quasar — a maintained, drop-in successor to histoire.
website	https://poveste.dev

Also worth doing while in there, from #402: verify the domain — poveste.dev is owned and already serving, and verification is what ties the org and the packages together publicly. The security defaults for new repositories (secret scanning, push protection, Dependabot alerts) are all off; they cost nothing to turn on and only apply going forward.

I have not touched any of these. They are outward-facing account changes, and the org profile in particular is the thing #372 asks about — whether this reads as a real project — so it should say what you want it to say, not what I guessed.

What is left in this block after that

Nothing. #291, #390 and the docs half of #403 land with #450; the settings above finish #402 and #403. None of it needs a release — the docs deploy from main and the settings take effect immediately.

[50rayn]

Progress: three of five closed in under two hours. #291, #390 and #403 all went in PR #450.

Remaining: #402 (the organisation has no name, description or website) and #449 (A5, the public board).

One correction raised on #450 before this reaches main: the new hero says "still maintained" and "a drop-in successor to histoire", both of which assert that histoire is not maintained — which #372 established this morning is false. Nothing is live yet, so it is a copy change rather than a retraction.