architecture: point actors and glossary at the concepts page

kiara commented

2026-08-23 21:33:46 +02:00

Owner

architecture-docs/architecture.md's ## Actors and ## Glossary become a pointer to https://core.pages.git.fediversity.eu/concepts.html, so exactly one copy of that vocabulary survives.

The page is new in the fediversity monorepo (core/docs/md/concepts.md), and is the union of the two copies that existed: it carries the root README.md text plus this document's Maintainers/Developers split under Actors and its Provider, Provider configuration and Resource glossary entries. Nothing is dropped. It lives there because that is where the terms are used -- the option reference and the flake-attribute pages on the same site refer to them without redefining them.

The two in-document links that pointed at the removed anchors (- Circle: [actor](#actors) and the components note) are repointed at the same page's anchors.

Separate note, not touched here: ### Proxmox under ## Technologies used still describes Proxmox as the hypervisor. The fediversity repo no longer uses it -- it deploys through Incus. Flagging rather than rewriting, since the rest of that section is a planning document rather than a description of the code, and deciding what replaces it is a call for the project team.

Assisted-by: Claude:claude-opus-5

`architecture-docs/architecture.md`'s `## Actors` and `## Glossary` become a pointer to <https://core.pages.git.fediversity.eu/concepts.html>, so exactly one copy of that vocabulary survives. The page is new in the `fediversity` monorepo (`core/docs/md/concepts.md`), and is the union of the two copies that existed: it carries the root `README.md` text plus this document's `Maintainers`/`Developers` split under Actors and its `Provider`, `Provider configuration` and `Resource` glossary entries. Nothing is dropped. It lives there because that is where the terms are used -- the option reference and the flake-attribute pages on the same site refer to them without redefining them. The two in-document links that pointed at the removed anchors (`- Circle: [actor](#actors)` and the components note) are repointed at the same page's anchors. Separate note, not touched here: `### Proxmox` under `## Technologies used` still describes Proxmox as the hypervisor. The `fediversity` repo no longer uses it -- it deploys through Incus. Flagging rather than rewriting, since the rest of that section is a planning document rather than a description of the code, and deciding what replaces it is a call for the project team. Assisted-by: Claude:claude-opus-5

kiara added 1 commit

2026-08-23 21:33:46 +02:00

architecture: point actors and glossary at the concepts page ea8cb7312a

The `fediversity` monorepo now carries these two sections at
`core/docs/md/concepts.md`, published as
<https://core.pages.git.fediversity.eu/concepts.html>. That is where the
terms are actually used -- by the option reference and the flake-attribute
pages on the same site -- so keeping a second copy here only invites drift
between them.

The published page is the union of both copies: this document's
`Maintainers`/`Developers` split and its `Provider`, `Provider configuration`
and `Resource` entries are carried over, not dropped.

Assisted-by: Claude:claude-opus-5
Claude-Session: https://claude.ai/code/session_01CR6QqMB5qE59MJvwjXxG2E

kiara merged commit eabb994eb8 into main

2026-08-23 21:41:45 +02:00

kiara deleted branch concepts-single-copy

2026-08-23 21:41:45 +02:00

kiara referenced this pull request from a commit

2026-08-23 21:41:46 +02:00

architecture: point actors and glossary at the concepts page (#41)

kiara referenced this pull request from fediversity/fediversity

2026-08-23 21:43:21 +02:00

docs: flesh out the published sites, and make the specs name the deployment #1574

toonn commented

2026-08-24 09:37:54 +02:00

Member

Maybe this was merged prematurely because the page nor the markdown source seem to exist? I'm also not convinced a glossary doesn't belong in the architecture-docs, all the architecture documentation needs to reference it. The problem with referencing the Hosting Provider-facing documentation in the fediversity repo is that we may change the terminology there at some point to be clearer to interested parties.

kiara commented

2026-08-24 12:20:31 +02:00

Author

Owner

apologies for the order - it landed now (fediversity/fediversity#1574).

we may change the terminology there at some point to be clearer to interested parties.

this is far, of course.

I'm also not convinced a glossary doesn't belong in the architecture-docs, all the architecture documentation needs to reference it.

so, the idea here kind of to move more from markdown files to actually deployed documentation, as this repo in practice is perhaps both less friendly to navigate as well as more ephemeral, containing largely historical stuff.
on source of the documentation, i'm seeing quite some close coupling to the point of it feeling sensible to update documentation and implementation in lock-step, so in that sense core/ (containing the data model modeling the concepts) felt like a sensible place perhaps.

apologies for the order - it landed now (fediversity/fediversity#1574). > we may change the terminology there at some point to be clearer to interested parties. this is far, of course. > I'm also not convinced a glossary doesn't belong in the architecture-docs, all the architecture documentation needs to reference it. so, the idea here kind of to move more from markdown files to actually deployed documentation, as this repo in practice is perhaps both less friendly to navigate as well as more ephemeral, containing largely historical stuff. on source of the documentation, i'm seeing quite some close coupling to the point of it feeling sensible to update documentation and implementation in lock-step, so in that sense `core/` (containing the data model modeling the concepts) felt like a sensible place perhaps.

Rows
Columns

architecture: point actors and glossary at the concepts page #41