# Gitt One Pages — content tags of the www engine A page is a file articles//index..mdx: front matter (title, description) and then a sequence of sections — one typed tag per slide of the page, top to bottom. Only the tags listed here exist. Sub-blocks (Feature, Step, Question, Plan, …) go inside their parent tag and never stand alone. Rules that hold for every tag: - Pictures are file names in images/ of the content repository: image="team.jpg", image="logos/acme.png". Files to download live in assets/ and are linked as "/assets/". The build resizes pictures; never inline a URL. - Icons are Heroicons: import at the top of the file (import BoltIcon from 'astro-heroicons/outline/Bolt.astro';) and pass the import as Icon={BoltIcon}. Names are the Heroicons outline set. - A prop with a string value is written title="…"; numbers, booleans and arrays are written in braces: columns={3}, open, overlapNext={false}, bullets={['a', 'b']}. - "Children: markdown" means the text between the opening and closing tag is rendered as markdown (paragraphs, lists, emphasis, links). "Children: tags" means only those tags belong inside; free text there is dropped. - theme values: "light" white; "muted" light grey; "dark" a stone band with white text; "brand" the brand gradient with white text; "brand-dark" the deep flat brand tone. Every colour derives from brandColor in pages.config.js. - Links: primaryHref / href take a site path ("/contacts/"), an anchor on the home page ("/#contacts" — the contact form's default id) or an absolute URL. - A button or link is shown only when its text prop is given. - Header and footer are not tags: they come from pages.config.js (title, navigation, defaultPhone, defaultEmail, footerLines, logoImage, brandColor). - An editor working through chat cannot add binary files. When a page needs a picture, a logo or a PDF that is not in images/ or assets/ yet, write the tag with the file name you chose and ask the user to upload the file under that name (GitLab: Repository → Upload file, on the branch being edited). - "Ask the user:" in a tag's reference names what only a person can do — accounts, keys, addresses, files, decisions. Do your part, never invent or copy such values, and end the reply with a numbered list of what the user has to do. The HTML gallery with rendered samples: https://pages.gitt.one/components/ ## Hero The first screen: title, pitch, picture, buttons. ### HeroCover (popular) HeroCover — the first screen: a full-width photo under the brand gradient, the title, pitch and buttons centered on top of it. Use for: a landing that opens with a wide, atmospheric photo (a landscape, a workplace, a team) and one short promise. Not for: a product shot that must stay whole (); a page that opens with words alone (). Children: optional markdown between the tags, rendered under the description and above the buttons. No sub-block tags. Picture: LANDSCAPE. It is cropped to fill the section and tinted with the brand colour, so it must not carry text or a logo. Without `image` the section is a plain brand-coloured band. `tint={false}` shows the photo as it is — for a background that already carries the brand colours. Logo: `logo` (file name in images/) is shown above the title, about 7rem high — for a landing without the site header (headerTheme "none"). Follow-up: by default the bottom keeps room for a row that hangs over the edge. Set overlapNext={false} when the next section is anything else, or the hero ends with an empty band. Buttons: a button appears only when its text is given; primary is the solid brand button, secondary the translucent one. Props: - title (string, required) — the headline, one line - highlight (string) — a second line of the headline, painted with the brand gradient - description (string) — the pitch under the headline, one or two sentences - image (string) — file name in images/, landscape; cropped to fill the section - tint (boolean, default true) — paint the photo with the brand gradient; false keeps its own colours - logo (string) — file name in images/, a logo shown above the title - overlapNext (boolean, default true) — keep room at the bottom for a row; false when nothing hangs over - primaryText (string) — text of the solid brand button; omit to hide the button - primaryHref (string, default '#') — link of the primary button, e.g. "/contacts/" or "#contacts" - secondaryText (string) — text of the second, translucent button - secondaryHref (string, default '#') — link of the secondary button Example 1: ```mdx ``` Example 2: ```mdx ``` Example 3: ```mdx ``` ### HeroSplit (popular) HeroSplit — the first screen with the text on one side and the picture on the other. Use for: a product with a picture worth half the screen — a device, a packshot, a screenshot. Not for: a wide photo as a backdrop (); no picture at all (). Children: optional markdown between the tags, rendered under the description and above the buttons. No sub-block tags. Picture: `imageFit` decides how it looks. imageFit="contain" (default) shows the picture whole, hugging the bottom edge of its half. Only a PORTRAIT or square picture looks right; a landscape one sinks into the bottom corner and leaves the top of its half empty. Product shots on a transparent or white background work best. imageFit="cover" fills the picture half edge to edge, cropped, with a diagonal that hands the text band over to the photo. Use it for a LANDSCAPE photo. Theme: "light" (white) or "dark" (stone band with white text). imageSide puts the picture left or right. Buttons: a button appears only when its text is given. Props: - title (string, required) — the headline, one line - highlight (string) — a second line of the headline, painted with the brand gradient - description (string) — the pitch under the headline, one or two sentences - image (string, required) — file name in images/; portrait for imageFit="contain", landscape for "cover" - imageSide ('left' | 'right', default 'right') — which side the picture takes - theme ('light' | 'dark', default 'light') — "light" white, "dark" stone band - imageFit ('cover' | 'contain', default 'contain') — "contain" shows the picture whole (portrait shots); "cover" crops it to fill the half (landscape photos) - primaryText (string) — text of the solid brand button; omit to hide the button - primaryHref (string, default '#') — link of the primary button - secondaryText (string) — text of the second, outlined button - secondaryHref (string, default '#') — link of the secondary button Example 1: ```mdx ``` Example 2: ```mdx ``` ### HeroText HeroText — the first screen without a picture: title, pitch and buttons, centered in a reading column. Use for: a page that opens with words alone — a service, a consultancy, a documentation landing, an inner page. Not for: a page that has a good picture — use or ; a mid-page call to action — use a section, this one renders an

