Word Puzzle Helper Starter Kit 1.0.0

• Responsive word puzzle helper template files.
• Words-from-letters, unscrambler, missing-letter, letter-wheel, 5-letter, and 6-letter modes.
• Offline-friendly installable app files, manifest, service worker, icons, robots file, and sitemap.
• Optional embed.html page that contains the word solver, required assets, and an optional link back to the full site.
• Privacy, terms, and contact pages inside the generated website.
• Local fonts, bundled word list, third-party notices, accessible form labels, and keyboard-friendly controls.
• Dark default theme, light theme, and an icon-only theme toggle.
• Customization metadata for brand, domain, SEO text, colors, app details, embed output, contact wording, optional code snippets, and optional ad placements.

Static website means the generated site is made from normal files: HTML, CSS, JavaScript, images, icons, robots.txt, sitemap.xml, and related assets. It does not need WordPress, a database, or a custom server app.

PWA means Progressive Web App. It is still a website, but supported browsers can offer app-like features such as an install shortcut and cached files after the site is served from a local static server or an HTTPS host.

Manifest is the small file browsers read for the app name, icons, colors, and install details. Service worker is the browser script that can cache files for faster repeat visits and offline-friendly behavior.

Cache prefix is a short unique name used by the service worker so this site's cached files do not collide with another site you publish.

Embeddable output means the generated ZIP can include an embed.html page that removes the full homepage frame and leaves the interactive word solver for iframe embeds or focused landing-page sections. It can also show a small link back to your canonical homepage.

Public embed code means the full homepage can show an optional panel with an embed.html link and iframe snippet. Use it only when you want visitors, partners, or teammates to copy the embed details from the public page.

The customizer reads the template package in your browser and builds the form from the included metadata. Enter your brand name, short mark, domain, contact method, SEO title, description, hero copy, default theme, theme colors, app name, and cache prefix.

The embed page toggle is on by default. Leave it enabled if you want embed.html in the generated ZIP. Turn it off when you only need the full-page site. The embed backlink toggle is also on by default and adds a small link from embed.html to your canonical homepage.

The public embed-code toggle is off by default. Enable it only when the full homepage should show a public panel with an embed link, iframe code, and copy buttons. This panel does not create embed.html; the tool-only embed page toggle does that.

The selected default theme and accent colors are used by both the full pages and embed.html, so embedded placements keep the same visual identity as the main site.

Optional code and ad fields are disabled by default. Enable only the spots you need, paste complete script, style, meta, or ad tags, and leave everything else off so no empty ad containers appear in the generated site.

Required fields, URL shape, domain format, cache prefix, important color contrast pairs, and obvious snippet problems are checked before the customized ZIP is created.

When enabled, embed.html is a compact tool-only page for iframe embeds, CMS blocks, partner pages, or focused landing-page sections. It keeps the word solver and required assets while removing the homepage hero, tool cards, support copy, FAQ, footer, and other surrounding content.

The embed page uses the same default theme and accent tokens as the full site. Preview it in a narrow iframe or sidebar-sized viewport if you plan to embed it inside a CMS block, blog post, or partner page.

If the embed backlink option is enabled, embed.html shows a small branded link below the solver that opens your canonical homepage in a new tab. Turn that option off when the host page already provides enough attribution or when you need the cleanest possible iframe.

Example iframe code:

<iframe
  src="https://example.com/embed.html"
  title="Word puzzle solver"
  loading="lazy"
  style="width:100%;min-height:900px;border:0;"></iframe>

Test the iframe on desktop and mobile after hosting. If your host or site builder restricts iframes, link directly to embed.html or paste the generated page into a controlled landing-page section instead.

For an iframe to work, the page at embed.html must be served by a host that allows framing. Some hosts, CDNs, and site builders send X-Frame-Options or Content-Security-Policy with a restrictive frame-ancestors rule. If the iframe is blocked, update those host settings, allow the domain that will embed the tool, or use a host that permits iframe embeds.

If you enable the public embed-code panel, the generated homepage shows visitors the direct embed link and iframe code. Keep it off when the solver is only for your own site or when you do not want third parties embedding it.

• Open the generated homepage directly for a quick content and layout review.
• Open embed.html and confirm the stripped tool-only output is present if you enabled it.
• If you enabled the public embed-code panel, copy the iframe code from the homepage and test it inside the actual page builder, CMS, or partner site where it will be embedded.
• Check privacy.html, terms.html, and contact.html for your actual contact wording and service providers.
• Open manifest.webmanifest and confirm the app name is correct.
• Open sitemap.xml and robots.txt and confirm the public domain is correct.
• Search the generated files for {{. There should be no placeholder tokens left.
• If you added analytics, ads, or custom scripts, test the live hosted page and confirm those providers load as expected.
• Check dark mode, light mode, mobile width, keyboard focus, and link text before publishing.

The starter kit code, original template content, and original visual assets are licensed under the included LICENSE file. Bundled third-party fonts and the bundled English word list keep their own licenses.

Keep THIRD-PARTY-NOTICES.txt with the starter kit and with generated websites. It documents the local Atkinson Hyperlegible and Fraunces font files, plus the filtered word-list v4.1.0 dictionary used by the solver.

The generated site can be opened directly from your computer for a quick preview, but browsers do not install PWAs from file:// pages. The app manifest, install prompt, and service worker need the site to be served from a local static server while testing or from an HTTPS host after launch.

If you see browser console messages about a manifest being blocked from a file URL, upload the site to hosting or test it through a local static server before checking install behavior.

This is a static website. You do not need WordPress, a database, or a server app. Upload the generated website files to your public web folder, often called public_html.

These files should be at the site root after upload:

• index.html
• privacy.html
• terms.html
• contact.html
• embed.html, if enabled
• manifest.webmanifest
• robots.txt
• sitemap.xml
• service-worker.js
• assets/

Hostinger is the recommended host for this starter kit because it is straightforward for small static websites and beginner-friendly launches.

Affiliate disclosure: the Hostinger link is an affiliate link. A commission may be earned if you buy through it. You can use coupon code MILLIONDOLLARS for the current discount available through that link.

Open Hostinger

The customizer is the recommended path. If you edit manually, open the template folder and search for {{. Replace every placeholder before publishing.

Common placeholders include:

• {{BRAND_NAME}}
• {{CONTACT_METHOD}}
• {{CANONICAL_URL}}
• {{PRIMARY_COLOR}}
• {{APP_NAME}}
• {{CACHE_PREFIX}}

Custom setup, deployment help, and new niche tool builds are available at ryanrhode.com.

This starter kit is not legal, tax, advertising, or SEO advice. Review your own privacy policy, terms, ads, analytics, affiliate disclosures, local laws, and hosting terms before publishing.