Skip to content

docs: describe this project to the portfolio - #43

Merged
DutchyD merged 1 commit into
developmentfrom
docs/folio-content
Aug 10, 2026
Merged

docs: describe this project to the portfolio#43
DutchyD merged 1 commit into
developmentfrom
docs/folio-content

Conversation

@DutchyD

Copy link
Copy Markdown
Contributor

Carries the portfolio prose already written under .dylan/ into the .folio format the portfolio actually reads. On the live API, Loom currently appears with no name, no tagline, no tags and zero sections.

What moves where

.dylan/.folio/
description.md / .nl.mdcontent/{en,nl}/overview.md
story.md / .nl.mdcontent/{en,nl}/story.md
star/1-analyzer.md / .nl.mdcontent/{en,nl}/analyzer.md
meta.toml[[links]] + label_nlproject.toml links + locales/{en,nl}.toml

The prose is carried verbatim. The only edit is an H1 on overview and story (# Overview / # Overzicht), so each file stands on its own when read on GitHub — the leading H1 becomes the section title and is stripped from the body. analyzer.md already had one.

project.toml adds status, role, started = "2026-07" from the repo's first commit, and tags csharp, dotnet, tooling.

Two things dropped, deliberately

featured and weight. Both are the site's decision, not the project's, and featured is already set for Loom in the central config.

[[release.packages]] — all ten NuGet identifiers. GitHub releases already reach the portfolio through repository metadata, and the format has no registry concept.

One thing lost, which you may want back

Link labels key on type (link.docs), so two docs links would share a single label. I kept the agents guidance as docs with its original English and Dutch labels, and added package pointing at the NuGet listing. "Sample ordering API" is not carried. Swapping which link survives is a two-line change.

Verified

The real files were run through Folio's PortfolioResolver alongside the central config:

PROJ en loom name=Loom fallback=False tags=3 links=2 relations=used-by->folio
sections=overview:Overview, story:Story, analyzer:An analyzer for…
PROJ nl loom tagline=Tien .NET-pakketten die de saaie keuzes één keer maken
sections=overview:Overzicht, story:Verhaal, analyzer:Een analyzer voor…

Zero warnings. used-by → folio is generated from a uses declared in Folio, not written here.

.dylan/ is left in place; removing it is a separate decision.

Carries the prose already written under .dylan into the .folio format the
portfolio reads: the description becomes an overview, the story and the
analyzer entry become sections, each in both published locales.
Package identifiers are dropped, since GitHub releases already reach the
portfolio, and featured now lives in the central config rather than here.
@coderabbitai

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 724449c5-48e4-480a-b0e9-4a42b1496892

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@DutchyD
DutchyD merged commit 19ebc12 into developmentAug 10, 2026
9 checks passed
@DutchyD
DutchyD deleted the docs/folio-content branch August 10, 2026 12:12
Sign up for freeto 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

@DutchyD