Source identity
| Field | Recorded value |
|---|---|
| Source type | GitHub source |
| Original record | Janady13/thatdeveloperguy-website / content/pages/government/page.json |
| Date | Not specified in source |
| Repository | Janady13/thatdeveloperguy-website |
| Revision | 2bea2ebdff0e34494bff597d4fa9c8422a0c3a94 |
| Branch | main |
| Path or archive member | content/pages/government/page.json |
| Original SHA-256 | 3a034851277a5a877b419769cebbf5536228b79cf70ddcfebf495d2767bf5316 |
| Git blob SHA | 919a10159ce2e10b908b17b1f60da22c86681638 |
| Reading-copy SHA-256 | 3a034851277a5a877b419769cebbf5536228b79cf70ddcfebf495d2767bf5316 |
Recovered source transcript
Download complete source text ↓17 lines · 2.2 KB
{ "id": "audience.government", "path": "/government", "template": "audience", "parentId": "home", "audience": ["government", "prime-contractors"], "primaryIntent": "Understand how a government organization or prime contractor buys from ThatDeveloperGuy",
"title": "Government Solutions — ThatDeveloperGuy", "description": "How government organizations and prime contractors scope, contract and receive IT, cybersecurity and software work from ThatDeveloperGuy LLC.",
"heading": "Government Solutions", "summary": "Planning, requirements, contracting and delivery for agencies and the primes that serve them.",
"bodySource": "body.md", "sceneId": "government",
"primaryAction": { "label": "Request a project briefing", "pageId": "contact", "project": "govweb" },
"relatedPageIds": ["capability.business-it", "capability.cybersecurity", "company"],
"entityReferences": ["organization"], "claimReferences": [],
"publicationStatus": "demo", "approvalReference": "owner-demo-2026-09-15", "indexPolicy": "index",
"sections": [
{ "id": "solutions", "heading": "Government solutions", "body": "Websites, internal applications, workplace IT and security work for public organizations, scoped to the requirement and delivered with the records a reviewer expects." },
{ "id": "planning", "heading": "Project planning", "body": "Scope, schedule and acceptance criteria are written down before work starts. Changes are recorded, not absorbed." },
{ "id": "requirements", "heading": "Review requirements", "body": "Accessibility, records retention, security review and hosting constraints are read from the solicitation and confirmed with the buyer." },
{ "id": "contracting", "heading": "Contracting and capability statement", "body": "Procurement identifiers (CAGE, SAM.gov registration status, NAICS codes, set-aside status) are shown here only once the owner supplies and verifies them." },
{ "id": "process", "heading": "Delivery process", "body": "Discovery, build, review, handover. Each step ends with something the buyer can inspect." },
{ "id": "delivery", "heading": "Government websites and workplace IT", "body": "Public sites, staff tools and the machines and networks that run them." }
] }