Last updated on April 22, 2022.

This document and the information contained therein are intended for illustrative purposes only. The enclosed content is the sole property of Gone Fishing Studio LLC.

📖 Abstract

• Develop a best in class, responsive website for the XYZ Portfolio.
• Utilize modern tooling and best practices to deliver a thoughtful experience for the XYZ audience.
• Employ forward-thinking development for the maintainers of the site as it evolves, both for the content managers as well as any code owners.

⏳ Process

Our development process is broken up into four phases: Core Development, Content Integration, User Testing & QA, and Post Launch Support.

Core Development

With approved design mockups in hand, we begin the web development process. Live staging links will be provided at designated checkpoints along the way as we work towards a live beta of the site. It's also recommended that we have a weekly standup during this phase. This a top to bottom build of all deliverables listed in the statement of work. There may be bits and pieces of polish left until QA, but this generally includes:

• Frontend template development
• CMS architecture and placeholder content
• Interactions and animations
• Staging hosting environment

Content Integration

We deliver a content outline to you that specifies all required copy and asset specifications. Once we receive a filled in content outline we populate all initial content into the staging CMS ahead of launch.

User Testing & QA

Once initial content is populated, we start this phase; it has two parts:

1. We deliver a bug tracker (generally a Notion Kanban board) to triage requests, and update you on progress as we head to launch. We reserve a fixed period, typically 1 week, for both teams to go through the staging site and make notes on tweaks, fixes, and suggestions on anything that doesn't feel quite right.
2. We pause User Testing, and enter QA. This period is reserved for addressing any requests before launch. We provide frequent check ins through this process, and are often in communication on a daily basis as we work through the list. Completing any requests made after this process starts will be addressed at our discretion.

Launch & Post Launch Support

After completing QA, it's time to launch this thing! Typically, this entails us making DNS updates to point the the current domain to the new website. We then hand off all hosting information, 3rd party service credentials, and other documentation.

After launch, we reserve a 30 day period to be available to you for a smooth launch. Generally this is for small fixes that went unnoticed, tutorials of the CMS, and general support. This 30 day period includes a 10 hour budget.

Example Deliverables

• Bug fixes
• Client team training
• Low-level optimization and enhancement of existing codebase
• Incorporation of plugins or apps
• Updating content and assets within existing website pages

🧩 Components of a Headless Website

There are two larger components to this headless build:

1. Sanity.io as the CMS

Sanity.io is a CMS built for headless experiences. It allows for highly customized content management, and additionally can be extended to include internal tools analytics, CRM type functionality, and more.

2. Netlify for CDN Hosting

After you're done building out your content in Sanity, Netlify then automatically builds and hosts your website. This prebuilt website is then served across Netlify's content delivery network. This prebuilt website is a collection of HTML files, along with any static assets like CSS, JS, and images. Additionally, there are a set of serverless functions. This can give us the ability integrate 3rd party APIs for search and filtering, and more.