1. Map the visitor journey
Write one sentence: “Visitors should read my portfolio and contact me”, or “They should book and manage an account”. If you need an on-chain feature, identify the state that must be verifiable and who may change it.
Separate public pages from private records. Quote requests, personal documents and passwords do not belong in a public website package. Never put secret credentials in JavaScript delivered to a browser.
2. Prepare the content
A static website contains HTML, CSS, JavaScript, images and other files. A CMS or database-backed application may require a running server. Exporting its visual pages does not necessarily export the original service’s functionality.
For a first exercise, create a page with a title, description, contact method and links. Check alternative text, contrast and button sizes. An advanced domain cannot compensate for incomplete content or a page that is unreadable on a phone.
3. Choose how to make it available
HTTPS hosting: upload files or deploy the application to a service that serves them on the Web. Configure DNS, TLS certificates, backend services and databases according to the provider.
IPFS: content receives a content identifier, or CID. To keep it retrievable, arrange persistent storage, for example through nodes that pin it. Changing files creates new content and normally a new CID.
IPFS does not automatically run PHP, a Node.js server or a private database. A frontend can call external APIs, whose availability then remains a dependency.
4. Connect the name
- For a DNS domain, configure the records required by the hosting service and verify HTTPS.
- For a blockchain name, check the holder, network and supported record types.
- Set the appropriate reference: destination URL, IPFS/contenthash reference or another compatible record.
- Approve only the intended operation with an account that has the required permissions. Check the transaction result.
- Document a working visitor route: HTTPS URL, gateway or required integration.
5. Test the complete journey
- Open the site on another device and outside your management session.
- Check links, images, forms and internal pages, not just the homepage.
- Test the HTTPS URL, Web3 name and wallet record separately: one can work while another does not.
- If using a gateway, also verify retrieval of the expected CID and plan an alternative route.
- Review updates, backups and who can publish or change records.
A route through the Web3Domain ecosystem
You can search for a name on Web3Domain, prepare a site with Web3App, and check its access route using Browser.Web3Search. Available functionality depends on the site format, configured records and compatible services.
A bridge does not turn a blockchain name into a globally delegated DNS domain or replace file persistence. To help discovery, publish a stable HTTPS link, readable content and appropriate metadata; owning a domain does not guarantee indexing.
Before and after an update
Answers to common questions
Can a Web3 domain point to my existing Web2 website?
Yes, if its naming system supports a suitable redirect record or integration. Visitors need a route that can resolve the name. The destination remains the existing website.
Can I copy WordPress to IPFS and keep every feature?
A static export can preserve pages and assets, but PHP, databases and dynamic operations require a separate architecture. Those features must be redesigned or retained on compatible services.
Does publishing on IPFS keep files forever?
No. A CID identifies content, but availability depends on who stores and provides it. Plan pinning, backups and monitoring.
Sources and further reading
Primary documentation consulted for this guide. Product, network and integration support can change: check current requirements before configuring a service.