docpensieve 0.3.0 → 0.4.0-beta.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docpensieve",
-  "version": "0.3.0",
+  "version": "0.4.0-beta.1",
   "description": "DocPensieve command-line interface (init, build, check, dev, serve)",
   "type": "module",
   "license": "MIT",
@@ -24,10 +24,10 @@
     "types"
   ],
   "dependencies": {
-    "@docpensieve/components": "0.3.0",
-    "@docpensieve/core": "0.3.0",
-    "@docpensieve/shared": "0.3.0",
-    "@docpensieve/theme": "0.3.0",
+    "@docpensieve/components": "0.4.0-beta.1",
+    "@docpensieve/core": "0.4.0-beta.1",
+    "@docpensieve/shared": "0.4.0-beta.1",
+    "@docpensieve/theme": "0.4.0-beta.1",
     "chalk": "^6.0.0",
     "chokidar": "^5.0.0",
     "commander": "^15.0.0"

package/starter/01-guide/01-installation.md

@@ -99,9 +99,9 @@ The documentation `init` installed in `99-docpensieve` stays at the version it
 came with. To refresh it, run `init` in a scratch folder and copy that folder
 over.
 
-Coming from the 0.2, [Migrate from 0.2 to 0.3](./migrate-from-0-2/) says what
-changes on its own and what to check first. To try the version being prepared,
-install `docpensieve@beta`, or run `npx docpensieve@beta` alone.
+Coming from the 0.3, [Migrate from latest to beta](./migrate-to-beta/) says
+what changes on its own and what to check first. To try this beta, install
+`docpensieve@beta`, or run `npx docpensieve@beta` alone.
 
 ## Checking
 

package/starter/01-guide/07-migrate-to-beta.md

@@ -0,0 +1,24 @@
+---
+title: Migrate from latest to beta
+description: Move a project from the latest version, the 0.3, to the 0.4 beta — what changes on its own, and what to check.
+tags: [guide, migration]
+---
+
+# Migrate from latest to beta
+
+A project on the latest version — the 0.3 — builds with the 0.4 beta as it is:
+every new field is optional.
+
+## Update
+
+```bash
+npm install docpensieve@beta
+```
+
+Through `npx` alone, `npx docpensieve@beta` runs the beta. Going back is
+`npm install docpensieve@latest`.
+
+## What changes on its own
+
+Nothing yet: the 0.4 has just opened. Each change is listed here as it lands,
+beside what it asks of a project already built on the 0.3.

package/starter/05-whats-new.md

@@ -1,61 +1,28 @@
 ---
-title: What's new in 0.3
-description: What the 0.3 brings, and what it changes for a 0.2 project.
+title: What's new in 0.4
+description: What the 0.4 brings, and what it changes for a 0.3 project.
 tags: [release]
 ---
 
-# What's new in 0.3
+# What's new in 0.4
 
-This version is **out**. It is what `npx docpensieve init my-site` installs,
-and what the `latest` pages of this site document:
+This version is **in preparation**. Its betas go out under the npm tag `beta`,
+while the version installed by default stays the 0.3, documented in the
+`latest` pages of this site:
 
 ```bash
-npm install docpensieve@latest
+npx docpensieve@beta init my-site
 ```
 
-## What it brings
+## Already there
 
-### Authors at the head of a page
+Nothing yet: the 0.4 has just opened, and its pages are still those of the 0.3.
+Each feature is announced here as it lands, with a link to the guide and to the
+reference — this page announces, it is never the only place something is
+written.
 
-A page carrying `authors`, `date` or `modified` now opens with a byline: who
-wrote it, and when. The names show as written; a JSON file of the version,
-named by `authors: 'authors.json'`, adds a biography, an avatar and a link —
-and feeds the page data with them. See
-[Who wrote the page](./guide/writing-pages/) in the guide, and the
-[`authors` field](./reference/configuration/) in the reference.
+## For a 0.3 project
 
-### Series and cards
-
-A folder is a series: its `index` page introduces it, and the pages beside
-that index are its instalments. The `Cards` component turns that structure
-into a grid of clickable cards — title, description, image, number of pages,
-update date — instead of an index list written by hand, which goes stale at
-the first page renamed. See [Cards](./components/cards/).
-
-### Tags at the bottom of a page
-
-The `tags` of a page, read until now only by its structured data, show at the
-bottom of the page, below the text they describe. See
-[The frontmatter](./guide/writing-pages/) in the guide.
-
-### Description files, optional per version
-
-A `sidebar` or `authors` file named in the configuration no longer has to
-exist in every version folder. A version without it keeps the menu of its
-folders, or shows the names its pages give: describing the menu or the authors
-of a new version no longer forces a copy into the older ones. A file present
-but unreadable, or wrongly written, still stops the build.
-
-### Header links, and a menu on narrow screens
-
-`headerLinks` adds links to the header, beside the version switcher — each may
-name the version it leads to, so that a section written in one version is
-reachable from all of them. On a narrow screen, the switcher, the links and the
-search field move behind a menu button, which opens without a script. See the
-[`headerLinks` field](./reference/configuration/).
-
-## For a 0.2 project
-
-Nothing to change: a 0.2 configuration builds as it is.
-[Migrate from 0.2 to 0.3](./guide/migrate-from-0-2/) lists what changes on
+Nothing to change: a 0.3 configuration builds as it is.
+[Migrate from latest to beta](./guide/migrate-to-beta/) lists what changes on
 its own, what to check, and what is worth turning on.

package/starter/01-guide/07-migrate-from-0-2.md

@@ -1,47 +0,0 @@
----
-title: Migrate from 0.2 to 0.3
-description: Move a project from the 0.2 to the 0.3 — what changes on its own, and what to turn on.
-tags: [guide, migration]
----
-
-# Migrate from 0.2 to 0.3
-
-A project on the 0.2 builds with the 0.3 as it is: every new field is optional.
-
-## Update
-
-```bash
-npm install docpensieve@latest
-```
-
-Through `npx` alone, `npx docpensieve` fetches the 0.3 by itself. Going back is
-`npm install docpensieve@0.2.0`.
-
-## What changes on its own
-
-| What                                       | In 0.3                                          |
-| ------------------------------------------ | ----------------------------------------------- |
-| Pages with `authors`, `date` or `modified` | Open with a byline naming the authors and dates |
-
-Nothing to change, but something to know: those three fields already existed,
-read by the sitemap and the page data without ever being shown. They are now
-shown, so a page that carries them gains a block it did not have. A page that
-carries none of them looks exactly as before.
-
-`tags` follows the same path: read until now only by the page data, it now
-shows at the bottom of every page that carries it.
-
-One constraint is gone, too. A `sidebar` or `authors` file named in the
-configuration no longer has to exist in every version folder: a version
-without it keeps the menu of its folders, or shows the names alone.
-
-On a narrow screen, the header changes for every site: the version switcher and
-the search field move behind a menu button. Nothing to configure — `headerLinks`
-only adds links to that menu.
-
-## What to turn on
-
-| Field                        | Gives                                                 |
-| ---------------------------- | ----------------------------------------------------- |
-| `authors: 'authors.json'`    | Biographies, avatars and links, described per version |
-| `<Cards />` in an index page | A grid of cards built from the pages of the folder    |