What you get
A self-contained theme directory you can drop into wp-content/themes and activate. It includes:
- style.css — with a proper theme header (name, description, version) so WordPress recognises it.
- functions.php — enqueues Bootstrap 5 and the theme's own CSS/JS, registers menus, and sets up image sizes.
- header.php and footer.php — the global chrome lifted from your design, with menu locations registered for editing in the WordPress admin.
- Page templates — one per page in your design, mapping to the routes WordPress expects (
front-page.php,page.php,page-{slug}.php). - Editable regions — text and image areas are wrapped so the client can edit them through the WordPress dashboard, not the code.
Why bother
A static Bootstrap site is great when you're shipping a one-off marketing page. But the moment a client says "I want to update the homepage copy myself", static HTML stops being the right tool. Wyvid's WordPress output gives you the same clean Bootstrap markup with the editing experience that non-technical clients actually use.
It's an opt-in
You don't need to use the WordPress option if you're not going to ship on WordPress. By default Wyvid produces just the static build — a folder of HTML, CSS, and assets. Toggle the WordPress switch when creating a site and you get the theme in addition to the static output.
What we don't do (yet)
Wyvid doesn't ship custom post types, ACF blocks, or Gutenberg block bindings yet — the theme is built around classic page templates. If your client's site needs a custom blog structure or complex editorial flow, you'll likely want to extend the theme by hand once it's generated. That extension is straightforward because the markup is clean and the file structure follows WordPress conventions.