WebTayo

Websites. Systems. Automation.

Internal project / implementation case study

A business website.
A working delivery process.

WebTayo’s own platform combines service pages, a guided project brief, a PHP inquiry endpoint, and automated deployment to shared hosting.

AstroTypeScriptTailwind CSSPHPGitHub Actions
Screenshot of the actual earlier WebTayo homepage and interactive project starter
Actual screenshot of the previous homepage release. The current revision puts services and implementation evidence before Project Starter.

The site needed to describe the business, collect relevant inquiries, and deploy updates without manually copying files into cPanel. Production hosting needed to serve the website without a Node.js application server.

Project type: WebTayo-owned platform. The work documented here covers the website interface, static pages, inquiry flow, PHP endpoint, and deployment configuration.

What was implemented

The pieces behind the pages.

WEBSITE

Static pages with purposeful interaction.

Astro generates the public pages. TypeScript handles navigation, the project starter, and inquiry form states. Layouts combine Tailwind utilities with a shared CSS design system.

Website development
INQUIRY FLOW

A brief that carries through.

A visitor selects a challenge, sees a recommendation, and opens the contact page with a service and editable message prefilled. Keyboard users can move through the choices using arrow keys.

Try Project Starter
FORM HANDLING

Server-side checks and visible states.

The PHP endpoint validates names, email addresses, service choices, and message length. It includes a honeypot and submission cooldown. The interface displays sending, success, and failure states.

Email delivery is environment-dependent and has not been verified end to end in this case study.

SEARCH FOUNDATIONS

Crawlable pages and metadata.

Service pages have their own URLs, titles, descriptions, and canonical links. The build produces XML sitemaps, and page templates include relevant structured data and internal navigation.

Technical SEO & maintenance
  1. Change reviewed in GitHub

    Source changes are kept in the repository and merged into the main branch.

  2. Build runs in GitHub Actions

    The workflow generates the static production output and includes the PHP endpoint.

  3. Output transfers over FTPS

    The built files are uploaded to the configured shared hosting directory.

  4. Live behavior is checked

    The release is checked for page rendering and the project-starter-to-contact journey.

Verified scope

Implementation evidence, with clear limits.

The previous release passed Astro checks and production build, completed its GitHub deployment, and was checked in a browser for project selection and contact-form prefilling. Conversion uplift, client revenue, and search ranking gains have not been measured.

Discuss a similar build