Cowcy Start your project brief

Selected work and concept projects

I share project work with clear context. Verified internal work and self-initiated examples are labelled so their roles, evidence, and limitations stay visible.

Every project is labelled clearly as verified work, a concept project, or work being prepared for publication.

Start your project briefExplore services

How projects are labelled

The label describes what can be verified, not the visual quality or complexity of the work.

  • Verified work

    Verified work

    Client or collaboration work appears only when its project details and publication permission are confirmed.

  • Concept project

    Concept project

    Self-initiated work is labelled clearly and explains the intended problem, scope, and limitations.

  • In preparation

    In preparation

    Unpublished work stays off the project grid until it can be presented with accurate context.

Current project collection

Verified internal work and clearly labelled concept studies appear below with their roles, scope, evidence, and limitations.

Verified work

Only projects with confirmed details and publication permission are included.

  • Verified work Service-provider website

    Cowcy service website

    A fully static Angular website that explains Cowcy's frontend services, project boundaries, working process, and contact paths.

    Cowcy website shown in responsive Light and Dark interface layouts
    Role
    Internal product direction, content architecture, Angular frontend implementation, accessibility hardening, and IIS deployment preparation.
    Client or collaboration
    Internal Cowcy project
    Date
    2026
    Publication permission
    Confirmed
    Scope
    • Plan and implement the approved public route structure
    • Build reusable Angular components and typed local content
    • Add static prerendering, route metadata, and IIS deployment packaging
    • Harden keyboard, responsive, reduced-motion, and forced-colors behavior
    • Create static-output, release, and live-deployment verification tooling
    Evidence
    • Publication approved by the project owner
    • Automated test, static-build, release-audit, and browser-validation records
    Supported outcomes
    • Fully static Angular deployment artifact with direct-route validationEvidence: Static-output and release audits
    • Cross-route keyboard, responsive, reduced-motion, and forced-colors behavior validatedEvidence: Automated and browser accessibility validation

Concept projects

Self-initiated projects are labelled clearly and explain their intended scope and limitations.

  • Concept project Business website concept

    Local services website concept

    A self-initiated concept study for clearer service discovery, trust cues, and a mobile-first enquiry path.

    Concept interface for a responsive local services website
    Role
    Concept planning, information architecture, and frontend interaction design.
    Concept label
    Self-initiated concept study
    Scope
    • Goal-based homepage and service structure
    • Local trust and location-content hierarchy
    • Mobile-first contact and enquiry flow
    • Accessible FAQ and proof sections
    Intent

    Demonstrate how a local service website can guide visitors from service discovery to a clear contact decision without overloading the first page.

    Limitations
    • No real client or business identity is represented
    • No booking backend, CRM, analytics, or live local-search result is included
    • No traffic, lead, ranking, or commercial outcome is claimed
  • Concept project E-commerce storefront concept

    Independent storefront concept

    A self-initiated storefront study covering product discovery, product details, cart states, and checkout handoff.

    Concept e-commerce storefront with product, cart, and checkout interface states
    Role
    Frontend flow planning, responsive state design, and storefront information architecture.
    Concept label
    Self-initiated concept study
    Scope
    • Product discovery and collection structure
    • Product-detail and cart interface states
    • Checkout handoff to an established commerce platform
    • Loading, empty, unavailable, and error states
    Intent

    Show how an e-commerce frontend can make product choices and checkout handoff clearer while keeping platform responsibilities explicit.

    Limitations
    • No real merchant, products, orders, or customer data is represented
    • No payment, tax, inventory, shipping, or fulfilment infrastructure is built
    • No conversion, revenue, or sales outcome is claimed
  • Concept project Web app interface concept

    Operations dashboard interface concept

    A self-initiated workflow study for task states, filtering, tables, forms, and review actions.

    Concept operations dashboard with tables, filters, and review workflows
    Role
    Frontend workflow architecture, component planning, and accessible interaction design.
    Concept label
    Self-initiated concept study
    Scope
    • Dashboard information hierarchy
    • Table, filter, and status-state patterns
    • Form and review workflows
    • Responsive and keyboard-accessible interaction planning
    Intent

    Demonstrate how a complex internal workflow can be made easier to scan, review, and act on through a structured frontend.

    Limitations
    • No real organisation, employee, customer, or operational data is represented
    • No authentication, database, API, real-time service, or permission backend is included
    • No productivity, efficiency, or business outcome is claimed

What each published case study will explain

Proof is useful only when the context is clear. Published work will separate the problem, my role, the delivery scope, and the evidence behind any result.

  • Problem and objective

    What needed to change and what the project set out to achieve.

  • My role and scope

    What I designed or implemented, which integrations were involved, and what remained outside my responsibility.

  • Constraints and decisions

    The practical limits, trade-offs, and choices that shaped the frontend.

  • Evidence and outcomes

    Only supported results, working links, approved visuals, or documented review records are included.

Have a project that needs a clear frontend path?

Share your goal and I'll suggest a suitable project path without assuming a larger scope than you need.

Start your project brief I'm not sure—help me choose