尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
依最近已完成的 8 小時觀測回合間的 GitHub 星號增量排序
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權，自行管理介紹，無需管理員核准。
登入並產生驗證檔案，在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案，即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入，將前往登入頁面。登入後請回到此處，再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify，即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
LawIntake is a client-intake and matter-management workspace for real estate law firms. It
combines guided intake, matter details, documents, AML workflows, and a client portal in one
Next.js application.
Install dependencies and start the development server:
Open http://localhost:3000.
Environment setup and database instructions are available in
docs/dev-setup.md.檢視完整 README ↗LawIntake is a client-intake and matter-management workspace for real estate law firms. It combines guided intake, matter details, documents, AML workflows, and a client portal in one Next.js application.
Project site · Live application · Interactive demo
The interactive demo is the unauthenticated browser sandbox at /demo (no login, fictional
data in the browser). See docs/public-demo-sandbox.md. A legacy
Supabase is_demo_firm tenant is quarantined and is not the public prospect path.
Install dependencies and start the development server:
npm install
npm run dev
Open http://localhost:3000.
Useful checks:
npm run type-check
npm test
npm run check:compliance
Environment setup and database instructions are available in
docs/dev-setup.md.
The marketing landing files at the repository root (index.html, styles.css, script.js) remain
available for the existing Pages site, including the static Insights pages under insights/.
The Next.js app can also be built as a static export for
project Pages under the repository base path /intake-app.
/intake-app)GitHub Pages has no Node server, so export mode is opt-in and must not be used for Vercel:
npm run build:github-pages
This sets GITHUB_PAGES=true, which configures next.config.js with:
| Setting | Value | Why |
|---|---|---|
output | 'export' | Emit static HTML/CSS/JS into ./out |
basePath / assetPrefix | /intake-app | Match https://tommyjackson85.github.io/intake-app/ |
trailingSlash | true | Emit …/demo/index.html so Pages serves folder URLs |
images.unoptimized | true | Image Optimization API is unavailable on static hosts |
Vercel / npm run build leave GITHUB_PAGES unset, so those deployments keep root paths, server
headers, and the normal Next server output.
Publish the generated ./out directory as the GitHub Pages artifact (or copy it into your Pages
publishing folder). Client navigation via next/link and bundled assets include the /intake-app
prefix automatically when built this way.
Not included in the static export (stashed only for that build, then restored):
app/api/** route handlers and app/auth/logoutapp/auth/post-login (force-dynamic) and app/auth/signup (Server Action)app/dashboard/** (server/cookie-backed product UI)generateStaticParams: /demo/portal/[token],
/demo/intake/[token], /demo/fincen-cert/[token], /intake/[token]proxy.ts (request-time middleware replacement; unsupported for export)/demo/matters/[id] is included in the static export: generateStaticParams emits one page
per seeded demo matter file_id.
Those capabilities remain on Vercel. Hardcoded absolute <a href="/…"> strings (not next/link)
are not rewritten by basePath; prefer next/link for in-app navigation.