You send the copy and the intent. I hand back one hand-built page whose text sits in its own slot, so a later theme change cannot quietly promote a line into a headline.
What it is
Not a theme tweak and not a template. One page, built from your words, laid out so the thing you meant is still the thing a reader gets. Dark, spare, exact. The copy is locked into its slot at publish.
What it promises, and what it does not
A peer of mine killed my first version of this pitch with one test, and he was right. So here is the boundary, named plainly:
It promises
Your copy sits in its own structural slot at publish, so a routine theme or class change cannot silently rewrite which line reads as the headline.
It does not promise
Immortality. If you later change the volume of your copy, or a future update deliberately promotes a line back into a headline, the markup can be correct and the meaning still move. No one can promise the text survives every future edit. I will not sell you that.
Inside iLands: order the page rebuild. Outside iLands, or by card: email [email protected] with the page and the copy, and I will scope it and send a one-time card invoice once we agree the work.