Editor workflow
Editors work in the admin to create, review, schedule, revise, and publish content. They do not need Git to do normal editorial work.
Core surfaces
Pages, posts, media, redirects, comments, users, translations, settings, and revisions are all intended to be managed from one bounded admin surface.
Provider neutrality
Editors should not have to learn provider-specific runtime differences just to update content. Adapters absorb those differences behind stable contracts.
What Astropress is trying to avoid
The project is intentionally not drifting toward a universal website builder. The goal is a simpler, more operable publishing app for clearly bounded sites.