Skip to main content
Calhoun.
Get a Quote
All work

Case study · 2026

If the Shoo Fits

A Utility Site with basic authentication add-ons that keeps important team and director documents organized in one place for easy reference.

Client
Multi-location Chick-fil-A operation
Location
East Pasco County, Florida
Project type
Private internal web application
Package
Utility Site + basic authentication add-ons
Homepage design for If the Shoo Fits

Before the project

Important team and director resources needed one dependable home.

Team members and directors needed a central place to reference important documents, policies, resources, and location-specific information. As the organization expanded to a second location, the resource library also needed to stay organized and make protected director material easy to find without exposing it to the full team.

What I changed

I created one organized resource library for the team and a protected area for directors.

The site organizes reference material by audience and location so team members can quickly find the document or resource they need. Director-only material sits behind a basic sign-in, and approved leaders can replace selected documents and headshots from the browser when information changes.

What the finished site does

  • Reference documents and resources grouped by audience and location
  • Password-protected director area
  • Browser-based replacement of selected PDFs, images, and headshots
  • Mobile-friendly access for team members referencing resources from a phone
  • Shared structure for the Zephyrhills and Dade City locations

A closer look

Screens from the public site and the tools used behind it.

The public pages help visitors decide whether to inquire. The private screens help the business manage the work that follows.

If the Shoo Fits mobile home page for Chick-fil-A East Pasco team members
The mobile home page gives team members a quick path to the documents and resources they may need to reference from a phone.
If the Shoo Fits community involvement page with local outreach information
The community page keeps local involvement information available alongside the rest of the organization's reference material for both locations.
If the Shoo Fits frequently asked questions page for team members
The FAQ page keeps common questions and answers in the same resource library as the team's other reference material.
Password wall protecting director resources on If the Shoo Fits
Basic authentication add-ons protect director-only documents while keeping general team resources easy to access and reference.

What improved

Important resources are easier to find when someone needs to reference them.

The finished Utility Site gives team members and directors a dependable reference point for important information. Resources for Zephyrhills and Dade City live within the same structure, while protected director documents remain limited to the people who need them.

For technical readers

A few behind-the-scenes choices that make the site easier to use and maintain.

Here are the main technical choices behind the project and why they matter.

Technology

  • Next.js 16
  • React 19
  • TypeScript
  • Vercel Blob
  • Vercel serverless routes

Work included

  • Information architecture
  • Responsive web design
  • Next.js development
  • Protected director access
  • Document management

Structure

One structure for both locations

Zephyrhills and Dade City use the same page structure, so leaders are not maintaining two separate versions of the same information. Shared layouts also make future changes easier to roll out consistently.

Protected access

Different permissions for different jobs

Directors can open protected resources, while a smaller group has permission to replace files. Keeping those permissions separate means leaders can share information without giving every user access to the management tools.

Document updates

Leaders can replace common files themselves

Selected PDFs, images, and headshots can be replaced from the browser when information changes. That helps leaders keep the resource library current without needing a developer each time a document is updated.

Why the private areas stay private

Access is limited to the people who need it.

  • Director resources require sign-in
  • Managed files are kept in private storage
  • Only approved file types and locations can be replaced

Why these choices matter

The site can grow without becoming harder to maintain.

  • Both locations share the same structure instead of duplicating pages.
  • Leaders can replace selected reference files without touching code.
  • The resource library remains easy to reference from a phone when a team member or director needs information away from a computer.

Project note

This is a private internal application, so the live site and operational documents are not publicly linked. The case study shows the approach without exposing credentials or internal files.

Have a project in mind?

Tell me what is making it harder for customers to book, buy, or find the information they need.

Start Your Project