01
Fast Website
Fast real estate pages with lazy maps, responsive images, and clear loading paths.
Project example
BayHaus Immobilien as a production web and operations platform.
Premium website, admin/CRM, ImmoScout import, SEO/LLM layer, CI system, and modernized infrastructure come together in one production setup.
Evidence
- Live website running on bayhaus.de
- Admin layer for content, properties, media, and operational maintenance
- ImmoScout data can move into a controlled draft workflow
- Architecture focused on performance, SEO, social preview, and LLM readability
- Brand assets and social previews are documented and reproducible
- Hosting, functions, and deployments are connected through CI/CD and Firebase
02
SEO & Social
Dynamic sitemap, Open Graph tags, structured data, and agent-readable discovery files are part of the architecture.
03
ImmoScout Import
Expose data is captured, normalized, and moved into the internal property draft flow.
04
Admin as Lean CRM
Media, content, image audit, and import workflows run through one central portal.
05
Infrastructure Migration
Hosting, email, domain/DNS and Firebase were pulled into one coherent setup.
06
Branding
Logo, color system, and typography support the premium character of the brand.
Starting point
- The site had to feel premium while still making properties, references, and contact paths easy to find.
- Content, images, and recurring maintenance should not depend on manual technical work forever.
- Hosting, domain/DNS, email, and Firebase had to behave like one reliable operating setup.
Approach
- The project was shaped as a lean marketing and operations layer: fast public pages in front, practical admin flow behind them.
- SEO, social sharing, structured data, and agent-readable discovery files were treated as core functionality rather than polish.
- The infrastructure was organized so website, content, media, and contact paths can be operated coherently.
Outcome
- BayHaus has a real live web presence rather than a portfolio mockup.
- The use case connects website, content operations, SEO, import paths, and infrastructure into one system.
- The case reads as a reference for small business web systems, not only interface design.
Role
Frontend EngineeringCloud/Firebase ArchitectureAdmin/Operations WorkflowsSEO/AEO ImplementationInfrastructure MigrationCI/Brand Development
Impact
- Production website instead of a demo artifact
- Less manual maintenance through admin and import workflows
- Better technical visibility for search engines, social bots, and LLMs
- Faster and more stable property detail pages through performance architecture
- Modernized infrastructure with more controllable running costs
Business context
- Premium real estate needs trust, discretion, and a calm high-end perception.
- The team needs a simple maintenance interface instead of scattered manual processes.
- Visibility has to work for Google, social bots, and LLM/agent systems.
- Hosting, email, DNS, and deployments should be easier and less expensive to operate.
Architecture
Public Website
Vite/React frontend for properties, references, contact, social previews, JSON-LD, and fast delivery.
Content & Media
Firestore and Storage as the working base for properties, images, responsive WebP variants, content, and maintenance.
Admin Layer
A lean portal for media, content, image audits, import workflows, and redirect/SEO inventory.
Agent Discovery
llms.txt, dynamic property feeds, XML/Markdown sitemaps, and security.txt make the site readable for agents too.
Operations
Hosting, domain/DNS, email, and Firebase setup as part of the project so the site stays usable day to day.
Project path
Brand and first structure
Logo, color direction, information architecture, and the main website paths were established first.
Website and content
Property, reference, and contact areas were shaped around fast orientation, responsive images, and visible trust signals.
Admin and operations
Media, content maintenance, image variants, import logic, and infrastructure were brought together so the site does more than look good.
Stack
ViteReactTypeScriptTailwindCSSshadcn/uiFirebase HostingCloud FunctionsFirestoreFirebase StorageGitHub ActionsZoho MailHetzner DNSGemini / Genkit
Why it matters
- Premium real estate hero section
- 4 to 6 short project cards
- Stack chips directly under the summary block
- Small infrastructure path for migration and operations
- CRM/admin portal as its own evidence block
- Mini timeline for brand, platform, and go-live
Tags
Real EstateSEOCRMInfraPerformancePremium UIAdmin PortalImmoScoutBranding
Context
Founder Ops, AI Automation & Web Dev
This example shows how I shape projects across product, operations, and structure: clear information, clean architecture, and a practical path for day-to-day use.