List of Best Practices

1. Use absolute paths for every reference (links, assets, fragments).
2. Keep all static or SEO-critical content in the base HTML file.
3. Leverage SEO-friendly URL elements: breadcrumbs, JSON-LD structured data, XML sitemaps.
4. Store each fragment type in its own clearly-named folder.
5. Add target to every internal link; omit the attribute on external links.
6. Create and deploy /404.html in the site root.
7. Link at least one CSS file statically in every page.

Suggestions

When creating a website with Fragmanium, planning is essential. Before jumping into development, decide how many sections your site needs, which ones should load statically, and which parts will be repeated or require maintenance. Build reusable snippets for common tasks—starting without a plan often leads to rework and extra effort.

Fragmanium has a very small learning curve and is simple to master, so take the time to learn it thoroughly and understand its philosophy.

Avoid using static import statements inside fragments. If you must import at runtime, use dynamic import() and prefix any global object with top. (e.g., top.document.body). Fragmanium JavaScript fragments are already modular.