尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Fifty Pages of Shades — fine art photography website
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Collector-acquisition site for Fifty Pages of Shades by Nick Brand. Black-and-white bodyscape & abstract photographic art, limited editions on framed canvas. Built with Next.js 15 (App Router), TypeScript, Tailwind. Runs natively on Vercel with automatic image optimisation.
npm install
npm run dev # http://localhost:3000
npm run build # production build
npm start # serve the production build
site/ folder to a Git repo (GitHub/GitLab/Bitbucket).fiftypagesofshades.com in Vercel → Project → Domains.Or from the CLI: npm i -g vercel then vercel (preview) / vercel --prod (production), run inside site/.
Image optimisation (AVIF/WebP, responsive srcset) is handled automatically by Vercel — no extra setup.
sitemap.xml, robots.txt, Organization / WebSite / Person / VisualArtwork / CollectionPage schema../artworks/ (the Body Scapes/artworks folder in the project) — artworks.csv, pricing.csv, images/.data/catalog.json — the generated catalogue the site reads.node scripts/build-data.mjs # rebuilds data/catalog.json from the CSVs (set ART_DIR if needed)
python3 scripts/build_images.py # rebuilds web images from masters (pip install pillow)
(Step 2 is only needed when you add or replace artwork files.)
pricing.csv (non-$2,700 cells are indicative placeholders).app/api/enquiry/route.ts (emails the studio via Resend). To turn
it on, set RESEND_API_KEY, ENQUIRY_TO and ENQUIRY_FROM in Vercel → Project → Settings → Environment
Variables (see .env.example, and verify your sending domain at resend.com). Until those are set, the form
automatically falls back to opening the visitor's email client — so it works either way.../02_Content_Engine_200_Ideas.md (edit lib/journal.ts).Brand voice, SEO, schema strategy and the full build spec are in ../01–../06 markdown docs.