Skip to content

Commit 7a61437

Browse files
pawel-kowpawel-kow
committed
Final page for publish
1 parent c0e9b85 commit 7a61437

17 files changed

Lines changed: 539 additions & 164 deletions

‎.claude/settings.local.json‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
"permissions": {
33
"allow": [
44
"Bash(curl -s \"https://stats.domainconnect.org/stats.json\")",
5-
"Bash(.venv/bin/python3 -)"
5+
"Bash(.venv/bin/python3 -)",
6+
"Bash(.venv/bin/mkdocs build *)"
67
]
78
}
89
}

‎.github/workflows/pages.yml‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,15 @@ jobs:
3232
- name: Install dependencies
3333
run: pip install -r requirements.txt
3434

35-
- name: Build site
35+
- name: Build landing site
3636
run: mkdocs build --strict
3737

38+
- name: Build marketing site
39+
run: mkdocs build --strict --config-file mkdocs-marketing.yml
40+
41+
- name: Build implementers site
42+
run: mkdocs build --strict --config-file mkdocs-implementers.yml
43+
3844
- name: Setup Pages
3945
uses: actions/configure-pages@v5
4046

‎.gitignore‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,5 @@
11
.DS_Store
2-
docs
2+
docs
3+
.venv/
4+
.claude/
5+
__pycache__/

‎CLAUDE.md‎

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Project purpose
44

5-
This is a marketing knowledge base about the Domain Connect protocol. It serves as source material for LinkedIn posts, blog articles, conference presentations, partner outreach, and analyst briefings.
5+
This is a knowledge base about the Domain Connect protocol. It serves as source material for implementation work (DNS providers, service providers), protocol contribution and IETF participation, communications and marketing (LinkedIn posts, blog articles, press briefings), and conference presentations and partner outreach.
66

77
**Author:** Pawel Kowalik — co-author of `draft-ietf-dconn-domainconnect-01`. DNS concepts do not need to be over-explained. Content should reflect the perspective of a registry operator and protocol author.
88

