Quick Start Guide

The essential 5-step workflow to get your PathPro project up and running in minutes. Follow these steps in order and you'll have a fully functional public roadmap, feature voting page, and release notes feed ready for your community.

Step 1: Create Your Project

Everything in PathPro starts with a project. If you haven't created one yet, head to your dashboard and click "New Project". You'll choose a name, URL slug, and visibility setting. The entire process takes under a minute.

Your project is live immediately after creation at your-slug.app.pathpro.co. You can share this link right away, though you'll want to add some content first.

For a detailed walkthrough of every option in the creation form, see Creating Your First Project.

Step 2: Add Task Groups

Task groups are the columns or sections that organize your public roadmap. Think of them as stages in your development pipeline -- common examples include "Planned", "In Progress", and "Complete", but you can name them anything that fits your workflow.

To create a task group, navigate to your project's roadmap page and click "Add Task Group". Give it a name and optionally a description that explains what this stage represents to your community.

Each task group has a publication status:

• Published — Visible on your public roadmap. Community members can see all tasks inside this group.
• Draft — Hidden from the public view. Use this to prepare upcoming work before making it visible.
• Archived — Removed from the active roadmap but preserved for historical reference. Useful for past milestones you no longer want front-and-center.

Once your task groups are in place, add tasks to each one. Tasks represent individual items on your roadmap -- features you're building, bugs you're fixing, or improvements you're planning. Each task can have a title, description, and status that your community can follow.

Step 3: Add Features for Voting

The feature voting page is where your community tells you what matters most to them. Unlike roadmap tasks (which represent your committed plan), features on the voting page are ideas and requests that the community can upvote to signal demand.

To add a feature, go to your project's voting page and click "Add Feature". Fill in the following:

• Title — A clear, concise name for the feature (e.g., "Dark mode support" or "Slack integration").
• Type — Categorize the feature to help your community filter and browse. Common types include Feature Request, Improvement, Bug Fix, and Integration.
• Description — Provide enough context so voters understand what the feature would do and why it's being considered. Markdown formatting is supported.
• Status — Set the initial status such as "Under Review", "Planned", or "In Progress" to give voters context on where things stand.

Community members can upvote features and leave comments explaining their use case. This gives you quantifiable data to help prioritize your roadmap decisions.

Step 4: Invite Your Community

With your roadmap and voting page populated, it's time to bring people in. Share your project's subdomain link (your-slug.app.pathpro.co) with your user base through any channel -- email newsletters, in-app announcements, social media, or your website.

Community members can register in several ways:

• Email registration — Standard sign-up with email and password.
• Google login — One-click sign-in via Google account.
• Facebook login — One-click sign-in via Facebook account.

Once registered, community members can vote on features, submit their own feedback and feature requests (if submissions are enabled), comment on tasks and features, and follow items to get notified of updates.

If your project is set to Private, only users you've explicitly invited will be able to access it. For Public projects, anyone with the link can browse your roadmap and voting page -- they just need to register to interact.

Step 5: Publish Release Notes

Release notes close the feedback loop with your community. When you ship something, announce it so the people who voted for it know their voice was heard.

To create a release note, navigate to the Release Notes section of your project and click "New Release Note". Each release note includes:

• Title — A headline for the release (e.g., "February 2026 Update" or "v2.4 -- Dark Mode & API Improvements").
• Content — A rich-text description of what was shipped, changed, or fixed. Write for your users, not your engineers.
• Linked tasks — Connect completed roadmap tasks to this release note so everything ties together. Community members who followed those tasks will see the update.

Published release notes appear on your project's release notes page in chronological order. Subscribers receive notifications when a new release note goes live, keeping your community informed and engaged without requiring them to check back manually.