Everything that is a decision, a cut, or a missing asset. None of this appears on the page itself.
Ezra told Crowd Supply in May there would be three pledge levels, the middle one being a board plus an unassembled shell. It has never been priced and is not on the website. The draft assumes it dies and shows two.
This blocks issue #9, and #9 blocks the campaign page. Chris also said he expects the fully assembled unit to outsell the others significantly and offered to simplify the lineup for you.
Deliberately absent from the spec list. The Home Assistant repo says its pin sits on ADC2, which the WiFi radio owns, and that it moves to ADC1 next revision. If the shipping revision has it on ADC1, it goes in the spec list. If not, leave it out rather than field the complaints.
Studio was promised to the whole list in the Aug 21 email and it currently has its own section on this page. Either it ships and we screenshot it, or the section softens to a sentence in the software paragraph. Do not put a mockup on a funding page and present it as a product.
The Support and Documentation section says the design files go public before units ship. Two things make that not true yet. OpenMote-internal-hardware is still private, and it carries Apache 2.0, which is a software licence. Pick CERN-OHL or a Creative Commons licence.
The Discord in that same list does not exist yet either, and it was promised in the Aug 28 email.
I checked the raw HTML of three real Crowd Supply pages, including your own pre-launch page. Every single video embed is Vimeo or YouTube.
Zero Instagram, zero TikTok anywhere. Their markdown has a ~~~ vimeo: ~~~ block and no equivalent for Instagram. So the Linus Tech Tips and Brett Tech reels go to Chris as links for the In the Press block, which Crowd Supply generates itself and which takes URLs rather than embeds. If you want either clip in the body of the page, mirror it to YouTube or Vimeo first.
Four, all designed for this page at 1512 px wide so they land at exactly 2x in the 756 px column, with zero horizontal padding so their text lines up with the body copy. They carry no headings and no sentences. A graphic that repeats the paragraph above it is just a second paragraph in a worse font.
Infrared was cut. Two attempts, both unreadable. The copy carries that section and the learning photograph goes on the shoot list. A bad diagram is worse than no diagram.
Source is graphics.html in this folder. Ordinary HTML, edit and re-render.
Every photograph on this page is one of the eight already live on your Crowd Supply pre-launch page. I pulled the list straight out of that page's HTML rather than picking from the folder. Seven are used, the eighth is the raw Arduino IDE screenshot, which our own editor graphic replaces.
Nothing is cropped and nothing is portrait. Every image is checked against a 520 px ceiling in the 732 px column, and the tallest on the page is 412 px. The earlier draft had a portrait file rendering 1301 px tall, which is the full-screen scroll you hit.
The pledge tier images are now proper 16:9 tiles, which is the format Crowd Supply uses for product listings, built from the two images the waitlist survey used.
Modelled on MNT Reform, which is the most successful campaign on the platform. It runs intro, then a block of short use-case sections each with one image, then specs broken into subsystem headings, then the four business sections Crowd Supply requires. Precursor uses the same shape. Both sit between 4,000 and 5,200 words with 46 to 86 images.
Home Assistant comes second, immediately after the intro, rather than being buried in a lifestyle paragraph the way the February draft had it. It is your strongest wedge, the Home Assistant community is a named launch channel, and it is the highest value search term you can own. It is bolded on first use, the same as on the website.
Crowd Supply generates the H1, the tagline, the price block, In the Press, About the Team and Ask a Question. The file you hand them is body only, H2 for sections, H3 for sub-sections, image filename alone on its own line where a photo goes.
The body is now about 3,300 words. MNT Reform is 5,151 and Precursor is 4,040, so this sits just under the pages it is modelled on and comfortably above ANAVI Handle at 1,407. The remaining gap is almost entirely captions and the two sections that cannot be finished until there is material to show, gaming and Studio.
No. The site has a badge set, the gamepad, house, infrared, robot and wand marks, and none of it belongs in the body of a Crowd Supply page. Neither MNT Reform nor Precursor uses a decorative icon system, because on that platform an icon next to a heading reads as filler rather than as design. The icons that do appear on this page are the real platform logos inside the smart home graphic, where they are doing actual work by telling somebody their ecosystem is supported.
campaign-body.md in the repo root is the file Crowd Supply actually needs, and it now matches the preview exactly. It uses their conventions, image filename alone on its own line per issue #12, and ~active / ~success / ~warning / ~danger cell markers in the comparison table.
The image filenames in that file are the target names for the finished assets, so they will not all match what is currently sitting in the preview folder. Rename on delivery.