Muebles San Francisco JYN: corporate site and catalog
This project is focused on strengthening the company's digital presence with a bilingual site that is clear, fast, and easy to maintain. The main goal is to present the brand story, showcase completed work over the years, and organize the catalog in a way that supports trust and discovery.
Challenge
Build a bilingual website that could communicate company history, trust, and experience while also presenting completed work and catalog content without depending on a complex admin layer.
Solution
Built the site with Next.js App Router, next-intl localization, and structured JSON content. The architecture prioritizes editorial clarity, strong performance, and low-friction maintenance for catalog, company-history, and corporate sections.
Results
- Consistent bilingual corporate presence for end customers
- Catalog and completed work presented in a clear and structured way
- Company story and brand credibility communicated more effectively on the web
- Lightweight, maintainable technical base for evolving content without unnecessary complexity
Technical details
Stack and technologies
- - Next.js 15 + React 19 + TypeScript
- - Tailwind CSS v4 with semantic design tokens
- - next-intl for es/en localization
- - JSON files for catalog and corporate content
- - Formspree for contact form
How it is organized
- - app/: thin routes, layouts, and page composition
- - src/content and JSON files: structured catalog and corporate content
- - shared/: reusable UI and common utilities
- - i18n/: routing, messages, and localized navigation
- - Pages consume static content and map it into clear sections
Key modules
- - Corporate home: value proposition, company history, and brand presentation
- - Catalog: categories and items rendered from structured content
- - Completed work: visual showcase to reinforce credibility and experience
- - i18n: es/en locales with localized links and messages
- - SEO: centralized metadata, canonical, alternates, sitemap, and robots
Risks / technical debt
- - Manual content maintenance requires editorial discipline
- - The catalog depends on a consistent JSON structure to avoid content errors
- - A larger catalog may eventually require a more robust editorial layer
- - Bilingual operation requires care to keep both locales aligned
Need to build or improve a system?
I help turn the need into a clear technical direction and a clean execution plan.