Project Boundaries
What Jenna Press does not aim to do, and why those boundaries protect the project.
A useful framework needs exclusion rules
Jenna Press is not trying to be a visual site builder, a collaborative editorial suite, or a general application shell. Those are valid products, but they require different trade-offs.
The project also avoids hidden expansion pressure. If a feature requires a runtime backend, a custom permission model, or highly dynamic personalization, it probably does not belong in the core framework.
These exclusions are not a weakness. They are the reason the supported path can stay clean.