Private Pro template · implemented
Soft Signal Studio
A creative-agency site centered on selected work, process, people, and project fit. The public page exposes only reviewed source-free metadata; private React, TypeScript, tests, and release files never enter this application.
Product route contract
//work/work/[slug]/studio/contact
State and quality contract
States: loading, empty, error, success, permission-denied, offline.
Requirements: responsive, light, dark, rtl-reviewed, keyboard-reviewed, seo-ready.
Evaluate the product fit
Soft Signal Studio is for a creative practice whose strongest evidence is selected work, a clear process, the people doing it, and an honest description of project fit. It is designed to let case studies carry the argument instead of relying on decorative awards, fabricated client marks, or vague scale claims.
Confirm every project has publication permission, licensed imagery, accurate roles, and enough context to distinguish contribution from outcome. The dynamic work route needs stable slugs and a withdrawn-project state. The contact route should qualify inquiries without collecting unnecessary budgets, confidential briefs, or personal information.
Test image failure, portrait and landscape media, long captions, missing credits, slow galleries, reduced motion, keyboard browsing, and readable case studies at high zoom. Replace all demonstration organisations and testimonials. The consuming studio owns consent records, asset retention, lead routing, and correction or removal requests.
The production plan should assign owners for portfolio corrections, asset rights, inquiry delivery, and removal requests. Monitor broken case-study media and contact failures without collecting full confidential briefs in ordinary logs. Backup and restore must preserve approved project records and credits as well as page code, while rollback must not republish work whose permission has been withdrawn.
Source-free preview
No public preview is published. Preview metadata remains private until release readiness and boundary review are complete.
Availability boundary
Implemented does not mean verified, release-ready, entitled, sold, or deployed. Manual browser and assistive-technology review, approved commercial terms, a protected archive, and server-side entitlement delivery remain required.