Skip to content

SnapWeb Roadmap 0.4.0 / Getting Started

SnapWeb Roadmap overview

Browse delivery states, vote once per item, and submit moderated feedback.

SnapWeb Roadmap

Version 0.4.0 adds a real progress timeline to every item detail. When staff move an item between considering, planned, in progress, shipped, or declined, Roadmap records the previous state, new state, and UTC time. The latest 25 transitions are returned through the portable presentation contract and rendered consistently in standalone WordPress, SnapWeb, and FluentCommunity.

SnapWeb Roadmap publishes considering, planned, in-progress, shipped, and declined work at /roadmap/. Visitors can browse the roadmap and read complete item details. Signed-in users can cast one vote per item, submit feedback for moderation, and suggest new ideas that enter a staff review queue instead of publishing directly.

The archive owns an explicit route so it remains available even when another plugin or theme changes WordPress custom-post-type rewrite ordering.

The page renders on the server and progressively enhances inside standalone WordPress, the SnapWeb persistent shell, and FluentCommunity. Filters and votes do not require full-page navigation.

Inside FluentCommunity, Roadmap declares native archive and item-detail application routes. Cards open the complete item inside the FluentCommunity shell, where signed-in users can vote and submit moderated feedback without falling back to a generic WordPress post. The presentation inherits SnapWeb or FluentCommunity light/dark tokens and provides accessible focus, loading, empty, error, reduced-motion, and mobile states.

Version 0.3.0 displays updated dates for changelog context, enforces one vote atomically per account and item, throttles voting, feedback, and idea submissions, rejects duplicate feedback, and keeps public roadmap reads available to signed-out visitors without sending an empty REST nonce. Provider-neutral staff notifications make new ideas, feedback, and published workflow changes operationally visible without exposing customer text in email.

Version 0.3.1 adds explicit SnapWeb payloads for both archive and item-detail URLs, keeps embedded item templates inside the persistent shell, and renders WordPress-sanitized rich item content in the FluentCommunity reader. Status filters now announce the visible result count, vote controls expose pressed state and contextual labels, and rich text, media, and code remain responsive in light and dark hosts.

Version 0.3.2 refines the narrow-screen status scroller so its browser scrollbar cannot overlap the live result count while horizontal touch and keyboard access remain available.

Version 0.3.3 keeps the item-detail back link and workflow badge on separate lines at narrow FluentCommunity widths.

Version 0.3.4 makes /roadmap/ the canonical archive and /roadmap/{item}/ the canonical item structure even when the site's normal posts use a /blog/ prefix. Existing /blog/roadmap/ archive and item URLs permanently redirect to the clean structure after a one-time rewrite refresh during upgrade.

Version 0.3.5 adds safe, removable demo content covering every workflow state and makes feedback and idea length validation Unicode-aware.

Version 0.3.6 certifies moderated feedback and idea-submission mutations end to end and adds explicit loading, error, keyboard-focus, and post-vote accessibility states across standalone, SnapWeb, and FluentCommunity surfaces.

Was this documentation helpful?Your response helps us improve this page.

Secure account access

Welcome back

Sign in to continue without leaving this site.