尚未检测到更新。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.