Owned productPrivate editorial music club
Still Stage
Brings themed issues, essays, and record notes together in one digital product.
- Current status
- Operating
- Author’s role
- Creator and music editor
Product task
Bring editorial content, member access, and publishing into one product that can evolve without separating content work from operations.
Author’s role
I created the product and its editorial model, lead the music work, and take responsibility for its architecture, releases, and production path.
Decisions that mattered
These are not technology badges. Each choice closes a concrete product or operating constraint.
A modular Flask monolith as one production unit
- Constraint or risk
- Editorial and server-side access functions need to evolve together, while the product scale does not justify distributed infrastructure.
- Why this choice
- One deployable unit reduces operating coordination, while module boundaries preserve separation of responsibilities inside the application.
PostgreSQL 18 for persistent data outside the application container
- Constraint or risk
- Timeweb App Platform replaces the container during deployment, so its runtime filesystem cannot be treated as persistent storage.
- Why this choice
- Product state stays separate from the replaceable compute layer and does not depend on the container lifecycle.
Explicit /ru/ and /en/ routes with canonical and hreflang links
- Constraint or risk
- Each language needs a direct URL and indexable HTML instead of existing only as client-side interface state.
- Why this choice
- The locale is encoded in the URL, and every public page declares its paired language alternative.
What the facts establish
Demonstrates the ability to bring an owned product into operation and maintain it.
Fact → evidence → boundary
Evidence record
An editorial product with member access
- Evidence
- Themed issues, a journal, registration and sign-in are available on the website. Its author creates the product and leads the music editing.
- Boundary
- The public surface establishes public functions; member-only access and real payments require separate checks.
Deployed code and accepted functionality are distinct
- Evidence
- The project record separates deployment of the cover editor code from the still pending acceptance of public use.
- Boundary
- A version number and a healthy server do not establish completion of every user workflow.
Data outlives application replacement
- Evidence
- Persistent data resides in a separate PostgreSQL database; the application is deployed separately.
- Boundary
- This separation alone does not prove backup recovery or continuous availability.
The date belongs to the source record. Reading it is not a new check of the operating system.
Verify it yourself
Public verification boundary. The RU/EN public surface, issue description, journal, registration, and sign-in paths are open for inspection. The member-only area and internal operating data are not presented as public evidence.