@@ -110,19 +110,28 @@ The knowledge base is published as a static website using [MkDocs Material](http
110110
- Primary: `#03263B` · Secondary: `#0b3954` · Accent: `#00bfff` · Tertiary: `#bddae6`
111111
- Font: Open Sans 300/400/700 (Google Fonts)
112112

113+
There are two separate builds, each with its own MkDocs config:
114+
115+
| Config | Audience | Output |
116+
|--------|----------|--------|
117+
| `mkdocs-marketing.yml` | Marketing, comms, speakers | `docs/marketing-kb/` |
118+
| `mkdocs-implementers.yml` | DNS/service providers, protocol contributors | `docs/implementers-kb/` |
119+
113120
**Local development:**
114121
```bash
115122
python3 -m venv .venv # first time only
116123
.venv/bin/pip install -r requirements.txt
117-
.venv/bin/mkdocs serve # live-reload at http://127.0.0.1:8000
124+
.venv/bin/mkdocs serve --config-file mkdocs-marketing.yml # http://127.0.0.1:8000
125+
.venv/bin/mkdocs serve --config-file mkdocs-implementers.yml # http://127.0.0.1:8000
118126
```
119127

120128
**Build:**
121129
```bash
122-
.venv/bin/mkdocs build --strict
130+
.venv/bin/mkdocs build --strict --config-file mkdocs-marketing.yml
131+
.venv/bin/mkdocs build --strict --config-file mkdocs-implementers.yml
123132
```
124-
Output goes to `docs/` (git-ignored on `main`).
133+
Output goes to `docs/marketing-kb/` and `docs/implementers-kb/` respectively (both git-ignored on `main`).
125134

126-
**Deployment:** Every push to `main` triggers `.github/workflows/pages.yml`, which builds the site and deploys it to GitHub Pages via the official `actions/deploy-pages` action. In the repository settings, Pages source must be set to **GitHub Actions**.
135+
**Deployment:** Every push to `main` triggers `.github/workflows/pages.yml`, which builds both sites and deploys the entire `docs/` tree to GitHub Pages. In the repository settings, Pages source must be set to **GitHub Actions**.
127136

128137
**Do not commit the `docs/` directory** — it is regenerated by CI on every deploy.

‎Knowledge Base/00_MASTER.md‎

Lines changed: 10 additions & 84 deletions
Original file line numberDiff line numberDiff line change
@@ -1,105 +1,31 @@
1-
# Domain Connect — Marketing Knowledge Base
1+
# Domain Connect Knowledge Base
22

33
**Version:** 1.0 | **Last updated:** May 2026
44
**Author:** Pawel Kowalik, Co-Author of Domain Connect specification
5-
**Sources:** APNIC blog article (Oct 2025), ROW presentation (Oct 2025), IETF-124 DCONN WG presentation (Oct 2025), IETF draft-ietf-dconn-domainconnect-01 (Mar 2026), IETF 123 WG transcript
65

76
---
87

9-
## About This Knowledge Base
10-
11-
This document is the master index for the Domain Connect marketing knowledge base. It is designed to serve as a comprehensive, authoritative source for:
12-
13-
- Social media posts (LinkedIn, X/Twitter)
14-
- Blog articles (technical and non-technical)
15-
- Conference presentations and talking points
16-
- Partner and registrar outreach materials
17-
- Press and analyst briefings
18-
19-
Each linked sub-document covers a specific angle in depth. This master document provides a concise overview and navigation guide.
20-
21-
---
22-
23-
## Quick Reference: What Is Domain Connect?
24-
25-
**Domain Connect** is an open-standard, application-level protocol that automates DNS configuration when a user connects a domain name to a third-party service (e.g., a website builder, email platform, or online store). It eliminates the need for users to manually create DNS records by enabling the service provider and the DNS provider to communicate directly — with the user simply giving informed consent.
8+
**Domain Connect** is an open-standard protocol that automates DNS configuration when a user connects a domain to a third-party service. It eliminates manual DNS record entry by letting the service provider and DNS provider communicate directly — the user just clicks "Connect" and approves.
269

2710
- **Originally proposed by:** GoDaddy, 2016
2811
- **Status:** Production-deployed; IETF standardization underway (DCONN working group, approved Oct 2025)
2912
- **Specification:** draft-ietf-dconn-domainconnect-01 (Standards Track)
13+
- **Scale:** ~20 DNS providers, 720 templates, 408 service providers, ~35% of .com zone covered
3014

31-
---
32-
33-
## Document Map
34-
35-
| # | Document | What it covers |
36-
|---|----------|----------------|
37-
| [01](./01_Problem_and_Context.md) | Problem & Context | Why DNS configuration is broken; domain growth & renewal data |
38-
| [02](./02_What_Is_Domain_Connect.md) | What Is Domain Connect | Definition, scope, what it is not, key concepts |
39-
| [03](./03_How_It_Works.md) | How It Works | Technical flows, templates, discovery, consent — explained accessibly |
40-
| [04](./04_Protocol_Features.md) | Protocol Features Deep Dive | All protocol features with technical detail |
41-
| [05](./05_Use_Cases.md) | Use Cases | Primary use cases, extended use cases, out-of-scope cases |
42-
| [06](./06_Value_by_Audience.md) | Value by Audience | What Domain Connect means for each stakeholder group |
43-
| [07](./07_Adoption_and_Ecosystem.md) | Adoption & Ecosystem | Current implementations, providers, standardization status |
44-
| [08](./08_Security_Model.md) | Security Model | Trust model, security features, known considerations |
45-
| [09](./09_Getting_Involved.md) | Getting Involved | How to implement, IETF participation, community resources |
46-
| [10](./10_Key_Messages.md) | Key Messages & Soundbites | Ready-to-use messaging for social posts, blogs, press |
47-
| [11](./11_Template_Reference.md) | Template Reference | Complete field-by-field reference for all template metadata and record flags |
48-
| [12](./12_Getting_Started_DNS_Provider.md) | Getting Started: DNS Provider | Step-by-step implementation guide for DNS Providers |
49-
| [13](./13_Getting_Started_Service_Provider.md) | Getting Started: Service Provider | Step-by-step integration guide for Service Providers |
50-
| [14](./14_Storytelling.md) | Storytelling | First-person stories for DNS/SP CEOs, PMs, support, devs; user stories; plain-language explainers |
51-
| [15](./15_Template_Use_Cases.md) | Template Use Cases | 9 use-case patterns from the template repository with examples, DNS setup guidance, and implementation notes |
15+
This knowledge base is published in two focused editions. Choose the one that matches your role:
5216

5317
---
5418

55-
## The One-Paragraph Summary
56-
57-
Half of all users who try to connect their domain to a service like Microsoft 365 give up before finishing — because DNS configuration requires expert knowledge most people don't have. Domain Connect solves this with a standardized protocol: the service provider defines a DNS template, the DNS provider vouches for and hosts it, and the user simply clicks "Connect" and approves. What used to take 40 minutes of following instructions now takes seconds. With ~20 DNS providers already supporting it (covering 35% of the .com zone) and 720 templates from 408 service providers deployed, Domain Connect has crossed from experiment to infrastructure. IETF standardization — through the newly approved DCONN working group — is now locking it in as an internet standard.
19+
## [Marketing & Communications Edition](/marketing-kb/)
5820

59-
---
60-
61-
## Core Statistics (as of May 2026)
21+
For marketing professionals, communications teams, conference speakers, and partner outreach. Covers the business case, key messages, soundbites, storytelling guides, and audience-specific narratives.
6222

63-
| Metric | Value |
64-
|--------|-------|
65-
| DNS Providers supporting Domain Connect | ~20 |
66-
| Share of .com zone covered | ~35% (May 2024) |
67-
| Service Provider templates | 720 |
68-
| Service Providers with templates | 408 |
69-
| GitHub contributors to template repository | 420 |
70-
| Merged pull requests (template repository) | 831 |
71-
| Microsoft 365 DNS setup failure rate (without DC) | ~50% |
72-
| MS 365 manual setup: DNS entries required | 7–15 |
73-
| MS 365 manual setup: help sites maintained | 16 (10 registrar-specific) |
74-
| MS 365 manual training time | 40 minutes |
75-
| Domain renewal rate, no content | ~70% |
76-
| Domain renewal rate, high content | ~90% |
77-
| Year first proposed | 2016 (GoDaddy) |
78-
| IETF WG approval | October 2025 |
79-
| Statistics source | stats.domainconnect.org (2026-05-14) |
23+
**Go here if you:** write LinkedIn posts or blog articles, prepare conference talks, brief analysts or press, or pitch Domain Connect to partners.
8024

8125
---
8226

83-
## Navigation by Content Goal
84-
85-
**"Explain what Domain Connect is"** → [02](./02_What_Is_Domain_Connect.md), [03](./03_How_It_Works.md)
86-
87-
**"Make the business case"** → [01](./01_Problem_and_Context.md), [06](./06_Value_by_Audience.md)
88-
89-
**"Go deep on the technology"** → [03](./03_How_It_Works.md), [04](./04_Protocol_Features.md), [08](./08_Security_Model.md)
90-
91-
**"Find use cases"** → [05](./05_Use_Cases.md)
92-
93-
**"Write a LinkedIn post or blog intro"** → [10](./10_Key_Messages.md)
94-
95-
**"Convince a registrar or DNS provider"** → [06](./06_Value_by_Audience.md), [07](./07_Adoption_and_Ecosystem.md)
96-
97-
**"Answer 'Is it a real standard?'"** → [07](./07_Adoption_and_Ecosystem.md), [09](./09_Getting_Involved.md)
98-
99-
**"Build or review a template"** → [11](./11_Template_Reference.md), [15](./15_Template_Use_Cases.md)
100-
101-
**"Implement as a DNS Provider"** → [12](./12_Getting_Started_DNS_Provider.md)
27+
## [Implementers Edition](/implementers-kb/)
10228

103-
**"Implement as a Service Provider"** → [13](./13_Getting_Started_Service_Provider.md), [15](./15_Template_Use_Cases.md)
29+
For DNS providers, service providers, and protocol contributors. Covers the technical protocol, template structure, security model, step-by-step implementation guides, and IETF participation.
10430

105-
**"Tell a story for a specific audience"** → [14](./14_Storytelling.md)
31+
**Go here if you:** are building Domain Connect support into a DNS platform or service, reviewing a template, or contributing to the IETF specification.

‎Knowledge Base/00_MASTER_implementers.md‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
# Domain Connect — Implementers Edition
2+
3+
**Version:** 1.0 | **Last updated:** May 2026
4+
**Author:** Pawel Kowalik, Co-Author of Domain Connect specification
5+
**Sources:** IETF draft-ietf-dconn-domainconnect-01 (Mar 2026), IETF 123 WG transcript, IETF-124 DCONN WG presentation, Templates repository README
6+
7+
---
8+
9+
## About This Edition
10+
11+
This edition is for DNS providers, service providers, template authors, and protocol contributors. It focuses on the technical protocol, implementation guidance, and template authoring.
12+
13+
| Who you are | What you'll find here |
14+
|-------------|----------------------|
15+
| **DNS provider or registrar** implementing Domain Connect | Discovery endpoint, template hosting, OAuth flow, sync and async APIs |
16+
| **Service provider** integrating Domain Connect | Template authoring, apply-template flow, signing, variable model |
17+
| **Template author** | Field-by-field template reference, use-case patterns, contribution process |
18+
| **Protocol contributor or IETF participant** | Full protocol specification context, security model, open issues, WG participation |
19+
20+
Looking for messaging, stories, or business-case materials? See the [Marketing & Communications Edition](/marketing-kb/).
21+
22+
---
23+
24+
## Quick Reference: What Is Domain Connect?
25+
26+
**Domain Connect** is an open-standard, application-level protocol that automates DNS configuration when a user connects a domain name to a third-party service. The service provider defines a signed DNS template; the DNS provider hosts it and applies it upon user consent. The protocol supports both synchronous (redirect-based) and asynchronous (OAuth-based) flows.
27+
28+
- **Originally proposed by:** GoDaddy, 2016
29+
- **Status:** Production-deployed; IETF standardization underway (DCONN working group, approved Oct 2025)
30+
- **Specification:** draft-ietf-dconn-domainconnect-01 (Standards Track)
31+
- **Template repository:** [github.com/Domain-Connect/Templates](https://github.com/Domain-Connect/Templates) — 720 templates, 408 service providers, 420 contributors
32+
33+
---
34+
35+
## Document Map
36+
37+
| # | Document | What it covers |
38+
|---|----------|----------------|
39+
| [02](./02_What_Is_Domain_Connect.md) | What Is Domain Connect | Definition, three-actor model, scope, what it is not |
40+
| [03](./03_How_It_Works.md) | How It Works | Synchronous and async flows, template structure, discovery, consent |
41+
| [04](./04_Protocol_Features.md) | Protocol Features Deep Dive | All protocol features with full technical detail |
42+
| [05](./05_Use_Cases.md) | Use Cases | Primary, extended, and out-of-scope use cases |
43+
| [06](./06_Value_by_Audience.md) | Value by Audience | Implementation benefits by stakeholder group |
44+
| [08](./08_Security_Model.md) | Security Model | Trust model, URL signing, OAuth scoping, known considerations |
45+
| [09](./09_Getting_Involved.md) | Getting Involved | IETF participation, GitHub contribution, community resources |
46+
| [11](./11_Template_Reference.md) | Template Reference | Complete field-by-field reference for all template metadata and record flags |
47+
| [12](./12_Getting_Started_DNS_Provider.md) | Getting Started: DNS Provider | Step-by-step implementation guide for DNS Providers |
48+
| [13](./13_Getting_Started_Service_Provider.md) | Getting Started: Service Provider | Step-by-step integration guide for Service Providers |
49+
| [15](./15_Template_Use_Cases.md) | Template Use Cases | 9 use-case patterns with examples, DNS setup guidance, and implementation notes |
50+
51+
---
52+
53+
## Use Case Detail Pages
54+
55+
| Use Case | Document |
56+
|----------|----------|
57+
| UC-01 Email Hosting | [Use Cases/UC-01_Email_Hosting.md](./Use Cases/UC-01_Email_Hosting.md) |
58+
| UC-02 Email Authentication & Marketing | [Use Cases/UC-02_Email_Authentication_Marketing.md](./Use Cases/UC-02_Email_Authentication_Marketing.md) |
59+
| UC-03 Email Security (DMARC) | [Use Cases/UC-03_Email_Security_DMARC.md](./Use Cases/UC-03_Email_Security_DMARC.md) |
60+
| UC-04 Website Hosting (Apex) | [Use Cases/UC-04_Website_Hosting_Apex.md](./Use Cases/UC-04_Website_Hosting_Apex.md) |
61+
| UC-05 Website Hosting (Subdomain) | [Use Cases/UC-05_Website_Hosting_Subdomain.md](./Use Cases/UC-05_Website_Hosting_Subdomain.md) |
62+
| UC-05-2 Website Subdomain + SSL | [Use Cases/UC-05-2_Website_Subdomain_SSL.md](./Use Cases/UC-05-2_Website_Subdomain_SSL.md) |
63+
| UC-06 CDN / WAF / Reverse Proxy | [Use Cases/UC-06_CDN_WAF_Reverse_Proxy.md](./Use Cases/UC-06_CDN_WAF_Reverse_Proxy.md) |
64+
| UC-07 URL Redirect | [Use Cases/UC-07_URL_Redirect.md](./Use Cases/UC-07_URL_Redirect.md) |
65+
| UC-08 Dynamic DNS | [Use Cases/UC-08_Dynamic_DNS.md](./Use Cases/UC-08_Dynamic_DNS.md) |
66+
| UC-09 DNS Subdomain Delegation | [Use Cases/UC-09_DNS_Subdomain_Delegation.md](./Use Cases/UC-09_DNS_Subdomain_Delegation.md) |
67+
68+
---
69+
70+
## Navigation by Task
71+
72+
**"Implement Domain Connect as a DNS Provider"** → [12 Getting Started: DNS Provider](./12_Getting_Started_DNS_Provider.md)
73+
74+
**"Integrate Domain Connect as a Service Provider"** → [13 Getting Started: Service Provider](./13_Getting_Started_Service_Provider.md)
75+
76+
**"Build or review a template"** → [11 Template Reference](./11_Template_Reference.md), [15 Template Use Cases](./15_Template_Use_Cases.md)
77+
78+
**"Understand the full protocol"** → [03 How It Works](./03_How_It_Works.md), [04 Protocol Features](./04_Protocol_Features.md)
79+
80+
**"Understand the security model"** → [08 Security Model](./08_Security_Model.md)
81+
82+
**"Find a use-case pattern for my template"** → [15 Template Use Cases](./15_Template_Use_Cases.md)
83+
84+
**"Contribute to the IETF spec"** → [09 Getting Involved](./09_Getting_Involved.md)
85+
86+
**"Understand what the protocol does and doesn't cover"** → [02 What Is Domain Connect](./02_What_Is_Domain_Connect.md), [05 Use Cases](./05_Use_Cases.md)

0 commit comments

Comments
 (0)