How to structure Webflow URL/Memberstack navigation for gated content while keeping it low-code? Answered
Hello All - another question about memberstack/webflow community core navigation with members, gated plans and access. Currently our devs have built our foundation using this method but I wanted to see what are the best practices to have as much low-code/no-code as possible and a solid bug free foundation to expand our communities and members access. Here is the solution the current developer built ( Dev: We're using a single page for all membership plans for courses, upgrades, and certificates, that is why we have three separate navigation bars on these pages. Each nav bar is customized to display content relevant to the member's specific plan. Since we can't link different plan-specific content to a single navigation item, separate nav bars are necessary. But apart from this all other urls have single navbar.) I would love any community feedback on what should have been done for best practices for members access, gated content in our dashboard.
Comments
11 comments
Hey Chad, the current setup would work as well. Just curious as to whether you could have one navigation bar with multiple items which have the necessary gated content attribute or is the different navigation bar for each type of plan necessary? Having one navigation bar with dynamic items would probably make it easier for you to manage in long run.
HI A J yes I 100% agree, assuming more custom coding will lead to more bugs/errors in the future. What is the best way to have a dynamic left side navigation bar. Aman Devchandani FYI
I personally have implemented this via gated content attributes for navigation whenever required for clients and have kept the navigation to be a single component so its easily manageable. But it also depends on the site that you are building and if you want it to be separate because of some reason like having too many buttons in the same navigation is confusing to manage in the back-end etc. Users will still be able to see the relevant information based on their access level, it becomes a choice of managing at that aspect. And also are you managing users via Webflow CMS + memberstack or is it just via Memberstack?
Great points - we currently have 3 plans as you see on the screenshot. We have both Eng/Spanish dashboards. How its build now is we will have 3 different URLs and left side navigation based on the plan the user is on. This leaves a lot of room for error with seamless sync of information (plan/gated content) between the Eng/Spanish dashboards. (Spanish being primary language). So this could lead to 18 different pages with 6 member based pages in dashboard. 36 pages if you are counting spanish
Ahh okay got it. Since there are many buttons in this use-case, it indeed is a choice made for managing it better on the back-end by having different navbars. Again this is a workable solution, just was wondering if having many buttons indeed was the cause of opting for different nav-bars.
Ok so the current way its being built with unique URLs Eng/Spanish is the best course moving forward?
In case, your site won't benefit by localization features like using Weglot, and having separate pages based on languages seems fit and feasible for your use-case, yes the way you have set the navigation works. Having custom code to populate the links dynamically would have been possible, but personally I won't risk it when it comes to navigation in the site.
Thanks A J much help
Will my memberstack course be in a subdomain or pathname with my webflow site?
course.example.com vs example.com/course
Pathnames will be the most simple if you're okay with it
You have to set the domain or subdomain in your Memberstack configuration to enable from which environment your users will be created.
As seen in here: https://docs.memberstack.com/hc/en-us/articles/7595262385819-Managing-Test-Mode-and-Live-Mode-Domains
Memberstack doesn't host your page course content, it only handles members data. Content is hosted in Webflow, so if you wanna set access to it from a domain or a subdomain will depend on your DNS settings https://help.webflow.com/hc/en-us/articles/33961334343827-Connect-a-custom-domain-overview
Please sign in to leave a comment.