Skip to content

Latest commit

 

History

History
36 lines (27 loc) · 1.23 KB

File metadata and controls

36 lines (27 loc) · 1.23 KB

Principles & Positioning

Principles

  • WordPress remains the runtime.
  • Symfony components provide structure where structure pays off.
  • Packages should be small, composable, documented, and testable.
  • Integration should improve maintainability without hiding WordPress behavior.
  • Adoption should work one package at a time.

What SymPress Is Not

SymPress is intentionally not:

  • a replacement for WordPress
  • a full-stack framework that hides WordPress
  • a page builder
  • a theme framework
  • a plugin marketplace
  • a reason to avoid learning WordPress APIs

The goal is to make WordPress projects more maintainable while keeping them recognizably WordPress.

Contributing

SymPress is built as an open project, and focused contributions are welcome. Bug reports, feature ideas, documentation improvements, examples, tests, and pull requests all help the project move forward.

If you are curious about modern WordPress architecture, Symfony components, Composer-first workflows, or better developer experience for WordPress teams, there is room to contribute. Start with the issue templates when opening new work, and read the contribution guide before sending larger changes.