Context
Currently all app detail pages look identical because modded apps inherit the source app's README, name, description, and tags unchanged. Every app in the registry looks the same, which makes discovery harder and reduces the sense of ownership for developers who deploy their own version.
What we want — deploy-time prompt covering the full metadata set
Before the final publish step (after the domain is set), the CLI and RevX should prompt the developer to update their app's:
- Display name (defaults to the modded source's name)
- Description (one-liner shown in the Apps grid + on the App Detail Page)
- Category tags (multi-select from the existing tag set used on the Apps tab filters)
- README (prompt to edit; skip = keep the inherited README; never silently copy the source app's README verbatim into the published metadata)
Flow sketch:
- ✔ domain → myapp01.dot
- → Name: [defaults to source name, editable]
- → Description: [cursor]
- → Tags: [multi-select chips]
- → Edit your README now? [Y/n] — opens $EDITOR / RevX file pane
- → Publish
Skip = keep the current source value; the user can still edit later in playground.dot (see playground-app #202).
Related
Updated to broaden scope from description-only (original framing) to the full metadata set including tags.
Context
Currently all app detail pages look identical because modded apps inherit the source app's README, name, description, and tags unchanged. Every app in the registry looks the same, which makes discovery harder and reduces the sense of ownership for developers who deploy their own version.
What we want — deploy-time prompt covering the full metadata set
Before the final publish step (after the domain is set), the CLI and RevX should prompt the developer to update their app's:
Flow sketch:
Skip = keep the current source value; the user can still edit later in playground.dot (see playground-app #202).
Related
Updated to broaden scope from description-only (original framing) to the full metadata set including tags.