Repository navigation
chore(site): remove the marketing site, keep a self-host page - #108
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Marketing sites do not belong in the open-source repo. The marketing site at www.meetingmouse.net now lives in the hosted service's private repo and deploys from the Vercel project
meetmouse-cloud, which already serves www and the apex domains. The blog tooling and the privacy-schema test moved there first (masaok/meetingmouse-cloud#112). What stays here is the app a self-hoster runs.Scope
src/app/blog (index, posts, feed, OG images), privacy, support, installation, legal, terms, the fourdata-*pages, vulnerability-disclosure,opengraph-image.tsx,sitemap.ts.src/components/(all of it),src/blog/,src/lib/{site,hosted,policies,installation}.tsand their tests,src/assets/fonts/(only the social image used them), the.post-bodyCSS.content/blog/,docs/BLOG.md,docs/BLOG_KEYWORDS.md,scripts/check-blog.ts,pnpm blog:check(fromverifyand CI), theadd-blog-postskill, themarkedandyamldependencies.public/(install screenshots, logo mark, Slack listing images and icon); the hosted repo serves them./is now a short self-host page: what the app is, that this copy is running and where Slack posts, a link to the README, a link to https://www.meetingmouse.net.robots.tskeeps/api/and/grid/disallowed, with no sitemap. Layout metadata no longer describes the marketing site.src/components/**glob./and the grid), TESTING, docs/README.Blast radius
The Slack route, Bolt, features, domain, db, migrations, the web grid and the library entry points are untouched. Nothing in the app linked to a removed page: the reference app sets no
supportUrl, and a grep for/privacy,/support,/installation,/terms,/legal,/blogandmeetingmouse.netinsrc/andscripts/outside the removed tree finds only test fixtures on example.com.manifest.jsonkeeps its placeholder URLs; DEPLOYMENT now calls them that. This project serves no custom domain, so no live page changes.Verification
Offline mode.
pnpm verifypasses: 30 test files, 231 tests; docs 14 files, prose 25 files, 0 problems; feature map; smoke imports;next buildroutes/,/_not-found,/api/slack/events,/grid/[token],/icon.svg,/robots.txt; pack check 25 files, 0 problems; smoke:pack 401.Against
next dev -p 3111with fake env andSLACK_TOKEN_VERIFICATION=off:pnpm healthpasses env, homepage 200, unsigned POST 401.pnpm slack:sign --command /meetreturns 200 and the log shows the poll-create listener running (it then fails on the fake database, as offline mode expects)./privacy,/support,/blog,/installationreturn 404.