SiteLauncher

A MetroVPS product. SiteLauncher is the site you land on at site-builder.service.adibthenoob.com: an AI-powered site builder that turns one source of truth — a resume (PDF/DOCX), a photo of a business card, or a LinkedIn/GitHub URL — into a whole, polished personal site. The AI reads the document, pulls out roles, skills, education and projects, and writes site copy in a voice you shape. You preview, edit anything, then publish with one click.

It is, in short, the antidote to blank-page paralysis for people who have the content but not the inclination to build it.

How it works

1. Upload your source. A resume, a CV, or a photo of a business card. PDF, DOCX, PNG or JPG — anything with the data we need.
2. AI extracts the data. A model reads the document, pulls out your info, and writes polished site copy. You stay in control: every field is editable before it is ever published.
3. Publish in seconds. One click goes live on a clean subdomain or your own domain. A sitemap, og:image, Twitter cards and the JSON-LD Google needs to surface you are generated with the page — no plugins, no config.

What I built

I architected and built SiteLauncher end to end at MetroVPS. Coming from a backend/Django background, the frontend was the steep part: “what is useEffect”, “is this even a component” were real search-bar queries for two months. In today’s stack, code is cheap — the work that carried this was choosing which library does what, and guarding the UI against AI slop with a strict, opinionated component kit.

Infrastructure

• Extraction runs in a managed pipeline; structured results land in PostgreSQL so every field is queryable and versionable.
• SSR for the marketing surface, ISR for templates, and CSR only for the editor, so pages are fast and the cockpit stays immediate.
• SEO by default: every public site ships canonical URLs, per-page meta and structured data (Person / Organization); SSL and CDN are provisioned and renewed automatically.
• Private and portable: export the full site as a zip bundle at any time, and bring your own domain — your data isn’t locked in.

What I learned

Shipping a React product without a frontend background taught me that most UI work is not pixels — it’s picking a primitive and sticking to it. Using Shadcn/ui as a constrained kit kept the markup consistent instead of letting an LLM spray a thousand slightly-different buttons across the page. SSR / ISR / CSR each have a real, different job: ISR for static content, SSR for user-specific data, CSR only where the interface needs to feel instant.

What’s next

• More templates (portfolio, doctor, lawyer, creative) and tone controls so the AI can match an existing brand voice.
• Progress indicators and resumable edits for long extraction jobs.
• A public template gallery so builders can see — and fork — real examples.