Community Roadmap, Bulletin Board & Feature Upvoting Guide

Print Life Software provides a live, transparent Community Roadmap and Bulletin Board that bridges print shop owners directly with our active development cycle. Whether discovering newly released features, tracking patched bug fixes, upvoting high-impact roadmap proposals from fellow shop owners, or viewing official development announcements and video tutorials, the bulletin board ensures our software evolves around real-world print shop needs.

---

1. Feature Scope & UI Navigation

The Community Roadmap and Bulletin Board are accessible from both the primary navigation sidebar and the global in-app Help Panel:

┌────────────────────────────────────────────────────────────────────────────────────────┐
│                                PRIMARY NAVIGATION PATHS                                │
├──────────────────────────┬─────────────────────────────┬───────────────────────────────┤
│ Full Bulletin Board Page │ /bulletin-board             │ Left Sidebar -> Community     │
│ In-App Help Panel        │ Top Header (?) Icon         │ Slide-Out Help -> Roadmap Tab │
│ Support Tickets Hub      │ /help-desk                  │ Header (?) -> My Tickets Tab  │
│ Public Support Portal    │ /support                    │ Public Help Desk Form         │
└──────────────────────────┴─────────────────────────────┴───────────────────────────────┘

Accessing the Community Roadmap (/bulletin-board)

• In the left navigation sidebar under Operations & Workflows, click Community Roadmap (/bulletin-board).
• When new platform releases, tutorial videos, or resolved bug reports are published, the Community Roadmap icon animates with a glowing notification badge until visited.

The In-App Help Drawer (? Header Icon)

• Click the ? icon in the top header action bar to slide open the Help Panel.
• Select the Roadmap tab to view trending community requests, cast upvotes, or check recent software updates without navigating away from your active quote or production screen.

---

2. Capabilities & Operational Boundaries

The Bulletin Board operates on an opt-in transparency model with automated freshness archiving:

┌────────────────────────────────────────────────────────────────────────┐
│                     COMMUNITY SUBMISSION PIPELINE                      │
│   Shop Ticket Submission  •  Feature Request  •  Tutorial Request      │
└───────────────────────────────────┬────────────────────────────────────┘
                                    │
                                    ▼
┌────────────────────────────────────────────────────────────────────────┐
│                      ADMIN MODERATION & OPT-IN                         │
│  Engineering review  •  Public visibility toggle  •  Status assignment │
└───────────────────────────────────┬────────────────────────────────────┘
                                    │
                                    ▼
┌────────────────────────────────────────────────────────────────────────┐
│                       COMMUNITY ROADMAP BOARD                          │
│   [Planned]            ──>            [Building]          ──> [Released]│
│   Community Upvoting                  Active Sprints          Live in App│
└───────────────────────────────────────────────────────────────────┬────┘
                                                                    │
                                                                    ▼
                                                 ┌─────────────────────────────────────┐
                                                 │       30-DAY FRESHNESS WINDOW       │
                                                 │ • Featured prominently for 30 days  │
                                                 │ • Automatically moves to historical │
                                                 │   archive after 30 days             │
                                                 └─────────────────────────────────────┘

Supported Capabilities

1. Democratic Community Upvoting: Shop owners and staff members can cast upvotes for proposed features and video tutorials. Items with high community demand are prioritized in upcoming bi-weekly development sprints.
2. Dynamic Multi-Type Lifecycle: Update cards adapt their visual badges and progress milestones based on ticket classification:
   • Feature Requests: Planned $\rightarrow$ Building $\rightarrow$ Released
   • Bug Patches: Reported $\rightarrow$ Fixing $\rightarrow$ Patched
   • Video Tutorials: Requested $\rightarrow$ Recording $\rightarrow$ Published
   • Platform Announcements: Posted $\rightarrow$ Updating $\rightarrow$ Archived
3. The 30-Day Freshness Window: To keep the board clean, exciting, and focused on current developments, completed updates stay in the active "Released & Published" feed for 30 calendar days before transitioning to the searchable historical archive.
4. Rich Media Integration: Announcements and tutorial cards feature embedded YouTube video walkthroughs, step-by-step markdown release notes, and direct links to documentation guides.

Operational Boundaries

• Privacy & Isolation by Default: User-submitted support tickets and bug reports submitted through the Help Sheet remain 100% private to your shop. A ticket is only displayed on the public board if our product team flags it as a community-wide feature or general interest topic.
• One Vote per Shop Account: Upvotes are tied to your shop organization, preventing ballot-stuffing and ensuring every business has an authentic voice in roadmap prioritization.

---

3. Step-by-Step SOP Workflows

SOP 1: Browsing and Filtering the Roadmap

