How peterwaf/pimofy-site works
1. Repository type and runtime
- This is a fully static marketing website for Pimofy Digital.
- There is no backend, no build pipeline, and no frontend framework; everything is served as plain HTML/CSS/JS, making the deployment boundary essentially “static hosting.”
2. Page-level architecture
- The site is organized as a set of standalone HTML pages: index.html, solutions.html, data-operations.html, capacity-audit.html, industries.html, resources.html, about.html, contact.html, plus supporting content/legal pages like privacy.html, terms.html, and several article-style pages.
- Each page is a separate entry point, so navigation is document-based rather than SPA routing.
3. Primary user journeys
- The architecture is conversion-oriented: visitors move from home → solutions/service pages → contact/audit CTA.
- Key funnel pages include the Data Operations Pod™ detail page, the Free Operations Capacity Audit™ page, and the Book a Call / Contact page.
4. Content and information structure
- The site includes a resources/blog hub and multiple long-form article pages such as hidden-cost-of-bad-data.html and why-best-people-shouldnt-do-data-entry.html.
- These pages function as SEO/content marketing assets rather than dynamic CMS-rendered content.
5. Shared presentation layer
- styles.css is the single global design system for the entire site.
- It centralizes brand tokens, layout rules, responsive behavior, typography, spacing, and animations; the README notes that colors and spacing are driven by CSS variables in :root.
6. Client-side behavior layer
- script.js is the only JavaScript module and acts as the shared interaction controller across all pages.
- It handles the navigation system, dropdown behavior, mobile menu, FAQ interactions, scroll-reveal animations, and form-related behavior.
7. Interactive boundaries
- Interactivity is intentionally lightweight and browser-native: the site relies on standard DOM behavior plus progressive enhancement.
- The README indicates graceful fallback behavior for features like IntersectionObserver, so core content remains visible even when advanced browser APIs aren’t available.
8. Assets and media
- The assets/ directory contains the brand and imagery used across the site: logo.png, hero.jpg, and team.jpg.
- These are static media dependencies; there is no separate asset pipeline or CDN configuration visible in the repo.
9. External service touchpoints
- The only explicit external service in the repo description is Calendly on the contact page, paired with a fallback form.
- That makes the contact page a boundary between the static site and an external scheduling workflow.
10. SEO and discovery layer
- SEO is treated as a first-class architecture concern: each page has unique title/description metadata and canonical URLs.
- The home page includes Open Graph data and Organization schema, while the Data Operations page includes FAQ schema in JSON-LD.
- robots.txt and sitemap.xml support search indexing and crawl control.
11. Accessibility and performance posture
- The site is built to be accessible and fast: semantic landmarks, skip link, focus states, ARIA support for nav/FAQ, and labeled form fields are called out in the README.
- Performance choices include no framework overhead, a single stylesheet, a deferred script, and font preconnects.
12. How to diagram it
- The cleanest architecture diagram is: static pages at the center, shared CSS/JS as cross-cutting layers, assets as static dependencies, and Calendly + search engines as the only meaningful external integrations.
- There are no internal services, databases, or APIs to model beyond those boundaries.
Main entry points: index.html Home · resources.html Resources · data-operations.html Data Ops · styles.css Styles
Components 25
Pages
Standalone marketing, service, content, and legal entry points.
- Home · Primary entry point and conversion hub.
index.html - Solutions · Overview of offerings and service paths.
solutions.html - Data Ops · Core Data Operations Pod™ offering page.
data-operations.html - Audit · Free Operations Capacity Audit™ funnel page.
capacity-audit.html - Contact · Book-a-call and contact conversion page.
contact.html - Resources · Blog and SEO content hub.
resources.html - About · Brand, team, and credibility page.
about.html - Industries · Industry positioning and use cases.
industries.html - Bad Data · SEO article on the cost of poor data.
hidden-cost-of-bad-data.html - Best People · SEO article on avoiding data entry bottlenecks.
why-best-people-shouldnt-do-data-entry.html - Pod Results · Outcome-focused article for the data pod offering.
dedicated-data-operations-pod-results.html - Capacity Buy · Article on buying capacity versus labor.
outsourcing-buying-capacity-not-labor.html - Protect Capacity · Article on preserving team capacity while scaling.
protect-team-capacity-as-you-scale.html - SaaS Capacity · Article on the capacity problem in SaaS.
saas-capacity-problem.html - Privacy · Privacy policy.
privacy.html - Terms · Terms of service.
terms.html
Shared layer
Global presentation and interaction code reused across pages.
SEO ops
Crawl and discovery files that support indexing and metadata.
Assets
Static brand and imagery dependencies.
- Logo · Site logo used across pages.
- Hero image · Primary marketing image.
- Team image · Team and credibility image.
External
Third-party service touchpoints and discovery targets.
- Calendly · External booking workflow from the contact page.
- Search engines · External indexing and organic discovery channel.
Connections 41
- Home → Solutions: nav · Primary path into services.
- Home → Data Ops: nav · Key service detail journey.
- Home → Audit: cta · Conversion path to the audit offer.
- Home → Contact: cta · Direct lead capture path.
- Home → Resources: nav · Content and SEO discovery path.
- Home → About: nav · Credibility and company context.
- Home → Industries: nav · Industry positioning path.
- Solutions → Data Ops: detail · Main solution branch.
- Solutions → Audit: cta · Offer to assess fit and capacity gaps.
- Solutions → Contact: cta · Lead handoff from service overview.
- Data Ops → Contact: cta · Book a call after reviewing the offer.
- Data Ops → Audit: cta · Audit as the lower-friction next step.
- Audit → Contact: cta · Schedule after audit interest.
- Contact → Calendly: book · External scheduling integration.
- Resources → Bad Data: article · SEO article entry.
- Resources → Best People: article · SEO article entry.
- Resources → Pod Results: article · SEO article entry.
- Resources → Capacity Buy: article · SEO article entry.
- Resources → Protect Capacity: article · SEO article entry.
- Resources → SaaS Capacity: article · SEO article entry.
- Robots → Search engines: crawl · Guides crawler access.
- Sitemap → Search engines: discover · Supports organic discovery.
- Home → Styles: uses · Global styling dependency.
- Solutions → Styles: uses · Global styling dependency.
- Data Ops → Styles: uses · Global styling dependency.
- Audit → Styles: uses · Global styling dependency.
- Contact → Styles: uses · Global styling dependency.
- Resources → Styles: uses · Global styling dependency.
- About → Styles: uses · Global styling dependency.
- Industries → Styles: uses · Global styling dependency.
- Home → Script: uses · Shared interaction layer.
- Solutions → Script: uses · Shared interaction layer.
- Data Ops → Script: uses · Shared interaction layer.
- Audit → Script: uses · Shared interaction layer.
- Contact → Script: uses · Shared interaction layer.
- Resources → Script: uses · Shared interaction layer.
- Home → Logo: media · Brand asset dependency.
- Home → Hero image: media · Hero imagery dependency.
- About → Team image: media · Team imagery dependency.
- Data Ops → Hero image: media · Marketing imagery dependency.
- Audit → Hero image: media · Marketing imagery dependency.