[Wishlist] Enable public profiles Planned
- 6 comments
1) The problem → I have a project where some member data needs to be displayed publicly. However, because I can't access more than one member's data via Memberstack directly I have to sync this data with another tool via webhooks, zapier, etc. My usecase requires some member data to be accessible to anyone, and some data requires permission granted via a membership plan. Each member will have their own page with just their data, and some pages will have lists of multiple members who's data meets certain conditions and may be sorted.
2) Why is this important → My use case depends on it, and I have to find a million work arounds to make it happen. Managing images is particularly problematic.
3) What will happen if this goes unsolved → I'll need to keep using third party tools to sync my data. Or I'll try again with a custom app or another tool.
4) Possible solutions → Make it possible to flag some member data types as "public" so it's accessible in the front-end. This would allow builders to render whatever UI they need in the front-end. Create attributes and methods for populating filtered/conditional data to a list.
We plan to tackle this problem in 2023. Please upvote or comment to receive notifications.
Does this post explain your situation well? Anything we're missing?
Hi Duncan Hamra
How far off are we for this?
Is it a month or two away or something that would be released in Q3 / Q4? We're planning to launch a similar feature across our communities.
Hey Chuck Lapointe 👋
We're still in the early design phase for this. So it's hard to say. That said, I do know we'll start with a simple first solution and then add complexity. For example, we'll probably start with a suuuper simple list of members in a directory. No individual pages or anything out the gate.
Got it, so focusing more on the "overall" members rather than individuals.
Would you recommend we build this ourselves for public profiles using our database connection instead if we need to be live in a few months?
Yup, exactly. At least to start. We're debating between building tooling to enable public profiles with data stored in Webflow or public profiles with data stored in Memberstack.
If you need something in a few months, I would recommend going the custom route. + will give you more flexibility to customize quickly as you learn from customer.
Please sign in to leave a comment.