Excalibur Security
Modernizing the frontend without rebuilding everything behind it.
Independent modernization concept. Not commissioned by, affiliated with, or endorsed by Excalibur Security, Inc.
An independent modernization concept for a Los Angeles security services company, exploring an Astro-based frontend while preserving the existing WordPress CMS and content workflow.
Current business website ↗
Reference only — this is not the concept demo.
Role · Independent Product Designer & Full-Stack Developer
Explore a practical way to modernize the presentation layer without requiring an immediate full-platform rewrite. Priorities included clearer information hierarchy, responsive layouts, maintainable frontend code and continuity for content editors.
Separate content management from frontend delivery. Build the Astro and TypeScript interface independently, then progressively connect and migrate pages using the WordPress REST API. Retain working content infrastructure and replace the legacy theme in stages.
Replace the layer that needs to change.
The concept began with a public review of the company’s website and software-development hiring needs. The review identified a modernization opportunity in the legacy theme and frontend components, rather than a need to discard the existing WordPress content infrastructure.
The intended audience includes businesses seeking security services, prospective clients, applicants, security personnel and staff looking for company resources.
Designed & built
- Responsive homepage and updated navigation
- Service presentation and clearer calls to action
- Visual direction, typography and spacing
- Astro frontend and TypeScript implementation
- Cloudflare deployment and technical documentation
Reviewed & proposed
- Public review of the WordPress presentation layer
- Content preservation and editorial continuity
- Headless WordPress / REST API integration
- Progressive page migration and legacy theme retirement
- React components where interactivity is needed
The work was independent. No intrusive security testing or unauthorized vulnerability exploitation was performed.
A clearer path from services to conversation.
Service categories, supporting content and consultation steps create a more deliberate information hierarchy. The supplied screenshots show the functional prototype, not the official company website.
The same priorities. A smaller screen.
The mobile layout keeps the primary action visible and gives navigation a dedicated expanded state.
Keep the content. Rethink its delivery.
These simplified diagrams distinguish the reviewed theme-driven architecture from the proposed migration target. The prototype demonstrates frontend delivery; it does not claim a completed migration of the company’s CMS.
Reviewed architecture
- Browser
- Web server · nginx / Apache
- PHP / WordPress
- Legacy theme · PHP rendering, jQuery, JavaScript and plugins
Proposed architecture
- Visitor
- CDN / edge delivery
- Astro + TypeScript · responsive UI and interactive components
- WordPress REST API
- Existing WordPress CMS
A progressive path, not a platform reset.
- Build the new frontend independently.
- Connect it to existing WordPress content.
- Migrate public pages progressively.
- Retire the legacy presentation theme.
- Modernize additional services where there is a clear business reason.
Which layer actually needs to be replaced?
For this proposal, the primary target is the presentation layer. Separating it from the CMS creates a path to preserve editorial workflows while changing the visitor experience.
A working prototype and a migration plan.
A functional Astro prototype, a responsive visual direction and a documented migration strategy. The headless WordPress integration remains proposed. This is not the company’s production website, and no conversion, revenue, SEO or production-performance gains are claimed.