How this place works & Architecture
Here is how apps are named, built, and shipped — with complete transparency on both the code pipeline and the lab mindset.
The Subdomain Strategy & Permanent IDs
Why use app0, app1, app2 instead of long project names?
Each application gets its own dedicated subdomain and a permanent, short technical identifier:
- DNS & Hostname Friendly: Short alphanumeric labels like
app1.stephanelauper.chavoid awkward characters, hyphens, or localized spelling pitfalls. - Decoupled from Branding: Product names change as projects mature (e.g. from a concept code name to a polished title). The technical ID remains completely stable.
- Unified Configuration: The exact same ID is reused across Apache/Nginx virtual hosts, SSL certificates, Git repositories, deployment scripts, and analytics.
- Isolated Scope: Each application runs in its own sandbox without shared session conflicts, cross-app CSS collisions, or bloated monorepo builds.
*.stephanelauper.ch → Web Hosting Environment
├── stephanelauper.ch # Main Hub & App Inventory
├── app0.stephanelauper.ch # Business Analyst Toolbox (Work in Progress)
├── app1.stephanelauper.ch # Live Application
└── appN.stephanelauper.ch # Future Applications
The Honest Lab Mindset
No corporate spin — just how I like to create and experiment here.
This isn’t a “zero-problem” corporate website. It’s a playground: somewhere to enjoy the web, try things out, and share what I learn. Please don’t expect everything to be flawless all the time — that’s not the deal.
I will break stuff sometimes. I’ll try again, patch what I can, and move on when it makes sense. I work on this in the time I have, with the energy I have. If something breaks, it breaks; if it can be fixed, I’ll fix it when I can. I’m not hiding that — it’s part of going with the flow and having real fun with it.
I use AI and modern tools the same way I use curiosity: to experiment, to speed up boring bits, and to turn half-formed ideas into something you can actually click on. It’s a collaboration between me and those tools — judgment and taste on my side, automation and speed on theirs. We’ll see where it goes.
Thanks for getting it. Let’s see what we build.
Core Principles
Simple, pragmatic, and designed for longevity.
Reliable Infrastructure
Hosted in Switzerland on stable, independent infrastructure with high availability, clean privacy standards, and low latency.
Lightweight & Fast
Built using direct web standards to ensure fast loading times, responsive interactions, and minimal maintenance overhead.
Mobile First
Designed to adapt cleanly to any screen size, with touch-friendly navigation, comfortable reading, and clear layouts.
Direct Delivery
Tracked under version control with transparent updates. Tools are published directly so new iterations can be tried immediately.
The Idea-to-App Pipeline
From raw spark to a live, tactile tool.
1. Concept & Needs
Identify real friction points in daily life, education, or business. Clarify the core value before writing code.
2. Rapid Prototype
Pair with AI assistants to scaffold interactive mechanics, test UX flows, and build quick playable iterations.
3. Ship & Iterate
Deploy to a designated appX subdomain, test on physical devices, and gather real community feedback.
Ready to explore the tools?
Check out the live apps or connect to suggest ideas and collaborate.