How Blockspace Co.'s sites are built

Every site of Blockspace Co. wears the same frame around its own content: the estate rail, the site's own bar, and a footer in a fixed order. The sites don't look identical. Each has its own palette, its own words and its own pages. But a visitor always knows where they are, how to get to the rest of the estate, and where the machine-readable files live.

The frame was designed from a survey of the Fortune 10's corporate websites (October 2026), then built on the estate's own rules: publish only what is real, link only what is live, and never open anything on hover.

The three rows, in order, on every site #

1. The estate rail.
   • It is a dark band across the top, reading "Blockspace Co. · N properties ▾".
   • It opens a panel listing every property by group, with each property's own line.
   • A property that isn't live is listed as text with its state, never as a link.
   • It is the same bytes on every site, rendered from the estate's projects list at every build.
   • The site's utility links (developers, contact, a search field) sit at its right.
2. The property bar.
   • The site's name or wordmark is on the left. The site's one-line description sits under it on the home page only.
   • Then come three to seven sections and exactly one call to action, at the right.
3. The panels.
   • A section with sub-pages opens a full-width panel: an intro column with "Overview →", then up to three columns of at most eight links.
   • It opens on click, Enter or Space, never on hover.
   • Escape closes it and returns focus to its trigger.
   • One panel is open at a time.

The footer: four parts, in a fixed order #

1. The name and line of the site.

2. The site's own headed columns: at most six columns of at most eight links.

3. The Related block: up to four related properties from the projects list, each with that site's one-line description. A property that isn't live shows as text with its state.

4. The relation row:

   • "A Blockspace Co. company" or "A project of Blockspace Co.", linked to https://blockspace.holdings/;
   • then " on blockspace.wiki";
   • then "All projects";
   • then "For machines: llms.txt · sitemap · manifest".

   The site's legal links follow on the same row.

The footer never lists every property: the rail does that.

Behaviour and access #

• Landmark labels: "The Blockspace Co. estate" for the rail, "Main" for the bar, "Utility" for the utility links, "Related" for the Related block.
• A skip link to the main content, first in the page.
• The current section is marked with aria-current="page" and an underline.
• Focus is always visible: a 3 px ring in the site's focus colour.
• Contrast: text meets WCAG AA in both light and dark themes. Themes follow the reader's system setting.
• On a phone:
  • the rail collapses to its one button;
  • the bar becomes a Menu button that opens an accordion of the sections, with search inside;
  • the call to action stays visible under the name.
• Without JavaScript, every panel still opens. The menus are native disclosure elements, and the script only adds one-panel-at-a-time, Escape and click-outside.
• No outside scripts, fonts or trackers.

What may vary, and what may not #

May vary per site:

• the palette and type, within AA;
• the section nouns and their count (three to seven);
• the call to action;
• the footer columns;
• a sticky bar, or not;
• the site's own share image.

May not vary:

• the order of the rows and of the footer's parts;
• the rail's bytes;
• any menu that opens on hover;
• a missing relation row;
• a missing link to the site's wiki page;
• a footer that lists every property.

Exempt sites #

degent.club, counters.fun, counters.gallery, proto.counters.gallery, block.space, explore.block.space, scribb.it, mintbitbars.xyz and spaceblocks.art keep their own navigation, footer and look, by the owner's decision. block.space's frame stays as it is today. They stay part of the estate through their machine-readable files and the plain links to Blockspace Holdings and blockspace.wiki in their own pages. The daily check reports them as exempt, never as failing; the link and file checks still apply to them.

Tokens #

A site sets these in its own stylesheet to theme the frame. A site that keeps its own CSS for the rest of the page matches them by name.

How it is checked #

A daily check visits every site and reports, per site:

• the rows are present and in order;
• the landmark labels and the skip link are there;
• there is exactly one call to action, and the current page is marked;
• no stylesheet opens a menu on hover;
• the footer has its four parts in order, with the relation row, the wiki link and the Related block;
• the footer doesn't list every property.

The same check confirms that each site links up to Blockspace Co. and across to its wiki page and related properties, and that every machine-readable file answers.

This wiki wears the same frame; its own "Sections" sidebar is its local navigation inside it.

Related #

• About this wiki
• Projects
• Machine surfaces

Sources #

1. The blockspace.holdings site · blockspace.holdings
2. Blockspace Co. records