Imperium
Studio configuration becomes public sites This page lists everything the Leumas graph records about how it relates to the rest of the system.
What Imperium is
Studio configuration becomes public sites It is recorded in the Leumas graph as a service in the architecture grain.
What Imperium relates to
The graph records 13 relationships for it, across 4 kinds. It contains react.leumas.tech and Leumas Files.
What it depends on, and what depends on it
Imperium depends on Leumas API. It is used by Leumas Studio, Sections, Bermudez Portfolio, Leumas QR and BulkForge (bulkforge.leumas.tech), and 4 more.
Why it is shaped this way
Imperium is Leumas hosting: Studio authors and manages sites, and Imperium resolves domains and serves the public result. A site is a row, not a deploy.
How to read this
Every relationship here is one of nine shared kinds, mapped from the source graph rather than invented. A kind that a source uses and this model does not express is dropped and counted rather than turned into "related to", so what you see understates the source rather than embellishing it.
- Contains: react.leumas.tech and Leumas Files.
- Part of: Leumas.
- Depends on: Leumas API.
- Used by: Leumas Studio, Sections, Bermudez Portfolio, Leumas QR, BulkForge (bulkforge.leumas.tech) and Leumas Splat, and 3 more.
Questions
What does Imperium depend on?
Leumas API.
What uses Imperium?
Leumas Studio, Sections, Bermudez Portfolio, Leumas QR, BulkForge (bulkforge.leumas.tech) and Leumas Splat, and 3 more.