content: say that OCPP chargers need no driver, and link the guide

[HuggeK]

FTW ships a built-in OCPP Central System (1.6J and 2.0.1), so an EV charger that speaks either connects directly and needs no Lua driver. The site never said so anywhere — a visitor asking "do I need a driver for my charger?" had no way to find the answer, and "OCPP" did not appear on the page at all.

This adds the claim where it is actually load-bearing, and links docs/ocpp.md.

What changed

• Integrations card (06 / CONNECT) — now says OCPP 1.6J and 2.0.1 chargers need no driver; the meta line reads HTTP · MQTT · OCPP · Lua.
• Build-with-it section — a fourth checklist item ("Skip the driver entirely for an EV charger that speaks OCPP") and an OCPP chargers ↗ link beside Write a driver and Browse drivers. This is the section a reader is in when the question occurs to them.
• Architecture map — the EV output node reads OCPP / V2X instead of load / V2X.
• <meta> description and keywords — OCPP, OCPP 1.6J, OCPP 2.0.1 added, so the page is findable by people searching for exactly this.

Why this is not a seventh capability card

.capability-grid is grid-template-columns: repeat(3, 1fr) with border-drawn cells, and there are currently six cards — two clean rows of three. A seventh would strand one card alone on row three (and alone again in the two-column breakpoint at max-width where it becomes 1fr 1fr). Going to nine would mean inventing two capabilities that do not exist.

Folding the fact into the card that already covers integrations keeps the grid rhythm intact and puts OCPP next to HTTP and MQTT, where it belongs.

Note on card height

Card 06's paragraph grows by roughly one line. .capability-grid article is min-height: 300px with code { margin-top: auto }, so the card absorbs it and the row sizes to its tallest member; rows are independent, so row 1 is unaffected. The sentence was deliberately kept short for this reason.

Review note

This is a visual change and I have no browser in this environment, so the layout reasoning above is from the CSS rather than from a render. Please eyeball the capabilities grid and the Build section before merging — particularly that the three .inline-actions links still sit on one line at desktop width.

Upstream context: srcfl/ftw#732 adds the OCPP server this describes.

🤖 Generated with Claude Code

[miravoss26]

Marketing copy only: adds OCPP language to the meta description/keywords, the EV-charging map node label, the "Open integrations" capability copy, and a new "skip the driver" bullet + link to srcfl/ftw/docs/ocpp.md. No code, no config, no build files touched.

• Content checks out against what already shipped (OCPP support in ftw core) — not overselling something unbuilt.
• The new docs link (github.com/srcfl/ftw/blob/master/docs/ocpp.md) — worth a human eyeballing that it resolves; I can't fetch it from here.
• No security surface: static HTML copy edit, no scripts/attributes changed.

Safe to merge from my read, modulo confirming that one doc link resolves.