FIELD GUIDE / 01
Hosting & CDN
Choose where your files live, how they are cached, and what happens when you publish a change.
Explore deliveryAN INDEPENDENT GUIDE TO THE STATIC WEB
Build light.
Think global.
A clearer path to static websites. Explore hosting, CDNs, CMSs, and templates—and make your next build easier to understand, publish, and maintain.
Practical explanations. Useful tradeoffs. Open possibilities.
DESIGN → CONTENT → FILES → DELIVERYILLUSTRATED WORKFLOW
01 / UNDERSTAND THE STACK02 / CHOOSE YOUR WORKFLOW03 / PUBLISH WITH INTENTION
01 / YOUR STARTING POINT
One web.
Many good ways to build.
Every static project is a set of choices. Find the layer you’re working on, understand its tradeoffs, and connect it to the rest of your site.
FIELD GUIDE / 02
Content & CMS
Give editors a clear path from draft to published page, with a content model that stays maintainable.
Find your CMS approachFIELD GUIDE / 03
Templates & builders
Explore HTML, Hugo, and Astro workflows. Choose structure and usability before decorative polish.
Explore templatesFIELD GUIDE / 04
WordPress to static
Audit your existing site, account for dynamic features, and verify every important page after export.
Plan your migrationFIELD GUIDE / 05
AI web design
Turn a focused brief into a reviewed design. Keep accessibility, factual accuracy, and human judgment in the loop.
Build a review workflowFIELD GUIDE / 06
Website ownership
Understand the files, domain, licenses, and access behind a website—including the limits of tokenized claims.
Understand ownership02 / DELIVERY, WITHOUT THE MYSTERY
Your files.
A sensible
delivery plan.
Static hosting is about serving published files. A CDN adds a caching and delivery layer. Cloud hosting describes the infrastructure underneath. Understanding the difference helps you ask better questions.
- Match cache rules to how often each file changes.
- Check domains, HTTPS, releases, and rollback support.
- Evaluate total cost and operational work together.
A SIMPLE OUTPUT. A CLEAR JOB FOR EACH FILE.
- index.html
- The homepage
- about/index.html
- A clean page URL
- assets/styles.css
- The visual language
- assets/site.js
- Focused interactions
- sitemap.xml
- A map for crawlers
03 / MAKE THE MOVE
From WordPress
to a considered static site.
A successful conversion preserves what matters: content, URLs, usable navigation, and a practical way to publish the next update.
Know what moves.
List the pages, media, URLs, and dynamic features your visitors actually use. Keep a copy of the starting point.
Audit the siteExport with a plan.
Choose a page export or a generator rebuild. Keep a written plan for features that need a different implementation.
Choose an approachCheck the details.
Test links, images, mobile content, metadata, and keyboard access against an explicit acceptance list.
Use the checklistKeep a way back.
Ship a versioned set of files. Confirm delivery, retain the previous release, and repeat the checks after launch.
Plan deployment04 / FIND YOUR BUILDING BLOCKS
Good structure.
Your own expression.
Choose a template workflow around content and maintenance. These guides explain what to inspect before a design becomes your website.
HTML WORKFLOW
Direct, editable files.
For a focused site, start with semantic pages and shared styles. Review the complete output before you commit.
Read the HTML guideHUGO WORKFLOW
Content takes the lead.
Explore layouts, content types, taxonomies, and a repeatable publishing workflow for a growing library.
Read the HUGO guideASTRO WORKFLOW
Static, selectively interactive.
Consider a component workflow when a mostly static site also needs a few carefully chosen interactive elements.
Read the ASTRO guide05 / IDEAS NEED A WORKFLOW
Let AI help.
Keep your judgment.
Use a written brief, a structured content model, and a human review gate to turn fast drafts into deliberate publishing decisions.
Design with an acceptance list.
Review the small screen, the keyboard journey, the meaning of the content, and the final output. A compelling first draft is the beginning of a design process.
Explore AI web designGive content a human owner.
Separate drafting, checking, approval, and publication. Keep source notes and a clear revision history as content moves through your static CMS.
Explore AI-assisted CMSFIELD NOTES & PRACTICAL GUIDES
Go deeper in the Lab.
CDN caching for static websites: a practical guide
Build a cache policy around how your site changes, then verify the actual responses and rehearse a release and rollback.
Read the guide
Hugo vs Astro: choose a static-site workflow
Choose between Hugo and Astro by testing the work your team actually does: editing content, changing layouts, adding interaction, and shipping static files.
Read the guide
A practical AI web design review workflow
Turn AI design suggestions into specific, reviewable improvements using page goals, representative evidence, small patches, and real browser checks.
Read the guideTHE QUESTIONS WORTH ASKING
Start curious.
Leave clearer.
Understand the moving parts before you choose the tools.
What is StaticGlobal.com?
StaticGlobal.com is an independent guide to static publishing. Explore how hosting, CDNs, content management, templates, migration, and AI-assisted design fit together, then use the detailed guides to plan your own project.
Does a static website need a backend?
A published static page can be delivered as HTML, CSS, JavaScript, and media files. Features such as private accounts, transactions, or shared live records need additional services. The Static Global overview explains where that boundary matters.
Can WordPress be converted to a static site?
Public pages can be exported or rebuilt, but a migration also needs a plan for search, forms, logins, comments, and any other dynamic features. Begin with the WordPress migration guide and validate a representative sample before a full move.
How do I choose between Hugo, Astro, and plain HTML?
Start with who edits the content, how often the site changes, and which interactions it needs. Plain HTML offers direct control, while generators introduce reusable templates and content workflows. Compare the tradeoffs in the Hugo and Astro guide.
Do you provide hosting accounts or an online converter?
The pages here explain how to evaluate and use those approaches. This site provides guides and checklists; provider-specific accounts, conversion tools, or hosting plans are chosen separately.
Where should I start?
Choose a topic above, or visit the Static Global starting guide. For a project already on WordPress, start with migration. For a new site, begin with content, templates, and hosting requirements.