Feedhaus

Yes. The structure is curriculum, paths, templates, team, pricing, contact and FAQ, and that holds for photography, bookkeeping or podcasting just the same. What is cut for social media are the eight levers, the four platforms and the HTML visuals such as the calendar and the phone. The copy sits in four data files, and the visuals can be kept, rewritten or removed. The start skill says up front how big the rebuild will be.

All eight sit in hebel.ts, one entry each with title, introduction, key sentence, sections, checklist and key figure. From that entry come the tile on the home page, the row in the progress list, the page of its own under /tipps/ and the references on the platform pages. Six modules instead of eight levers means six entries, and the progress ring and percentage calculate themselves. The copywriting skill writes the guides to your brief.

Recoloring yes, in one file. Navy, indigo, periwinkle and the glass surfaces sit as variables. The five 3D icons carry their own gradients in one component and are recolored there separately. A fully dark presence is more work, because the white cards, the shadows and TikTok's platform color are made for the light ground. The design-system skill knows both routes and checks the contrasts along the way.

They get replaced or deleted. The 1,200 participants, the 92 percent recommendation rate, the six testimonials, the eight wordmarks in the logo band, the timeline and every key figure on the levers are examples and are labelled as such on the page. The knowledge layer explains why unlabelled invented reviews break competition law and why a money-back guarantee is a contract, not a marketing line.

Only in the draft. The four portraits and the working photos come from Unsplash and ship in the package so the site looks finished when unpacked. There is no model release, so no right to show real people under an invented name as your team. That is why the testimonials carry monograms instead of photos. Before going live your own images go in, and the knowledge folder describes the sizes.

In the package both forms show a success message after submitting, nothing more. That is deliberate, so the site runs on any host. For production you connect a form service, a script from your host or your own endpoint; the knowledge folder describes three routes. The checklists on the lever pages do not save their ticks either, and the page says so.