Codex Sites examples are 30 copyable workflow templates for internal apps. Open one to see its prompt, pages, storage and access plan, then copy it or customize it in the prompt generator.
Each template is a working pattern, not a finished app. It gives you the audience, core pages, data model (D1 or R2), access rules and a testing checklist, so you can paste a complete @Sites prompt instead of describing a vague idea.
Two ways to use one: open a template and copy its full prompt, or open the prompt generator to edit the app type, audience, workflow, storage and access into your own draft.
A workspace hub for new hires, task owners, policy links and first-week checkpoints.
SalesApproved decks, objection scripts, pricing notes, battlecards and feedback loops for revenue teams.
OperationsA weekly operating dashboard that summarizes status, blockers, owners and metric changes.
ProductMilestones, launch owners, readiness signals, risks, content tasks and approval dates.
MarketingVenue, speaker, sponsor, budget, run-of-show and follow-up task planning in one app.
ProductCluster user feedback by segment, severity, product area, owner and review status.
TeamSearchable procedures, owners, freshness status, decision notes and missing-article requests.
MarketingCampaign briefs, channels, publish dates, dependencies, creative status and KPI notes.
StartupA private monthly investor update room with metrics, asks, narrative and Q&A tracking.
HRBenefits, policies, forms, employee FAQs, request routing and ownership metadata.
ProductReadiness checklist, launch risks, release notes, support prep and stakeholder approvals.
OperationsTeam metrics, owner notes, trends, alert thresholds and review cadence.
EngineeringBug intake, severity, reproduction steps, owners, sprint target and resolution status.
AgencyA client review workspace for deliverables, decisions, comments, milestones and approvals.
TeamStructured meeting notes with attendees, decisions, action items and search filters.
PeopleCandidate stages, interview feedback, owners, next steps and hiring manager views.
FinanceExpense intake, approval status, policy notes, owner comments and export-ready records.
LeadershipObjectives, key results, confidence, owners, blockers and weekly check-in history.
GrowthHypotheses, variants, metrics, status, learnings and decision records for growth tests.
MarketingCreator pipeline, deliverables, rates, contract status, performance and renewal notes.
AgencyShared campaign briefs, files, approval queues, risks and next actions for client teams.
LocalShift notes, inventory issues, repairs, reservations, daily sales and staff updates.
Real EstateDeals, comps, underwriting notes, tasks, documents, risk flags and next calls.
EducationLessons, worksheets, cohorts, office hours, support requests and learner progress notes.
CommunityMember profiles, skills, interests, join date, tags, referrals and moderation notes.
SupportTicket categories, severity, owner assignment, response status and escalation views.
OperationsInternal app requests, impact, requester, owner, status, dependencies and review notes.
ContentIdeas, drafts, channels, owners, publish dates, approvals and performance follow-ups.
LeadershipDecisions, context, alternatives, owners, date, reversibility and follow-up tasks.
SecurityVendor reviews, risk notes, controls, evidence, approvers and renewal reminders.
The same answers are published as FAQPage structured data on this page.
They are 30 ready-made workflow templates — onboarding hubs, dashboards, launch calendars, review rooms, trackers and resource libraries — that show a repeatable pattern you can copy into a Codex Sites prompt instead of starting from a blank page.
Open the template to read its suggested pages, D1/R2 storage plan, access model and testing checklist, then copy the full prompt or edit it in the prompt generator before pasting it into Codex with Sites available.
No. They are independent patterns written by CodexSites.org to plan a Codex Sites build. This site is not affiliated with OpenAI, and availability of Codex Sites itself stays an official-provider question.
Start with the template closest to your workflow — onboarding hub for HR, pulse dashboard for operations, or launch calendar for releases. If nothing matches, use the prompt generator to build a prompt from scratch.
Most templates store structured records, so D1 is the recommended database. R2 is optional and only needed when the workflow requires uploading files. Check each template's build notes for its storage plan.
After you pick a template, check access and write the prompt.