. Children: optional markdown between the tags, rendered under the description and above the buttons. No sub-block tags. Theme: "light" (white) or "dark" (stone band with white text). Buttons: a button appears only when its text is given. Props: - title (string, required) — the headline, one line - highlight (string) — a second line of the headline, painted with the brand gradient - description (string) — the pitch under the headline, one or two sentences - theme ('light' | 'dark', default 'light') — "light" white, "dark" stone band - primaryText (string) — text of the solid brand button; omit to hide the button - primaryHref (string, default '#') — link of the primary button - secondaryText (string) — text of the second, outlined button - secondaryHref (string, default '#') — link of the secondary button Example: ```mdx ``` ## Features & lists Grids and lists of benefits, services, steps, products, checklists. ### FeatureCards (popular) Sub-blocks: . FeatureCards — a grid of cards, one per card: services, benefits, reasons to choose, audiences. Use for: three to six parallel items of equal weight, each with an icon or a picture and a sentence or two. The most used section of the library. Not for: a dense list of many short points (, no cards); one topic explained in several points beside a heading (); a numbered process (); a choice between two or three things (). Children: tags only, three or more. Content written directly between the tags is not rendered. Layout: `columns` 1–4 (default 3); the cards wrap to one column on phones. `overlap` pulls the grid up over the previous section — pair it with a right above (its default overlapNext keeps the room). `heading="left"` or a `kicker` moves the heading out of the centre. Look: `icons="soft"` paints the icon squares in a pale tint instead of the brand gradient; `decor="dots"` adds the decorative dot grid; on theme="brand" the cards turn translucent white on the gradient. Link: `linkText` + `href` add one centered button under the grid. Props: - id (string) — anchor of the section, e.g. "services" → /#services - kicker (string) — short uppercase line above the title, painted with the brand gradient - title (string) — the section heading - description (string) — one or two sentences under the heading - columns (1 | 2 | 3 | 4, default 3) — cards per row on desktop - theme ('light' | 'muted' | 'dark' | 'brand' | 'brand-dark', default 'light') — background of the section - decor ('none' | 'dots' | 'dots-left', default 'none') — decorative dot grid behind the content - overlap (boolean, default false) — hang the cards over the bottom edge of the section above (a ) - heading ('center' | 'left', default 'center') — where the heading sits - icons ('brand' | 'soft', default 'brand') — "brand" gradient squares behind the icons, "soft" a pale tint - linkText (string) — text of one centered button under the grid; shown only with href - href (string) — link of that button - class (string) — escape hatch for compositions: extra classes for the section shell Example 1: ```mdx import BoltIcon from 'astro-heroicons/outline/Bolt.astro'; import SignalIcon from 'astro-heroicons/outline/Signal.astro'; import CloudIcon from 'astro-heroicons/outline/Cloud.astro'; ``` Example 2: ```mdx ``` Example 3: ```mdx import SignalIcon from 'astro-heroicons/outline/Signal.astro'; import ShieldIcon from 'astro-heroicons/outline/ShieldCheck.astro'; import BatteryIcon from 'astro-heroicons/outline/Battery50.astro'; ``` ### Feature (popular) Sub-block of . Feature — one item of , or : a badge (icon or number), a title, a description, optional bullets, optional markdown and an optional link. Parent: never on its own; always inside one of the three Feature… sections, which decide whether it is a card, a plain block or an aside row. Badge: `Icon` is a Heroicon imported at the top of the file — `import BoltIcon from 'astro-heroicons/outline/Bolt.astro';` then `Icon={BoltIcon}`; `number` puts an ordinal in the badge instead. Without either there is no badge. Children: markdown between the tags is rendered under the description (paragraphs, lists, emphasis, links). Picture: `image` (file name in images/) is shown full width above the title — for a screenshot or an illustration instead of an icon. `imageWidth` caps it (in px) — for a small spot illustration that would otherwise blow up to the card's width on phones. Link: `linkText` + `href` render an arrow link at the bottom of the item. Props: - title (string, required) — the item heading - kicker (string) — a short mono label beside the badge, e.g. a product code or a version - description (string) — one or two sentences - Icon (any) — a Heroicon component imported in the article, e.g. Icon={BoltIcon} - image (string) — file name in images/, shown above the title - imageWidth (number) — largest width of that picture in px; without it the picture fills the item's width - number (string | number) — an ordinal shown in the badge instead of an icon - bullets (string[], default []) — short points listed under the description - linkText (string) — text of the arrow link at the bottom; shown only with href - href (string) — link target ### FeatureAside (popular) FeatureAside — the heading, a paragraph and an optional picture on the left; a dense icon-and-text list of on the right. Use for: one subject explained in several points — "how we work", "what is included", "why it matters" — where the points support the heading rather than compete with it. Not for: parallel offers of equal weight (); a numbered sequence (). Children: tags, three to six. The icon of each sits to the left of its text. Picture: `image` is placed under the heading text on the left; any proportions, shown whole. Link: `linkText` + `href` add one centered button under the block. Props: - id (string) — anchor of the section - kicker (string) — short uppercase line above the title - title (string) — the section heading, left column - description (string) — a paragraph under the heading, left column - theme ('light' | 'muted' | 'dark' | 'brand' | 'brand-dark', default 'light') — background of the section - decor ('none' | 'dots' | 'dots-left', default 'none') — decorative dot grid behind the content - image (string) — file name in images/, shown under the heading text - linkText (string) — text of one centered button under the block; shown only with href - href (string) — link of that button - class (string) — escape hatch for compositions: extra classes for the section shell Example: ```mdx import BoltIcon from 'astro-heroicons/outline/Bolt.astro'; import SignalIcon from 'astro-heroicons/outline/Signal.astro'; import ShieldIcon from 'astro-heroicons/outline/ShieldCheck.astro'; ``` ### FeatureList FeatureList — the items without cards: the icon and the text straight on the section's background. Use for: many short points — six, eight, twelve — where a card around every line would be noise: a feature matrix, "what you get", a capabilities list. Not for: three to six items that deserve a card each (). Children: tags only. Layout: `columns` 1–4 (default 3); `heading="left"` or a `kicker` moves the heading out of the centre. Link: `linkText` + `href` add one centered button under the list. Props: - id (string) — anchor of the section - kicker (string) — short uppercase line above the title - title (string) — the section heading - description (string) — one or two sentences under the heading - columns (1 | 2 | 3 | 4, default 3) — items per row on desktop - theme ('light' | 'muted' | 'dark' | 'brand' | 'brand-dark', default 'light') — background of the section - decor ('none' | 'dots' | 'dots-left', default 'none') — decorative dot grid behind the content - heading ('center' | 'left', default 'center') — where the heading sits - icons ('brand' | 'soft', default 'brand') — "brand" gradient squares behind the icons, "soft" a pale tint - linkText (string) — text of one centered button under the list; shown only with href - href (string) — link of that button - class (string) — escape hatch for compositions: extra classes for the section shell Example 1: ```mdx import BoltIcon from 'astro-heroicons/outline/Bolt.astro'; import CloudIcon from 'astro-heroicons/outline/Cloud.astro'; import MapIcon from 'astro-heroicons/outline/MapPin.astro'; ``` Example 2: ```mdx ``` ### FeatureSection Sub-blocks: . FeatureSection — a wrapper for one or more rows: big split blocks, each with a headline, a paragraph, a button and a large picture bleeding to the edge of the screen. Use for: one or two flagship features that deserve a screen each — a dashboard screenshot, a device photo — presented editorially rather than as a grid. Not for: a grid of several equal features (); a picture beside plain text ( with an image or ). Children: tags only; each is a full-width row. Look: white background with a soft grey gradient at the top; the design is an author block kept from one of the fleet's sites and has no theme or columns props. Props: none — a wrapper around its children. Example: ```mdx ``` ### FeatureItem Sub-block of . FeatureItem — one row of : an icon badge, a headline, a paragraph and a gradient button on the left, a big picture on the right bleeding past the container. Parent: only. Children: none; the text comes from `description`. All five props are required. Picture: `imgPath` (file name in images/) is a LANDSCAPE screenshot or photo; it keeps its proportions and is cropped only on very wide screens. The icon in the badge is fixed (an inbox). Props: - title (string, required) — the headline of the row - description (string, required) — the paragraph under the headline - btnText (string, required) — text of the gradient button - btnPath (string, required) — link of the button - imgPath (string, required) — file name in images/, a landscape screenshot or photo ### ChecklistSection (popular) Sub-blocks: . ChecklistSection — a heading on the left and a three-column grid of check-marked points () on a light grey band. Use for: requirements, "what you need before you start", compliance points, a checklist of what is included — items that read as "yes, done" rather than as features to sell. Not for: benefits with icons (, ); an ordered process (). Children: tags only, usually three to nine. Look: an author block kept from one of the fleet's sites — always the grey band, always three columns on desktop; the heading has a gradient `subTitle` above it. Props: - id (string) — anchor of the section, e.g. "features" - subTitle (string) — short uppercase line above the title, painted with the brand gradient - title (string, required) — the section heading - description (string) — a paragraph under the heading Example: ```mdx ``` ### ChecklistItem (popular) Sub-block of . ChecklistItem — one point of : a brand-coloured check mark, a bold title and a line of text. Parent: only. Children: none, both props are plain strings. Props: - title (string, required) — the point, bold - description (string, required) — one sentence under it ### Steps Sub-blocks: . Steps — a numbered how-it-works list: circle badges numbered automatically, a title and a short text under each (). Use for: a process in three to six steps — "how it works", "how to order", onboarding. Not for: a horizontal chain of one-word stages on a dark band (); unordered points (). Children: tags only; the numbering follows their order. Layout: `columns` 2–4 (default 4). The heading is left-aligned by design (this block came into the library as it was). Props: - id (string) — anchor of the section - title (string) — the section heading - description (string) — a paragraph under the heading - columns (2 | 3 | 4, default 4) — steps per row on desktop - theme ('light' | 'muted' | 'dark' | 'brand' | 'brand-dark', default 'light') — background of the section Example: ```mdx ``` ### Step Sub-block of . Step — one item of : the numbered circle, a title and a description. The number is automatic. Parent: only. Children: optional markdown between the tags, rendered under the description. Props: - title (string, required) — the step heading - description (string) — one or two sentences ### Workflow Sub-blocks: . Workflow — a horizontal process chain on a dark stone band: numbered circles joined by arrows, one short label each (). Use for: a pipeline or lifecycle in one-word or few-word stages — "Order → Build → Test → Deploy" — as a compact divider between bigger sections. Not for: steps that need a sentence of explanation each (). Children: tags only; three or six fit a row best (six per row on desktop, three on tablets). Numbering and arrows are automatic. Props: - id (string) — anchor of the section - title (string) — a heading centered above the chain Example: ```mdx ``` ### WorkflowStep Sub-block of . WorkflowStep — one link of the chain: the number and a short label. Parent: only. No children. Props: - title (string, required) — the stage label, a few words ## Compare Things side by side with equal weight: products, builder images, code samples. ### Compare (popular) Sub-blocks: . Compare — two or three columns of equal weight, one card each: old vs new, two products, two builder images, two code samples. Use for: a choice, where the reader is meant to look left and right — "on-premise or cloud", "before and after", "basic or pro". Not for: a list of features that are not alternatives (); prices (). Children: tags, two or three. Layout: `columns` 2 (default) or 3; three columns only from large screens — tablets get the stacked layout. `heading="left"` moves the heading out of the centre. Props: - id (string) — anchor of the section - kicker (string) — short uppercase line above the title - title (string) — the section heading - description (string) — a paragraph under the heading - columns (2 | 3, default 2) — cards per row on desktop - heading ('center' | 'left', default 'center') — where the heading sits - theme ('light' | 'muted' | 'dark' | 'brand' | 'brand-dark', default 'muted') — background of the section (default "muted") - decor ('none' | 'dots' | 'dots-left', default 'none') — decorative dot grid behind the content Example 1: ```mdx ``` Example 2: ```mdx ``` ### CompareItem (popular) Sub-block of . CompareItem — one column of : a white card with an optional picture on top, an icon or a mono label, a title, paragraphs, bullets, a code sample and markdown. Parent: only. Text: `description` is one paragraph or an array of paragraphs; words between *asterisks* inside it are painted in the brand colour. Code: `code` renders a dark code block at the bottom of the card, `file` its file-name caption — for comparing two configurations or snippets. Children: markdown between the tags is rendered at the end of the card. Picture: `image` (file name in images/) is shown whole in a fixed-height box above the text — a product shot or a logo, not a wide photo. Props: - title (string, required) — the card heading - kicker (string) — a short mono label beside the icon, e.g. a version or a code - description (string | string[]) — one paragraph, or several as an array; *emphasis* is painted in the brand colour - image (string) — file name in images/, shown whole above the text - Icon (any) — a Heroicon component imported in the article, e.g. Icon={BoltIcon} - bullets (string[], default []) — short points listed under the description - code (string) — a code sample rendered in a dark block - file (string) — file name shown as the caption of the code block ## Text & prose Words rather than grids: mission, about, certification texts, text beside a picture or a video, questions and answers. ### Prose (popular) Sub-blocks: , . Prose — a text section: kicker, title and lead, then markdown in a reading column. The section for anything that is words rather than a grid. Use for: mission, about us, a certification text, terms, a long explanation, a page that is mostly paragraphs. Not for: a first screen (); a list of parallel points (); questions and answers (). Children: markdown between the tags — paragraphs, headings, lists, links, emphasis, tables, code. Also the sub-block tags (a titled sub-section) and (a card floated beside the text). Layout: align="center" (default) centers the heading and the text; align="left" is the shape for long reading. `width="text"` keeps a comfortable reading measure, `width="wide"` uses the whole print zone — use "wide" together with a . `heading` aligns the heading independently (a centered heading over a left-aligned body is the certification-page shape). Picture: `image` (file name in images/) is shown under the text — a certificate scan, a schema. `imageFrame="none"` drops the card (rounded corners, shadow) and lets the picture grow to 56rem — for a cut-out device mockup on a coloured band; with nothing else in the section the picture then is the whole slide. Links: `linkText` + `href` render an arrow link; primary/secondary buttons follow under the text. Props: - id (string) — anchor of the section - kicker (string) — short uppercase line above the title, painted with the brand gradient - title (string) — the section heading - description (string) — the lead paragraph, larger than the body - align ('center' | 'left', default 'center') — alignment of heading and text - width ('text' | 'wide', default 'text') — 'text' keeps the reading measure; 'wide' uses the whole print zone — what a section with a wants - heading ('center' | 'left') — header alignment; defaults to `align` - theme ('light' | 'muted' | 'dark' | 'brand' | 'brand-dark', default 'light') — background of the section - decor ('none' | 'dots' | 'dots-left', default 'none') — decorative dot grid behind the content - image (string) — file name in images/, shown under the text - imageFrame ('card' | 'none', default 'card') — "card": rounded with a shadow, up to 42rem; "none": as it is, up to 56rem - linkText (string) — text of an arrow link under the text; shown only with href - href (string) — target of that link - primaryText (string) — text of the solid brand button; omit to hide the button - primaryHref (string, default '#') — link of the primary button - secondaryText (string) — text of the second, outlined button - secondaryHref (string, default '#') — link of the secondary button - class (string) — escape hatch for compositions: extra classes for the section shell Example 1: ```mdx Growers used to choose between a thermometer that told them nothing and a research mast nobody could afford. Nordvind sits in between: the sensors that change a decision, and none of the ones that only look good on a datasheet. * Frost, wind, rain and leaf wetness — inside the crop * One battery per season, one bolt per station * Readings exported as CSV, PDF or through the API ``` Example 2: ```mdx We promise that a station keeps measuring when the network is down, that a sensor can be replaced by the person who found the problem, and that the data leaves with you if you leave us. We do not promise a forecast that is right every time. Nobody can. What we can do is tell you what is happening in your field right now, minutes after it starts happening. ``` Example 3: ```mdx ``` ### ProseAside Sub-block of . ProseAside — a card floated beside the text of a : a quote, a picture, a callout. The text flows around it. Parent: only — put it right after the opening tag and give the section width="wide", or the pair will not fit. Children: what the card holds — typically one , or markdown (a paragraph, a picture written as markdown). Side: right by default; side="left" floats it left. Why a tag and not a named slot: `slot="aside"` does not reach `Astro.slots.has()` from MDX, so content written by hand could never turn the two-column shape on. A tag works from MDX and from Astro alike. Props: - side ('right' | 'left', default 'right') — which side of the text the card floats to ### ProseItem Sub-block of . ProseItem — a titled sub-section inside : a subheading, markdown, an optional picture and an optional button. Several of them stack inside ONE section with a normal vertical rhythm. Use for: an "about" page with three themes, a certification page with one block per certificate, a services description — anything that would otherwise become a run of separate sections. Parent: only (usually ). Children: markdown between the tags. Picture: `image` (file name in images/) is shown under the text of this item. Props: - title (string) — the subheading - image (string) — file name in images/, shown under the text - linkText (string) — text of a button under the item; shown only with href - href (string) — link of that button Example: ```mdx Stations go up while the ground is still hard: one bolt, one scan, and the thresholds from last year are already there. The dashboard is quiet on purpose. It speaks when a field crosses a line you drew, and stays out of the way otherwise. The season is exported in one click and compared with the ones before it. The stations stay where they are. ``` ### MediaSplit MediaSplit — text on one side, a picture or a YouTube video on the other: heading, paragraphs or a list, buttons. Use for: one point of a landing explained next to what illustrates it — an illustration, a screenshot, a demo video; alternate `side` between neighbouring blocks for the zig-zag rhythm. Not for: a first screen (); figures beside a photo (); a flagship screenshot bleeding off the screen (); a video on its own (