1. Open the Community Roadmap (/bulletin-board) from the sidebar.
2. Use the category filter tabs at the top of the board:
   • All Updates: View all community proposals and releases chronologically.
   • Features: Discover upcoming capabilities, quoting tools, and automation enhancements.
   • Bug Patches: Track resolved shop floor issues and system stability improvements.
   • Tutorials & Videos: Browse newly published masterclasses and screen recording walkthroughs.
   • Announcements: Review major version upgrades, scheduled maintenance windows, and partner integrations.

---

SOP 2: Casting Upvotes for Proposed Features

1. Locate a feature or tutorial card in the Planned or Building columns.
2. Review the feature summary and user benefits.
3. Click the Upvote button (featuring the up-arrow icon).
4. The vote count increments immediately, signaling increased priority to our development team.
5. Note: Clicking the upvote button a second time removes your vote if your shop's priorities change.

---

SOP 3: Viewing Release Notes & Video Walkthroughs

1. On any card in the Released & Published column, click the card to expand details.
2. Read the formatted release notes, improvements, and relevant screen locations.
3. If the update includes a video guide, click Watch Tutorial to open the video walkthrough.
4. If the update links to our technical guides, click Read Documentation to open the full operating SOP in the Help Library.

---

SOP 4: Accessing Older Historical Releases

1. Navigate to the bottom of the Released & Published column.
2. Click Show older updates to expand the historical archive.
3. Browse past software versions, legacy patches, and archived announcements beyond the standard 30-day freshness window.

---

4. Business Logic, Formulas & Freshness Rules

30-Day Freshness Filter Formula

Items in the active "Released & Published" column are evaluated against a 30-day temporal threshold:

$$\Delta t = D_{\text{current}} - D_{\text{resolved}}$$

$$\text{Active in Feed} = \begin{cases} \text{TRUE} & \text{if } \Delta t \le 30\text{ days} \ \text{FALSE (Archive)} & \text{if } \Delta t > 30\text{ days} \end{cases}$$

Where:

• $D_{\text{current}}$ is today's calendar date.
• $D_{\text{resolved}}$ is the timestamp when engineering marked the item as Released, Patched, or Published.
• Items where $\Delta t > 30$ are safely preserved in the database and accessible via the Show older updates control.

---

Unseen Notification Glow Logic

The animated glow on the sidebar Community Roadmap link activates whenever new public items are published:

$$\text{Badge Glow} = \begin{cases} \text{ACTIVE} & \text{if } T_{\text{latest_update}} > T_{\text{last_viewed}} \ \text{INACTIVE} & \text{if } T_{\text{latest_update}} \le T_{\text{last_viewed}} \end{cases}$$

Upon landing on /bulletin-board or opening the Help Drawer Roadmap tab, the workspace records $T_{\text{last_viewed}} = \text{now()}$, immediately clearing the notification glow.

---

5. Troubleshooting & Diagnostic Matrix

Symptom / Question	Root Cause	Exact Remediation Step
A bug I reported is not visible on the Community Board	Tickets are private by default to protect shop confidentiality.	Only general platform bugs or community feature requests approved by our team appear on the public board. Your private tickets remain visible under Help Panel $\rightarrow$ My Tickets.
Upvote button is greyed out or unclickable	Your account does not have active staff privileges or you are not signed in.	Ensure you are logged into your shop workspace before voting.
I remember seeing a release announcement last month that is now gone	The announcement passed the 30-day freshness window.	Scroll to the bottom of the column and click Show older updates to view past announcements and releases.
The sidebar glow won't clear after visiting the page	Browser cache or session storage was blocked by an ad-blocker.	Refresh the page once or click the Roadmap tab inside the top header ? Help Drawer.

---

6. Frequently Asked Questions & Action Prompts

Q: How do I submit a feature request for community voting?

Answer: Click the ? Help icon in the top header, navigate to Support Tickets, and click New Ticket. Choose Feature Request or Tutorial Request as the classification. Our team reviews submissions daily and promotes high-impact proposals to the public Roadmap for community upvoting.

[How do I submit a feature request?](chat:How do I submit a feature request or support ticket?)

Q: Does upvoting a feature guarantee it will be built?

Answer: Upvotes strongly influence our active sprint planning. Items with significant shop demand are reviewed during our bi-weekly development cycles. When development begins, the card transitions from Planned to Building on the board.

[Show me the Community Roadmap](chat:Where is the Community Roadmap and Bulletin Board?)

Q: Can customers or competitors see our shop name on the Bulletin Board?

Answer: No. The Bulletin Board displays only the feature description, vote counts, and development milestones. Your shop's identity, private account details, and internal quotes are never shown publicly.

[Where do I find release announcements?](chat:Where are software updates and release announcements posted?)