Publish Your Roadmaps & Voting Panel
Once your project is configured, it's time to put it in front of your community. PathPro gives you multiple ways to publish your roadmap, feature voting panel, and other project views directly on your own site — via your project URL, an embed code, or a custom domain.
How PathPro Displays Content by Role
PathPro uses a hybrid display model that adapts what each visitor sees based on their role. Every project has a single URL, but the experience changes depending on who's viewing it:
- Community members (and logged-out visitors on public projects) see the public view — a clean, consumer-facing interface showing your roadmap, feature voting page, release notes, and submission form. There are no admin controls, settings panels, or internal metadata visible. This is what your users interact with.
- Admins and team members who are logged in see the management view — the same content, but with additional controls layered on top. They can edit tasks inline, change statuses, triage submissions, manage team members, access settings, and use all the tools covered in this knowledge base.
This means there's no separate "admin site" and "public site" — it's one unified experience. When you share your project URL with your community, they see exactly the public-facing version. When you log in with your admin account at that same URL, you see the full management interface.
This hybrid approach means you can preview exactly what your community sees by logging out or opening an incognito window. What you see as an admin is a superset of the public view.
Your Project URL
Every PathPro project gets a unique subdomain under app.pathpro.co as soon as it's created. The URL is based on the slug you chose during project setup:
- If your slug is
acme-saas, your project lives atacme-saas.app.pathpro.co - Your roadmap is at
acme-saas.app.pathpro.co/roadmap - Feature voting is at
acme-saas.app.pathpro.co/features - Release notes are at
acme-saas.app.pathpro.co/release-notes
This URL is fully functional from the moment you create your project. You can share it immediately — anyone who visits will see the public view of whatever content you've added so far. Community members can register, vote, submit feedback, and create support tickets all from this URL.
The most straightforward way to publish your project is simply to link to your project URL from your website, app, or email communications. Add a "Roadmap" or "Vote on Features" link in your product's navigation, footer, or help menu that points to the relevant page on your PathPro subdomain.
Embedding on Your Site
If you want to display your PathPro roadmap or voting panel directly inside your own website — without sending visitors to a separate URL — you can use an iframe embed. This keeps your community on your domain while showing live PathPro content.
To embed your project, add an iframe to any page on your site:
<iframe
src="https://acme-saas.app.pathpro.co/features"
width="100%"
height="800"
frameborder="0"
style="border: none; border-radius: 8px;"
title="Feature Voting"
></iframe>You can embed any page of your project — the roadmap, feature voting panel, release notes, or submissions view. Simply change the path in the src attribute:
/roadmap— Your task groups and roadmap view/features— The feature voting panel/release-notes— Your public changelog
Tips for Embedding
- Set an appropriate height — A height of 700–900px works well for most views. The voting panel and roadmap both benefit from more vertical space.
- Use 100% width — This lets the embed respond to your site's layout and container width.
- Consider the container — Place the iframe inside a well-padded container on your site. PathPro's public view is designed to look clean when embedded.
- Authentication still works — Community members who are logged into PathPro can still vote and interact within the embed. If they aren't logged in, they'll see a registration prompt when they try to vote.
Using Your Project's Custom Header
PathPro's Header & Design settings let you customize the navigation tabs your community sees at the top of your project. This is a lightweight way to make your PathPro project feel like a native part of your product without any embedding.
In the Header settings, you can:
- Rename tabs — Change "Roadmap" to "Product Plan", or "Feature Voting" to "Vote on Features" to match your product's language.
- Add custom links — Add menu links that point back to your main site, documentation, or support portal. This makes navigation between your product and your PathPro project seamless.
- Upload your logo — Replace the PathPro default with your own brand logo so the project header matches your product.
- Set your accent color — Match the project's accent color to your brand, ensuring visual consistency.
When combined, these settings make your PathPro project page look and feel like a branded section of your product. A visitor clicking "Roadmap" in your product's navigation arrives at a page that shares the same logo, color palette, and language — even though it's hosted on PathPro's infrastructure.
Publishing on a Custom Domain
For the most seamless experience, you can connect a custom domain to your PathPro project (available on plans that include the custom domain feature). Instead of acme-saas.app.pathpro.co, your community visits something like feedback.acmeapp.com or roadmap.yourproduct.com.
With a custom domain:
- Your project URL matches your brand entirely — no PathPro branding in the address bar.
- All the public views (roadmap, voting, release notes) are served from your domain.
- Combined with header customization and white-label options, the experience is fully branded.
Setting up a custom domain involves adding a CNAME record in your DNS provider that points to cname.app.pathpro.co, then verifying the domain in your PathPro project settings. For the full setup guide, see Custom Domains & Branding.
feedback.theirapp.com as a custom domain, uploaded their logo, matched their accent color, and renamed the tabs. Their users interact with the roadmap and voting page daily — most don't even realize it's powered by PathPro.Choosing the Right Approach
Each publishing method suits different situations. Here's a quick comparison:
| Method | Best For | Effort | Branding |
|---|---|---|---|
| Direct link to subdomain | Quick launch, email campaigns, social sharing | None — works immediately | PathPro subdomain visible in URL |
| Iframe embed | Showing roadmap/voting inside your site | One line of HTML | Your site wraps the content |
| Header customization | Making the project page feel branded | 5 minutes in settings | Custom logo, colors, tab names |
| Custom domain | Fully branded experience | DNS setup + verification | Fully your brand (paid plans) |
You can also combine these approaches. For example, use a custom domain with header customization for the main experience, and embed specific views (like the voting panel) on other pages of your marketing site.