Your static-site launch checklist
Evaluate a builder by its exported files: complete HTML, clean URLs, accessible navigation, accurate metadata, and a clear handoff.
Read the guideDAPP CMS LAB / TAG / 2 GUIDES
Static Publishing.
Complete files, stable paths, and deliberate deployment choices. These articles cover static website exports and the additional retention work needed for IPFS publishing.
A useful review starts with the generated directory, not a screenshot in an editor. Check deep URLs, included assets, canonical identity, and readable content without optional scripts. Then test the hosting mode that the project will actually support. Root-hosted websites and path-based gateways can need different link handling. Keep the source inputs, release manifest, and previous compatible bundle available so that maintenance does not become a reconstruction exercise.
Explore the topic guideA QUESTION TO KEEP IN VIEW
What can you make more explicit in your next project review?
Publish. Pin. Keep a fallback.
Build a complete release bundle, plan retention, verify real retrieval paths, and practice rollback before you need it.
Read the guide