How to Add a Changelog, Roadmap & Knowledge Base to Webflow

Webflow gives designers pixel-level control of a marketing site, but it ships with no changelog, no public roadmap, and no knowledge base. SaaS teams on Webflow need all three to show velocity, gather feedback, and deflect support tickets. The fastest fix is a single Embed Element that pastes a hosted ProductLift widget into any Webflow page in under five minutes.

Why Webflow customers need this

SaaS companies need to show active development. Prospects checking your site want to see that your product is evolving. Existing users want to know what shipped and when. 3.5 million designers and developers build on Webflow, the company raised at a $4 billion valuation in 2022, and brands like Dell, Vice, Discord, and Lattice run their marketing sites on it (per Webflow's customer page). Typical Webflow sites score in the 90s on Lighthouse, which is why founders pick it for landing pages, and why any changelog you bolt on cannot drag those numbers down.

Webflow has no changelog feature. The page at webflow.com/updates is Webflow's own product log for the Webflow platform. You cannot use it for your SaaS product. If you search the Webflow Marketplace for a changelog component, you will find nothing.

Without a changelog, your options are limited: manually write blog posts for every release, or hope users notice what changed. Neither scales. A dedicated changelog gives you categorized entries, email notifications, user reactions, and a permanent record of everything you ship.

3.5 million designers and developers build on Webflow. A changelog turns that visibility into a velocity story for your marketing site, since Webflow ships none of these features natively. (Webflow About page)

For a deeper look at what makes a good changelog, check out 15 best changelog examples and our guide on how to write release notes that users actually read.

How do you add a changelog to a Webflow site?

The fastest way is to drop a Webflow Embed Element onto a /changelog page and paste the ProductLift widget snippet. Here is how to set it up with ProductLift.

Step 1: Create your changelog

Sign up at ProductLift and create your first changelog. Add a few entries with categories (New Feature, Improvement, Bug Fix), screenshots, and descriptions. This takes about five minutes.

Step 2: Choose your integration method

Webflow gives you four practical ways to surface external content. Each fits a different team setup. Compare before picking:

A few notes on each row.

Embed Element on a dedicated page. Most common. Create a /changelog page, drag an Embed element onto your canvas, and paste the ProductLift iframe or JavaScript snippet. The changelog renders inside your Webflow layout with full responsive behavior. Embed elements support HTML, CSS, and JavaScript, capped at 10,000 characters.

CMS Collection page. If updates already live in a Webflow CMS collection, drop an Embed Element into the collection template so the live ProductLift feed sits alongside hand-curated entries. Useful during a migration window.

Custom Subdomain. Point changelog.yoursite.com to your ProductLift hosted changelog. Add a link in your Webflow nav. Zero code changes to your Webflow project, which matters when the designer is offline and engineering wants to ship.

Site-wide Custom Code. For a "What's New" badge on every page, paste the JavaScript widget in Project Settings under "Before </body> tag". Visitors see a bell icon that expands to show recent updates without leaving the page.

Try it yourself: Start your free plan and drop a changelog into your Webflow site with one Embed Element. No credit card required.

Step 3: Match your Webflow design

ProductLift offers full CSS customization. You can override colors, fonts, spacing, and borders to match your Webflow design system exactly. Webflow designers can add custom CSS in the Embed element or in the page's custom code section. The result looks like a native part of your site, not a third-party widget.

Step 4: Publish and distribute

Hit publish in Webflow. Your changelog for Webflow is live. Users can subscribe to email notifications, react to entries, and filter by category.

Why Your Webflow Site Needs a Public Roadmap

A public roadmap answers "What are you building next?" before the question reaches your inbox. It builds trust with prospects evaluating your product and keeps existing users engaged.

Here is an interesting comparison: Webflow itself uses Aha! for their own product wishlist and roadmap at $59 per user per month. ProductLift gives you the same functionality for $19/month total, not per user.

A static roadmap page designed in Webflow is just columns and cards. There is no voting, no real-time status updates, and no way for users to participate. When you move a feature from "Planned" to "Shipped," you have to manually edit the page. An interactive roadmap handles all of this automatically.

For a complete overview of why public roadmaps work, read our complete guide to public roadmaps.

How do you add a public roadmap to a Webflow site?

You create a /roadmap page in Webflow, drop in an Embed Element, and paste the ProductLift roadmap snippet. The process is similar to the changelog setup.

1. Create your roadmap in ProductLift with categories and items
2. Create a /roadmap page in your Webflow project
3. Drag an Embed element onto the page and paste the embed code
4. Link to /roadmap from your main navigation
5. Publish your Webflow site

Visitors can now vote on features, leave comments, and subscribe to status updates. When you move an item from "Planned" to "In Progress" to "Shipped," every voter gets notified automatically. This closes the feedback loop without manual follow-up.

ProductLift includes RICE, ICE, MoSCoW, and Impact-Effort scoring frameworks so you can prioritize with data, not guesswork. Connect Stripe to see which features your highest revenue customers care about most.

Your full roadmap for Webflow setup takes under ten minutes.

Why Your Webflow Site Needs a Knowledge Base

Users have questions. Answering them one at a time does not scale. A knowledge base lets users help themselves, and every article you write is a support ticket you never have to answer.

Webflow CMS is great for blog posts, but it was not designed for structured documentation. The limitations become clear as your docs grow:

• Flat collections. Webflow CMS has one level of categorization. Documentation needs nested categories like Getting Started > Account Setup > SSO Configuration.
• No cross-article search. Users cannot search across all your help articles from a single search bar without custom workarounds.
• No analytics. You cannot see which searches return no results, which articles users leave quickly, or which topics need more coverage.

A single support ticket costs between $15 and $50 to resolve. A well-organized knowledge base can deflect 30% to 50% of incoming support requests. For a SaaS company handling 200 support tickets per month, that translates to thousands in savings.

For a step-by-step guide on planning and writing help articles, see how to create a knowledge base.

How do you add a knowledge base to a Webflow site?

The cleanest setup is to point a docs.yoursite.com subdomain at a hosted ProductLift knowledge base, or embed it on a /help page using a Webflow Embed Element. You have two main approaches.

Custom subdomain (recommended). Point docs.yoursite.com or help.yoursite.com to your ProductLift knowledge base. Add a "Help Center" or "Docs" link in your Webflow navigation. Users land on a full knowledge base with categories, search, and structured navigation, all branded to match your Webflow design. Your Webflow project stays completely untouched.

Embed on a Webflow page. Create a /help page in your Webflow project, add an Embed element, and paste the ProductLift embed code. The knowledge base renders inside your Webflow layout with your navigation, header, and footer intact. Users stay on your site while browsing documentation.

Both approaches include instant search, nested categories, analytics on search queries, and support for hundreds of articles without performance issues.

67% of customers prefer self-service over speaking to a company representative. A searchable knowledge base captures most of those questions before they become tickets. (Zendesk CX Trends Report 2024)

Your full knowledge base for Webflow setup guide covers all the details.

How do feedback, roadmap, and changelog connect on Webflow?

Most SaaS startups on Webflow have a split stack. The marketing site is in Webflow, the product is a React or Next.js app on a different domain, and the cofounders are usually a designer-engineer pair. The pain point: feedback collected in the product app rarely makes it back to the marketing site, and the marketing site rarely shows the velocity that prospects want to see.

ProductLift's Journey Model bridges that split:

1. A user submits feedback inside the product app, on a feedback board embedded next to the actual feature they want changed
2. The same post surfaces on the public roadmap embedded in your Webflow marketing site, where prospects see live demand signals before they even sign up
3. The cofounder ships using Linear or whatever issue tracker the engineering side prefers, and updates the post status
4. When the release goes out, the post becomes a changelog entry. Every voter inside the product app gets notified automatically, and the same entry renders inside the Webflow marketing site embed as fresh proof of velocity
5. AI generates a knowledge base article from the shipped entry, ready to embed back in either property

One post, one continuous thread, two surfaces (product app and Webflow marketing site) sharing the same data. Designer-led startups stop maintaining a "what we shipped" page in Webflow CMS by hand, and engineers stop pasting changelog text into a separate marketing tool. The Webflow site stays as the polished marketing surface, and ProductLift is the data layer that keeps it honest.

How much does a Webflow changelog and roadmap cost?

ProductLift charges a flat $19 per month for the full stack of changelog, roadmap, and knowledge base, billed annually with unlimited end-users. The standard playbook for a Webflow-led startup is to evaluate Aha! at $59 per user per month or Productboard at roughly $20 per maker per seat. Aha! is built for enterprise PMs and prices accordingly: a designer cofounder, an engineer cofounder, and a part-time PM hits $177/month before you have shipped anything. Productboard's Maker seat tier escalates the moment you bring in a third contributor, and neither tool gives you a public-facing roadmap or changelog that embeds cleanly into a Webflow site without engineering work.

ProductLift is a flat $19/month (billed annually) with unlimited end-users and voters. The two cofounders share a single workspace, every plan includes feedback boards, roadmap, changelog, knowledge base, AI features, prioritization frameworks, and Stripe integration, and the embed lives natively inside Webflow Embed elements with no developer required. For a designer-led startup that cares about brand consistency and runway, the difference between $19/mo flat and $177/mo seat-based across a 24-month runway is meaningful: roughly $3,800 of cash that funds another sprint instead of disappearing into seat licensing.

Ready to plug it in? Create a free plan and connect ProductLift to your Webflow site. White-label and 27 languages are built in.

FAQ

Does it work with Webflow CMS?

Yes. You can place Embed elements on CMS collection template pages. The changelog, roadmap, or knowledge base widget will appear alongside your blog posts or resource pages. You can use Webflow's conditional visibility to show embeds only on specific collection items.

Can I match my Webflow design?

Fully. ProductLift offers dashboard-level customization for colors, fonts, and layout. For pixel-level control, add custom CSS overrides in the Embed element or in Webflow's custom code section. You can match your typography scale, color variables, spacing system, and border styles exactly.

Will it affect my Webflow site's performance?

No. ProductLift is hosted externally. The embed code loads asynchronously, meaning your Webflow page content renders first and the widget loads independently afterward. There is no impact on your Webflow hosting bandwidth, asset limits, or page speed scores.

Can I use it on client projects?

Yes. Webflow agencies can embed ProductLift on client sites to document deployments, collect feature requests, and share project progress. Each client gets their own feedback board, roadmap, and changelog. The embed works on any Webflow plan.

How long does setup take?

Under ten minutes for each feature. Sign up, configure your board, grab the embed code, paste it into a Webflow Embed element, and publish. The site-wide notification widget takes even less time since you paste one snippet in Project Settings.

Will I hit Webflow's Embed Element 10,000 character limit?

No. The ProductLift embed snippet fits well under 1,000 characters, even with custom CSS overrides. The actual content (entries, comments, votes) loads asynchronously from ProductLift's servers, so the character cap never becomes a constraint. If you need extensive custom CSS, move it into the page-level Custom Code section and keep the Embed Element itself minimal.

Can I try it before committing?

ProductLift offers a free plan with access to all features. No credit card required. Set up your changelog, roadmap, and knowledge base, embed them on your Webflow site, and see how they look before choosing a paid plan.