The official website for forceCalendar — open-source scheduling infrastructure for applications, people, and agents. The landing page separates the shipped engine, UI and Salesforce integration from the shared-calendar/agent layer in development and planned provider synchronization.
/— product overview/core— the headless engine (@forcecalendar/core)/interface— the Web Components UI (@forcecalendar/interface)/salesforce— Salesforce installation guide/platforms— sandboxed platforms the packages run in (Salesforce, ServiceNow, SharePoint, Forge, Chrome MV3, edge runtimes)/playground— live interactive demo running the real published packages
Next.js (App Router) · React 19 · Tailwind CSS · TypeScript. Response headers are defined in next.config.ts, including HSTS and frame-ancestors 'none'. The current CSP permits inline scripts/styles and eval; it is not a strict-CSP compatibility test for the calendar.
npm install
npm run dev # http://localhost:3000
npm run build
npm run lintThe site consumes @forcecalendar/core and @forcecalendar/interface from npm for its live demos, so the playground reflects the published versions resolved by the lockfile. It does not verify a Salesforce package or org deployment.
See the contributing guide. Content fixes and design improvements are welcome.
The install guide distinguishes repository source from install-package releases. Legacy package links are withheld while the new installer is validated. Do not claim a package contains current source changes until its version and contents are verified in a clean org. The salesforce-lightning-* images are real Salesforce Lightning demo captures from October 2, 2026, using Core 2.5.5 and Interface 1.8.1 with synthetic in-memory sample events, including the event creation form. They do not demonstrate live Apex CRUD or verify the package behind the install link. Original salesforce-month.png, salesforce-week.png, and salesforce-day.png assets are retained as earlier demo captures. Refresh Salesforce images only with real org captures using synthetic data after deployment validation.
Before merging content changes, run npm test, npm run lint, npx tsc --noEmit, and npm run build, then check the home page, Salesforce guide, and live demo at desktop and mobile widths.
The landing page uses a scoped CSS module and the real published Web Component. It seeds 23 synthetic appointments from the component’s displayed week, including overlaps. A finite, clearly labeled local API demonstration creates, moves, updates, and deletes one synthetic appointment. It pauses on pointer, keyboard, or scrolling input; reduced-motion disables automatic playback. User interaction never triggers snapshot replacement. Explicit Play resumes the sample sequence. Calendar UI, Event model, and Headless API panels explain the library and its callers without claiming an agent runtime or provider connection. Small screens use a contained horizontal calendar scroller. The maker credit is an understated peer of the bottom technical labels and links to https://dhanawada.org/.
Core and Interface explain the engine and UI separately. Salesforce documents the released installer, package/runtime version distinction, access configuration, verified scope, source deployment, and genuine capture provenance. Platforms distinguishes the released Salesforce distribution from minimal developer starters. The homepage promotes the interactive playground; synthetic examples are not connected provider accounts or production records.