Documented case 1 · The first website at CERN
Goal: explain the World Wide Web project and link documents. Architecture: pages and hyperlinks served from a computer and accessed through browsers. CERN documents the first website, devoted to the Web itself, at info.cern.ch.
Lesson: useful information and shareable links create value. Reading a document does not require an account or token. An instruction site or public archive can still benefit from a simple architecture with modern tooling and security.
Documented case 2 · A wiki using MediaWiki
Goal: let multiple people contribute to pages. Architecture: an editing interface, application software and revision storage. MediaWiki documentation describes editing and saving within a site’s permissions.
Lesson: readers can become authors. Collaboration and history depend on the application and its rules; the DNS name routes traffic but does not decide who may edit. A Web2 project can be open and community-operated.
Documented case 3 · An ENS name and its contenthash
Goal: connect a readable name with distributed content. Architecture: a contenthash record identifies the content, and a compatible interface or gateway makes it accessible. ENS documents this approach for decentralized websites.
Lesson: the naming registry and website files remain separate. Updating a record does not preserve its content; publishing a CID does not make every browser resolve the name. This is an architectural example, not a promise of compatibility for every TLD.
Workshop A · A simple portfolio
Show three projects and a contact
Create a static page with optimized images, descriptions and a contact link. Publish it over HTTPS using a DNS domain. Test without JavaScript: essential information should remain readable.
Reasoning: nobody needs to change shared state, so a blockchain is unnecessary. Final check: mobile layout, working URLs, a clear title and a reachable contact.
Workshop B · A booking service
Manage availability and requests
Design a public page, a form and an administration area. The backend validates data and stores requests in a database; permissions distinguish customers and administrators. Use fictional data in the prototype.
Reasoning: the task needs frequent updates and private data handling. Final check: no double bookings, correct access and clear confirmations. A Web3 name can provide another entry route without changing the backend.
Workshop C · A portfolio with a verifiable certificate
Publish the work, verify a record
Keep public pages on hosting or IPFS. Where the use case needs shared verification, design an on-chain record representing the certificate, without putting personal documents in plaintext on-chain. An HTTPS page explains the issuer and verification steps; a Web3 name can point to it.
Reasoning: the blockchain component supports record verification, not replacement of every service. Final check: consistency between issuer, record, files and interface. An immutable record does not make a false statement true.
Describe your project in six answers
- Who visits the site and what do they need?
- Which data is public and which is private?
- Who can change it and who can verify the change?
- Which domain and resolution path will visitors use?
- Which parts depend on hosting, gateways, APIs or blockchain?
- How will you recover if a dependency stops working?
When you can answer these questions, you can choose an architecture. Technology cannot substitute for a missing answer.
Answers to common questions
Are these all Web3Domain client projects?
No. CERN, MediaWiki and ENS are documented examples from primary sources. The three workshops are original learning scenarios, not claimed clients or commercial results.
Does a blockchain certificate prove a person is qualified?
On its own it only establishes what the system allows you to verify about the record. You must assess the issuer, their checks and what the statement actually means.
Can I start with Web2 and add Web3 later?
Yes. You can retain existing content and services, adding a name, wallet login or verifiable feature where useful after checking the required integrations.
Sources and further reading
Primary documentation consulted for this guide. Product, network and integration support can change: check current requirements before configuring a service.