Uh oh!
There was an error while loading. Please reload this page.
docs: describe this project to the portfolio - #43
Merged
Conversation
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.
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Carries the portfolio prose already written under
.dylan/into the.folioformat 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.mdstory.md/.nl.mdcontent/{en,nl}/story.mdstar/1-analyzer.md/.nl.mdcontent/{en,nl}/analyzer.mdmeta.toml[[links]]+label_nlproject.tomllinks +locales/{en,nl}.tomlThe prose is carried verbatim. The only edit is an H1 on
overviewandstory(# 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.mdalready had one.project.tomladds status, role,started = "2026-07"from the repo's first commit, and tagscsharp,dotnet,tooling.Two things dropped, deliberately
featuredandweight. Both are the site's decision, not the project's, andfeaturedis 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 twodocslinks would share a single label. I kept the agents guidance asdocswith its original English and Dutch labels, and addedpackagepointing 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
PortfolioResolveralongside the central config:Zero warnings.
used-by → foliois generated from ausesdeclared in Folio, not written here..dylan/is left in place; removing it is a separate decision.