[Wishlist] Enable public profiles Planned

Post author
Memberstack Team
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.

Comments

10 comments

  • Comment author
    Duncan Hamra
    • Official comment

    We plan to tackle this problem in 2023. Please upvote or comment to receive notifications. 

  • Comment author
    Duncan Hamra

    Robby Branham "Access members data via JavaScript across members - useful for displaying progress/leadership boards. Possibly a more robust database for members, rather than meta data?"

    Does this post explain your situation well? Anything we're missing?

    https://forum.memberstack.io/t/is-it-possible-to-have-different-types-of-members-on-the-same-instance/1078/4

    0
  • Comment author
    Chuck Lapointe

    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.

    0
  • Comment author
    Duncan Hamra

    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. 

    0
  • Comment author
    Chuck Lapointe

    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?

    1
  • Comment author
    Duncan Hamra

    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. 

    1
  • Comment author
    Duncan Hamra

    Exciting update! Julian Galluzzo kindly documented a solution for Public profiles here. You'll find a tutorial in the project as well. 

    https://webflow.grsm.io/webflow-is-awesome?page=made-in-webflow/website/public-member-profiles

    0
  • Comment author
    Alice Glasser

    Hi! Is it possible to do a simplified version of this (i.e. only name and contact info) without using Webflow CMS?

    We have a lot of members and I've read that Webflow CMS struggles with more than 10k items.

    1
  • Comment author
    Duncan Hamra

    Hey Alice 👋 I would not recommend it at this time. Unless you can find a way to store that member data in another database and pull the data into the Webflow UI. I'm worried you'd run into some blockers. 

    0
  • Comment author
    Alice Glasser

    Thank you, Duncan! That's what I told the client and I'm glad I can say the expert officials agree with that diagnosis :D

    1

Please sign in to leave a comment.