plans/engagify_theme/engagify_theme_step1_solution_assessment.md

Repository source: docs/plans/engagify_theme/engagify_theme_step1_solution_assessment.md

Feature plan: Step 1 · Step 2 · Step 3 · Step 4

Debug mode: enabled

Effort study: railspike-effort / v3/engagify_theme; host ledger. Standing P2 enrollment. No parent cycle.

Extended estimates: enabled

Cycle estimate: 0.75 (revised; original 0.70)

Original Query

I'd like to build a parody theme that has common anti-features in the UI, such as cookie notices, sign up for our newsletter, install our app, etc. Make a list of things to include.

List the ones that (will be most recognizable × easiest to implement).

I love the rate us, let's make a mockup, please.

OK, this has the right idea. The theme should be a ZenMemes theme that can be selected. It should make it easy to switch away when the user is done. This is also where we can start testing page-specific themes, meaning themes that are the default theme for a particular page.

Understood Intent

Add a selectable theme, working name Engagify, that buries the site under familiar dark patterns as a joke. The mockup sets the tone: a rate-us prompt that diverts bad ratings to a private box, then nags again after "Remind me later". The ranked list from the conversation supplies the rest: cookie banner, newsletter popup, "Open in app" bar, fake notification prompt, chat bubble, fake sign-up toasts, a countdown, a paywall fade and stacked sticky bars.

Leaving the theme must take one obvious click from any page. The same cycle adds a page theme: a theme that a specific page shows by default. Engagify is the first page theme, for example on the anti-cookie notice thread.

Problem

Themes today are CSS only and apply site-wide, so a theme cannot show dismissable popups or claim a single page.

Concepts touched: proposed "page theme" (created, every option); theme navigation icons (used unchanged). No matching feedback item in docs/feedback/items/. PF-20261104-B08 concerns the anti-cookie notice's wording only.

Shared by every option

Engagify is a normal entry in ThemeRegistry.php, so the theme menu, cycle button and pre-paint allow-list pick it up.
A page theme beats the site default and the viewer's saved theme, but only on its own page. Otherwise the joke never reaches anyone who has picked a theme.
An "Exit" control in the Engagify chrome restores the viewer's own theme. On a page theme, the page remembers that choice in the browser, so a revisit does not trap the viewer again.
Popups that arrive after a delay break "pages must look final on first paint" on purpose. They appear only while Engagify is active. This exception needs the maintainer's approval.

Option A — Theme script plus a page theme list

Estimate: 0.70 Main driver: a second asset kind per theme and a page theme in the pre-paint script. Uncertainty: medium, mostly in baked thread pages.

A theme may ship theme-engagify.js beside its CSS. The page loads the script only while that theme is active and unloads its popups on exit. The operator lists page themes in configuration, such as one thread path mapped to engagify. The renderer marks the page with its page theme, and the pre-paint script applies it.

Pro: real buttons for Exit, "Remind me later" and star ratings, as in the mockup.
Pro: other themes and pages stay untouched; the script never loads elsewhere.
Pro: page themes need no record format or schema change.
Con: a site setting, not a post, decides each page theme.
Con: baked thread pages need a rebuild after the list changes.

Option B — Option A with the page theme in the thread record

Estimate: 1.00

Moved to v3/theme_directive (planned on branch plan/theme_directive) in Revision 1; kept here as first written. Main driver: a new root header through parser, write path, read model and composer. Uncertainty: medium to high.

The theme script is the same as in Option A. A thread's root record carries a header such as Theme: engagify, like the event headers. The thread page shows that theme by default.

Pro: the author chooses the theme, and it travels with the content into exports.
Con: existing threads cannot gain a header without a new post.
Con: one theme name in a record ties content to a theme that may later be renamed.
Con: a read-model column and a composer field, at roughly the size of a whole cycle.

Option C — CSS-only theme plus a page theme list

Estimate: 0.35 Main driver: decorative pseudo-elements in one stylesheet. Uncertainty: low.

Every nag is a pseudo-element drawn by theme-engagify.css, with no script. Page themes work as in Option A.

Pro: follows the theme guide exactly; smallest change.
Con: nothing can be dismissed or rated, so the bit loses its punchline.
Con: decorations must not cover real controls, which limits overlays to edges.

Recommendation

Choose Option A. It delivers the mockup's interaction, keeps the theme guide's rule that other themes stay untouched, and gives page themes a small first form. Option B's record header can follow once page themes prove useful.

First vertical slice: Engagify selectable from the theme menu with the rate-us flow, cookie banner, newsletter popup and Exit. Second slice: the page theme list, with Engagify on one thread. Further nags from the ranked list follow in later stages if time allows.

Open question for Step 2: which page gets Engagify first. The anti-cookie notice thread is the suggested candidate.