CLIENT DELIVERY

Event website builder — Multi-Template Event Website Builder

Before Squarespace wedding sites, All Star Occasions / myevent.com let couples and families spin up themed microsites in minutes. This circa-2008 stack — custom PHP + mysql_* + MySQL — ships an operator admin desk, per-vertical modules (wedding, reunion, baby), a member control panel and static HTML publishing into per-user folders.

Legacy PHPMulti-TenantStatic PublishFCKeditorMySQL
Industry
Events · weddings · reunions · baby announcements
Type
Multi-template website builder SaaS
Roles
Platform admin · member site owner
Stack
PHP 5.6 · mysql_* API · MySQL (myevent) · FCKeditor
Proof
5 screens · local working restore

The problem

Event hosts needed wedding, reunion and baby microsites without hiring a developer for each celebration — before modern hosted builders were commonplace.

Constraints

Delivery stayed inside the client's stack, tenancy, compliance and media-ownership boundaries. Where a choice was forced (suite vs owned plane, BYOC vs CPaaS, local vs cloud models), the architecture section below records the trade-off rather than a marketing rewrite.

Business requirements

Platform admin template desk, member control panel, FCKeditor pages, vertical modules and static HTML publish into per-user folders.

Architecture

Legacy PHP + MySQL: admin and member cpanel write to myevent; generator emits static sites for cheap hosting.

Engineering challenges

  • Restore fidelity — PHP 5.6 + mysql_* on modern XAMPP for demo.
  • Publish pipeline — member edits must regenerate static HTML reliably.

The solution

Restored All Star Occasions stack with admin templates, member signup and working publish path — screenshots on this page.

My role

Legacy restore and documentation — local runbook, demo capture and architecture write-up.

Technology stack

PHP 5.6MySQLFCKeditor

Production considerations

  • Legacy stack is for preservation demo — not a greenfield security baseline.
  • Static publish avoids server-side runtime for guest traffic.

Screenshots

Marketing home

Event website builder marketing homepage with wedding birthday baby and reunion website categories

Central landing routes visitors to vertical modules — wedding, birthday, baby and reunion — with member login and free-trial signup flows.

Platform admin desk

Event website builder web administrator dashboard with template wedding reunion and baby site management tiles

Operators manage template groups, HTML skins, wedding/reunion/baby accounts, passwords and cross-site user records from one grid.

Member control panel

Event website builder wedding member control panel with edit pages menu and account help tiles

After login, members land on a cpanel with shortcuts to edit Welcome, Our Story, Wedding Party, event details, contact and header sections.

Page editor

Event website builder welcome page editor with site title event date and image upload fields

Each page exposes title, rich text, hero image, site title and event date fields — saved to MySQL then re-rendered into static HTML under the member folder.

Published wedding site

Generated Event website builder wedding microsite with welcome navigation and couple hero content

The publish step writes index.html, story, party, events and contact pages into a username directory — ready for subdomain mapping (e.g. username.asoccasions.com).

Architecture diagram

flowchart LR
  ADM[Admin desk]
  MEM[Member cpanel]
  DB[(MySQL myevent)]
  GEN[Static HTML generator]
  SITE[Published microsite]
  ADM --> DB
  MEM --> DB
  MEM --> GEN --> SITE

Outcomes

Restored or delivered system documented with screenshots and local demo — portfolio write-up only.

FAQ — buyer & architecture questions

Ten common questions about this case study, fit, and engagement.

If you need tenant admin, billing hooks and a serious ops console—yes. Consumer apps differ.

Both. Phase 1 proves the workflow; later phases harden tenancy and integrations.

Yes. Rescue begins with audit and test coverage on critical paths.

AWS, GCP, Azure and on-prem/VPS depending on data residency.

We document shipped features and architecture; we do not invent revenue or uptime claims.

Use the project brief with roles, integrations and timeline.

Share the current stack (PBX, CRM, cloud), the failure or goal in one paragraph, peak call volume, carriers, and any deadline. Screenshots, a pcap, or a short Loom beat a 40-page RFP. Use the project brief or email hello@unifiedpbx.in.

Yes. Delivery is remote-first from Delhi with scheduled overlap for EU, UK, US and APAC stand-ups. Production changes use written runbooks, rollback steps and agreed maintenance windows.

Yes. Many engagements begin with a 1–2 week SIP trace review, tenant-isolation audit, or architecture assessment. If the fit is good, scope expands from evidence—not from a generic sales deck.

Founders, CTOs, telecom leads, MSPs and product teams building or fixing UCaaS, CCaaS, CRM+voice, AI voice, or vertical SaaS—not buyers who only need seats on a mass-market suite.