Early Development
4WP Planner
Internal WordPress planning instrument for content, plugin releases, and calendar-driven workflows — planning only, no automated actions.
Version 0.3.0 · WordPress 6.4+ · PHP 7.4+ · Early-stage development · GitHub only (WordPress.org not submitted)
4WP Planner is in early-stage development. It is an internal instrument for the 4WP studio — not a finished product listing. Source, architecture notes, and MVP scope live on GitHub; expect breaking changes between releases.
Plan content and plugin work inside WordPress
Track articles, releases, social posts, and tasks across projects and time windows — with week/month calendar views, optional Google Calendar export, and REST endpoints for future integrations. The plugin helps you plan; it does not publish, deploy, or run automations on your behalf.
Domain model
- Projects — workspaces (4wp.dev, client sites, product lines).
- Plans — weekly, monthly, or quarterly planning windows with start and end dates.
- Items — atomic work units: articles, plugin releases, social posts, tasks, and more.
- Calendars — Google and ICS integrations (export layer, not a separate product module).
- Insights — internal gap analysis: overdue items, planning gaps, overload signals.
Week and month calendars are views inside Plans — powered by FullCalendar in the admin — not standalone modules.
What works today (MVP)
- Admin menu: 4WP Planner → Overview, Projects, Plans, Items, Insights, Calendars
- Demo data seeds on first activation — sample project, weekly plan, items, and a calendar connection
- ICS feed export — import into Google Calendar via URL
- Per-item Add to Google Calendar when a due date is set
- REST API namespace
fwpp/v1— projects, plans, items, calendars, insights, meta
On the roadmap
- Google Calendar OAuth — two-way sync (planned)
- Parent / child items — e.g. article → LinkedIn post
- Plugin registry linked to GitHub / WordPress.org
- Plan templates and recurring plans
Built for studio workflows
Early MVP — focused on clarity of planning, not automation
Structured planning
Projects → Plans → Items keeps content, releases, and tasks in one WordPress admin — instead of scattered spreadsheets.
Calendar views
Week and month views over plans and due dates — plus ICS export and per-item Google Calendar links in the current MVP.
REST-first
fwpp/v1 endpoints for projects, plans, items, calendars, and insights — groundwork for dashboards and external tooling later.
Requirements
| WordPress | 6.4 or higher |
| PHP | 7.4 or higher |
| Version | 0.3.0 (early development) |
| Distribution | GitHub — WordPress.org not submitted |
| Status | Internal / early access — not recommended for production client sites yet |
FAQ
Early-stage plugin — answers based on current GitHub documentation and architecture notes
What is 4WP Planner?
An internal WordPress admin tool for planning content, plugin releases, and calendar-driven work across projects, plans, and items. It is designed for studio workflows at 4WP.dev — not as a generic project-management SaaS replacement.
Is it ready for production?
No — early-stage development. The plugin is actively evolving (currently v0.3.0). APIs, admin screens, and calendar sync may change between releases. Use on staging or internal installs until we publish a stable roadmap.
Is it on WordPress.org?
Not yet. Install from the GitHub repository. An official directory listing has not been submitted.
Does it publish content or run automations?
No. Planning only — no automated actions. 4WP Planner helps you organize work and due dates; it does not post to WordPress, social networks, or deploy plugins on your behalf.
What can I plan with it?
Items support typed work units — articles, plugin releases, social posts, tasks, and related studio work — grouped under projects and optional weekly, monthly, or quarterly plans.
Does it integrate with Google Calendar?
MVP includes ICS feed export and per-item “Add to Google Calendar” links. Two-way Google OAuth sync is on the roadmap — see GOOGLE-SETUP.md in the repository for current setup notes.
Is there a REST API?
Yes — namespace fwpp/v1 with routes for projects, plans, items, calendars, insights, and meta. Useful for future dashboards or internal tooling; treat endpoints as unstable during early development.
Follow early development on GitHub
Clone the repo, read ARCHITECTURE.md, and try the MVP admin — feedback welcome while the product is still taking shape.