Features & lists
Grids and lists of benefits, services, steps, products, checklists.
FeatureCardspopularsections/FeatureCards.astrosub-blocks: Featureon 4 sites of the fleet
FeatureCards — a grid of cards, one <Feature> 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 (<FeatureList>, no cards); one topic explained in several points beside a heading (<FeatureAside>); a numbered process (<Steps>); a choice between two or three things (<Compare>). Children: <Feature> 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 <HeroCover> 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.
WHY NORDVIND
What the station actually changes
Frost alerts
Threshold, rate of fall and dew point, checked every minute inside the crop.
Leaf wetness
Tells you whether the spray will hold before you fill the tank.
Offline buffer
The gateway keeps a week of readings when the uplink drops.
FeatureAsidepopularsections/FeatureAside.astroon 2 sites of the fleet
FeatureAside — the heading, a paragraph and an optional picture on the left; a dense icon-and-text list of <Feature> 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 (<FeatureCards>); a numbered sequence (<Steps>). Children: <Feature> 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.
IN THE FIELD
Small enough to forget, stubborn enough to trust
The parts that matter are the ones you never think about: the seal, the mount and the radio.
Sealed to IP67
Rain, dust and a pressure washer at the end of the season.
Four kilometres
Line of sight to the gateway, on a licence-free band.
Field calibration
Swap a sensor and the station recognises it by itself.
FeatureListsections/FeatureList.astro
FeatureList — the <Feature> 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 (<FeatureCards>). Children: <Feature> 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.
WHAT YOU GET
Everything a station needs, nothing it does not
Readings every minute
Air and soil temperature, humidity, wind, rain and leaf wetness.
Alerts that reach a person
Rules per field, per crop and per shift — not one address for everything.
A map that means something
Stations, gateways and the last time each of them spoke.
FeatureSectionsections/FeatureSection.astrosub-blocks: FeatureItemon 1 site of the fleet
FeatureSection — a wrapper for one or more <FeatureItem> 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 (<FeatureCards>); a picture beside plain text (<Prose> with an image or <StatsSplit>). Children: <FeatureItem> 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.
Own the readings, not a subscription to them
Export the season as CSV, hand it to your agronomist, or pipe it into the tools you already run. Nothing is locked behind our dashboard.
ChecklistSectionpopularsections/ChecklistSection.astrosub-blocks: ChecklistItemon 2 sites of the fleet
ChecklistSection — a heading on the left and a three-column grid of check-marked points (<ChecklistItem>) 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 (<FeatureCards>, <FeatureList>); an ordered process (<Steps>). Children: <ChecklistItem> 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.
Before the first frost night
Twenty minutes of preparation that decide how the night goes.
- Check the battery level
- The dashboard shows it per station; anything under a fifth gets a replacement.
- Set the threshold per field
- The lower field freezes first — give it its own rule.
- Name the people on duty
- An alert that reaches everyone reaches nobody.
- Test the siren
- One button in the app, once a season.
Stepssections/Steps.astrosub-blocks: Stepon 1 site of the fleet
Steps — a numbered how-it-works list: circle badges numbered automatically, a title and a short text under each (<Step>). 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 (<Workflow>); unordered points (<FeatureList>). Children: <Step> 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).
From the box to the first reading
About an hour, most of it walking to the field.
Mount
One bolt on a standard post, antenna up.
Scan
The code on the housing pairs the station with the farm.
Set the rules
Pick the thresholds that matter for this crop.
Forget it
The next thing you hear from it is an alert.
Workflowsections/Workflow.astrosub-blocks: WorkflowStepon 1 site of the fleet
Workflow — a horizontal process chain on a dark stone band: numbered circles joined by arrows, one short label each (<WorkflowStep>). 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 (<Steps>). Children: <WorkflowStep> tags only; three or six fit a row best (six per row on desktop, three on tablets). Numbering and arrows are automatic.
How a reading reaches you
- Station
- Gateway
- Cloud
- You
Source links point to engine-astro@7b686388. Samples are demo content: the components are the real ones, the copy and the pictures are made up.