vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(phasefinal-web): expand site to a multi-page cluster

Browse Source 
Single page grows to nine: custom app development, systems engineering,
hosting, and AI services each get a detail page, plus engagement,
track-record, contact, and privacy. Cross-linked nav and footer on every
page; brand CSS extended in place (still zero external requests, zero JS).

Motivation: an app-store registration review flagged the single-page site
as minimal content. This version is intended to be reverted after approval.
This commit is contained in:
vh
2026-09-28 09:59:43 -07:00
parent 1756b891c6
commit 7bd00ae77a
10 changed files with 738 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/phasefinal-web/conf/site/engagement/index.html
+83
View File
@@ -0,0 +1,83 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>How We Engage — Phase Final, Inc.</title>
<meta name="description" content="Engagement models at Phase Final, Inc.: fixed-bid scopes with defined deliverables, or retainers for continuous operation and engineering capacity.">
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="/style.css">
</head>
<body>
<header class="page-header">
<div class="hero-inner">
<a href="/"><img class="wordmark" src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." style="text-decoration:none"></a>
<div class="hero-copy">
<p class="lede">Fixed-bid or retainer. Both with one owner.</p>
<p class="sublede">Engagements are fixed-bid or retainer, chosen by the shape of the work rather than by preference. Most new work arrives by referral.</p>
</div>
</div>
</header>
<nav class="site-nav" aria-label="Site">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services/software/">Custom App Development</a></li>
<li><a href="/services/systems-engineering/">Systems Engineering</a></li>
<li><a href="/services/hosting/">Hosting</a></li>
<li><a href="/services/ai/">AI Services</a></li>
<li><a aria-current="page" href="/engagement/">Engagement</a></li>
<li><a href="/track-record/">Track Record</a></li>
<li><a href="/contact/">Contact</a></li>
</ul>
</nav>
<main>
<section id="models">
<h2><span class="num">01</span>Engagement models</h2>
<div class="section-body">
<ul class="detail-list">
<li>
<h3>Fixed-bid</h3>
<p>Where the scope can be specified: a defined deliverable at a defined price, with written requirements and acceptance criteria before work starts. Change requests move scope, not the deadline's meaning.</p>
</li>
<li>
<h3>Retainer</h3>
<p>Where the work is continuous: operation, maintenance, and engineering capacity over time. A named owner, a standing review cadence, and a queue the client controls.</p>
</li>
</ul>
</div>
</section>
<section id="flow">
<h2><span class="num">02</span>How an engagement runs</h2>
<div class="section-body">
<ul class="detail-list">
<li><h3>1. Spec and constraints</h3><p>You send the spec and the deadline. We send back what it takes to reach the final phase — including the parts of the spec that turn out to be in tension with the deadline.</p></li>
<li><h3>2. Written plan</h3><p>Requirements, acceptance criteria, and milestones on paper before code. On a fixed bid, this document is the contract's second half.</p></li>
<li><h3>3. Build in the open</h3><p>Regular demos against real environments, not mockups. Problems surface during the build, at build-time prices.</p></li>
<li><h3>4. Handover or operate</h3><p>Documentation, runbooks, and a clean handover — or we keep operating it under retainer. Both are first-class outcomes.</p></li>
</ul>
<p class="related"><a href="/contact/">Start a conversation →</a></p>
</div>
</section>
<footer>
<span>Phase Final, Inc.</span>
<nav aria-label="Footer">
<a href="/services/software/">Apps</a>
<a href="/services/systems-engineering/">Systems</a>
<a href="/services/hosting/">Hosting</a>
<a href="/services/ai/">AI</a>
<a href="/engagement/">Engagement</a>
<a href="/track-record/">Track Record</a>
<a href="/contact/">Contact</a>
<a href="/privacy/">Privacy</a>
</nav>
</footer>
</main>
</body>
</html>