Built with
Company site for BuildSpark, deployed to AWS on a stack configured by hand rather than assembled from a hosting panel.
WordPress carries the content: company information, service offerings, and inquiry forms, with plugin work to extend functionality where the base install fell short. The content management choice was correct for a client whose team needed to publish without a developer in the loop.
The deployment is where the actual engineering sits. Rather than reaching for a bundled local environment like XAMPP, the development setup was configured directly with Apache, PHP, and MySQL, then migrated to production on AWS running Nginx on Ubuntu with PHP-FPM and MySQL. Swapping Apache for Nginx between environments is not ideal and was a deliberate trade, taking a small divergence in exchange for the production characteristics Nginx offers under concurrent load.
Doing it this way rather than clicking through a managed host is slower and teaches you where the real failure points are: file permissions, PHP-FPM socket configuration, Nginx rewrite rules that WordPress depends on, and the TLS termination that has to be right before anything is public.
SEO work followed launch so the site reaches an audience rather than sitting there correctly configured and unfound. Ongoing maintenance keeps WordPress and its plugins patched, which on this stack is the single highest-value recurring task, since an unpatched plugin is the most common way a WordPress site is compromised.
More work