尚未检测到更新。GitHub 发布版本后会显示在这里。
按最近已完成的 8 小时观测回合间的 GitHub 星标增量排序
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权，自行管理介绍，无需管理员批准。
登录并生成验证文件，在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件，即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录，将前往登录页面。登录后请回到此处，再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify，即可验证所有权并自行管理介绍。
一分钟完成验证Marketing landing page for Critter - CRM & Marketing Automation for Pet Care Businesses
翻译准备中
取自仓库 README
正在加载完整 README。
查看完整 README ↗Marketing landing page for Critter - CRM & Marketing Automation for Pet Care Businesses.
This is a standalone Next.js application that serves as the marketing landing page at critter.pet. Log In and sign-up go to Critter Hub CRM (hub.critter.pet). The legacy Critter Ops scheduling product is retired from this site; /features/scheduling redirects to /features/data-integration.
# Install dependencies
npm install
# Create environment file
cp .env.example .env.local
# Run development server
npm run dev
Visit http://localhost:3000 to see the landing page.
NEXT_PUBLIC_HUB_URL=https://hub.critter.pet
| Route | Description |
|---|---|
/ | Main landing page |
/pricing | Pricing page with plan comparison |
/togo-ai | Togo AI assistant feature page |
/ttp | Time To Pet introduction and context-preserving CRM signup |
/faqs | Product, onboarding, and billing FAQs |
/features/* | CRM and product feature pages |
This repo is configured to deploy to Vercel. The vercel.json includes redirects for legacy routes:
{
"redirects": [
{ "source": "/dashboard/:path*", "destination": "https://hub.critter.pet/dashboard/:path*", "permanent": true },
{ "source": "/auth/:path*", "destination": "https://hub.critter.pet/auth/:path*", "permanent": true },
{ "source": "/api/:path*", "destination": "https://hub.critter.pet/api/:path*", "permanent": true }
]
}
"Log In" links straight to Hub sign-in. Trial buttons start a new Hub CRM account. On /ttp, signup and sign-in retain the fixed Time To Pet onboarding destination. Other routes keep generic CRM signup behavior. The approved public offer facts live in lib/marketing-offers.ts; visible FAQs and FAQ structured data share lib/marketing-faqs.ts.
npm test runs actual React-render contract checks without external services. npm run build validates the production bundle. With the built site running locally, npm run test:browser runs desktop/mobile checks using an existing Playwright installation; set CRITTER_TEST_TOOLS to its node_modules directory if it is not available locally. It blocks external requests and substitutes a synthetic Hub navigation boundary.
See BL-403 public offer and TTP evidence for the BL-392 handoff, exact boundaries, and local proof.