The OC Guy
77d3f00072
- css/site.css: oat/espresso palette, Fraunces display, rounded surfaces, warm photo grade - index.html: Module of the Month replaced by the blog; tips, blog and community sections render from data/posts.json - js/feed.js: client-side feed + search over one manifest (blog/index.json technique) - scripts/sync_posts.py: daily webhook fetch, image download, dedupe by id and content hash, non-image attachments skipped - data/posts.json: manifest, one published post (Odoo 20 Community review)
4.0 KiB
Product
Platform
web
Stack
Plain static HTML/CSS. No framework.
Users
Small companies and startups searching for a business solution in the AI era. They need an affordable, battle-proven ERP as a foundation — and The OC Guy shows them how ODOO Community + AI is the answer. The visitor should walk away seeing ODOO Community as the smart, cheap backbone for an AI-powered business.
Product Purpose
oc-guy.com is the homepage and brand hub for The OC Guy — the alter ego of Oliver Arnold (安雷威), an advocate for using ODOO Community as the affordable, battle-proven ERP foundation for bolting AI on top. The site introduces The OC Guy, explains the mission, and drives engagement with video content and community resources.
Positioning
ODOO Community is the best kept secret in business software — a full-featured, production-hardened ERP that costs fractions of the proprietary alternatives, and it's the perfect platform for the AI era. The OC Guy exists to wake up small companies and startups to this truth. The strong belief: you don't need expensive enterprise licenses to run a modern, AI-powered business — you need ODOO Community plus smart AI on top.
Operating Context
- Site served as a static webpage at
https://oc-guy.com - Content is video-driven — scenes, title cards, and screen captures exist in
/root/workspace/40_assets/ - ODOO instance used for demos:
https://005-003-9a9333fc-1f68-4786-a4fe-5c6d24d207ed.odoo4projects.com - Repo at
/root/oc-guy, push-to-deploy viagit push origin main
Capabilities and Constraints
- Single-page or simple multi-page static site
- Must host/surface video content from the broader project
- Must communicate the ODOO Community + AI positioning clearly
- [OPEN] Email/newsletter signup? Not yet decided.
- [OPEN] Blog or changelog section? Not yet decided.
Brand Commitments
- Name: The OC Guy
- Tagline: ODOO Community Advocate
- Creator: Oliver Arnold / 安雷威
- Visual identity: warm editorial. Oat ground
#F2E9D6, espresso ink#3B2619, warm sand#D9C7A5, honey oak#AC8050, dusty navy#29444B, muted olive#747552, terracotta accent#B76D48. Chunky rounded display type (Fraunces), soft rounded surfaces, warm window light, matte textures. No stark white, no pure black, no neon, no cyberpunk. - Style authority:
/root/workspace/shared/manifesto/STYLEGUIDE.md— read it before changing any page. Claims and voice authority:MANIFESTO.mdin the same directory. - The old dark/purple/cyan video identity (
#0a0a0f,#9C27B0,#00E6FF) is retired for web. Video title cards still needing it should be re-rendered in the warm palette rather than reintroducing the old one. - Domain:
oc-guy.com
Evidence on Hand
- Title screen HTML with brand styling:
/root/workspace/40_assets/title_screen_hyperframes.html - Frame renderer with palette and animations:
/root/workspace/40_assets/frame_renderer.html - Video scenes (s1.mp4 through s4.mp4) and PNG title/end cards in
/root/workspace/40_assets/ - ODOO login page screenshot:
/root/workspace/40_assets/odoo_login_page.png - No testimonials, case studies, press mentions, or customer logos available. None should be fabricated.
Product Principles
- Visual energy matches the mission — The cyberpunk aesthetic signals this is forward-looking tech, not dusty enterprise software.
- Community first — The OC Guy serves the ODOO Community. Value, advocacy, and connection over sales.
- Video as the primary medium — The OC Guy communicates through video content. The site is a hub that leads there.
- Authenticity over hype — Real ODOO features, real demonstrations, real positioning. No fabricated success stories.
- Keep it lean — Static HTML/CSS, no build tooling, no framework overhead. Fast to load, simple to maintain.
Accessibility & Inclusion
No specific accessibility requirements have been established. As a public website, WCAG 2.1 AA compliance should be targeted. Video content should include captions.