docs(marketing): advance domain validation, Q2 drafts, and IA ADR#110
docs(marketing): advance domain validation, Q2 drafts, and IA ADR#110jarvislanou wants to merge 14 commits into
Conversation
… website ADR draft
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8ec0bfe7bc
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| ## Decision | ||
| 1. Keep `hypemd.dev` as canonical domain. | ||
| 2. No immediate defensive registrations. |
There was a problem hiding this comment.
This line declares “No immediate defensive registrations,” but the newly added canonical marketing doc at docs/marketing/domain-shortlist-validation.md now recommends actively acquiring hypecli.dev (and fallback domains). Keeping both contradictory “current decisions” in the same commit creates operational ambiguity for issue #83 updates and can lead to opposite execution (purchase vs defer), so one source of truth should be reconciled or clearly deprecated.
Useful? React with 👍 / 👎.
|
|
||
| ## Decision | ||
|
|
||
| Adopt **Option A**: Hype-generated unified static site deployed to DigitalOcean Static Sites. |
There was a problem hiding this comment.
This ADR decision chooses DigitalOcean Static Sites, but the new docs/adr/0001-website-architecture.md in the same commit records Dokploy as the selected deployment architecture. Two conflicting ADR 0001 decisions will mislead follow-up tasks and infrastructure changes, because teams reading different paths will implement different platforms; the duplicate ADRs should be consolidated or one marked obsolete.
Useful? React with 👍 / 👎.
|
Closing this to simplify workflow. Per Cory's direction, switching to issue-only execution with two concrete blog publish tickets. |
1 participant
Summary
This PR is now intentionally blog-only.
I removed the strategy/enterprise planning noise and kept scope focused on shipping practical Hype content.
What remains in scope
marketing/posts/What was removed from this PR
Current intent
Use this PR as a simple content lane: draft + refine publishable Hype usage posts.