Skip to main content
Back to projects

Live • Continuously improved

Building thedsouza.com as a Consulting Portfolio

A personal website developed into a practical consulting platform that communicates experience, services and technical work through responsive design, structured case studies and a disciplined release process.

Project objective

The website needed to move beyond a basic personal portfolio and become a credible platform that:

  • Introduce Glen as a technical consultant
  • Connect 22+ years of professional IT experience with current project work
  • Clearly explain available services
  • Present technical work through evidence-based case studies
  • Give prospective clients a straightforward path to make contact
  • Remain maintainable as Glen’s skills and projects develop

Technical foundation

The implementation uses a focused set of technologies already present in the repository:

  • Next.js App Router
  • React
  • TypeScript
  • Tailwind CSS
  • GitHub
  • Vercel

The site is built from reusable, section-based React components, responsive layouts for desktop and mobile, data-driven project and service cards, static case-study routes, same-page homepage navigation, and production deployment through GitHub and Vercel.

Information architecture and content

The homepage follows a deliberate journey:

  1. Section 1

    Hero

  2. Section 2

    About

  3. Section 3

    Experience

  4. Section 4

    Services

  5. Section 5

    Proof

  6. Section 6

    Delivery

  7. Section 7

    Projects

  8. Section 8

    Skills

  9. Section 9

    Contact

This order helps visitors understand who Glen is, his professional background, the services he provides, evidence of completed and ongoing work, and how to start a conversation.

Search and sharing foundation

The site includes a deliberate search and sharing foundation without claiming guaranteed search outcomes:

  • Unique page titles and descriptions
  • Canonical URLs
  • Open Graph metadata
  • Twitter card metadata
  • Sitemap
  • robots.txt
  • Person JSON-LD
  • Existing favicon and application identity assets

Production security baseline

The public site now has a strengthened defensive baseline through the following controls. These reduce avoidable exposure without representing a guarantee of perfect security or formal certification.

  • Content Security Policy for allowed content sources
  • MIME-sniffing protection
  • Referrer and permissions policies
  • Frame protection
  • Cross-origin isolation and resource policies
  • HTTPS and HSTS supplied through production hosting

Accessibility and responsive design

The implementation is reviewed as an interactive public site with implemented accessibility practices for structure, keyboard access, motion preferences and small-screen behavior. It does not claim formal accessibility certification or full compliance.

  • Semantic headings and sections
  • Keyboard-accessible navigation and links
  • Skip-to-content navigation
  • Visible keyboard focus styles
  • A consistent main-content target
  • Reduced-motion support for shared entrance animations
  • Responsive desktop and mobile verification
  • Contrast-conscious dark interface
  • Checks for overflow, clipping and awkward wrapping

Trust and Proof layer

The homepage now presents evidence rather than promises: 22+ years of professional IT experience, five published technical case studies and delivery signals covering security, accessibility, human-led AI use and controlled releases.

Google PageSpeed Insights mobile lab results measured 9 September 2026 recorded Performance 98, Accessibility 96, Best Practices 100 and SEO 100. These are dated lab results, and scores can vary between test runs.

AI-assisted delivery workflow

Development uses an AI-assisted workflow, but each change is deliberately scoped, reviewed, tested and approved before publication. AI supports implementation and analysis; project direction, factual accuracy, acceptance decisions and publication control remain human-led.

The internal release discipline is now expressed publicly as a controlled delivery method: focused definition, evidence and privacy boundaries, small implementation increments, review, normal versioned publication and production verification.

The controlled workflow is:

  1. 1.Define the problem and intended outcome
  2. 2.Confirm evidence, ownership and privacy boundaries
  3. 3.Design and build the smallest useful solution
  4. 4.Validate quality, accessibility and privacy
  5. 5.Review claims and the complete change
  6. 6.Publish through controlled versioning
  7. 7.Verify routes, content and browser health
  8. 8.Record the result and next decision

Selected improvements delivered

  • Technical-consulting positioning
  • Services and engagement models
  • Professional experience section
  • GHDC case study and roadmap
  • Self-hosted mail-server case study
  • Epping Tennis Club case study
  • SEO and structured metadata foundation
  • Removal or correction of outdated portfolio records
  • Responsive and accessibility verification
  • Production security headers
  • Skip navigation
  • Reduced-motion support
  • Trust and Proof section
  • Public delivery-method section

Engineering lessons

  • Clear information architecture matters as much as visual design.
  • A portfolio becomes stronger when claims are supported by detailed case studies.
  • Small controlled releases are easier to review and recover than large uncontrolled changes.
  • AI-assisted development still requires human judgement, verification and accountability.
  • Privacy review is essential when presenting infrastructure and operational work publicly.
  • A personal website should evolve alongside real experience rather than presenting future plans as completed work.

Current status and next direction

The website is live and remains under controlled, incremental development. Future improvements will add stronger project evidence, refine contact conversion, expand selected case studies and continue improving performance and accessibility.