Hey all,

How can I make it so that users have a "dashboard" but can also view others' profiles? I'm using webflow, airtable, zapier and memberstack. I feel like I'm overthinking this. 
Hey  Vitaliy Gnezdilov  

In a project which I shared within Slack community, I have static page working as a dashboard. It takes data from Memberstack, so that data is only available to member himself.

Then I setup a CMS item for each member and it is open to everyone. I do not set it as a member specific page in Memberstack, because this will make it accessible to that particular member only (as far as i know).
Aha, nice approach Igor. Ok so sounds like you have the private profile page that pulls private info from memberstack (not visible to anyone) that's only accessible to who is logged in.

Then you have a copy of this stuff as a webflow CMS item and have a dynamic cms page for each of these. Is that right?

I just came up with a different version of this:

In this version you use member-specific pages, but you don't specify the collection URL, making all member-specific pages accessible. Then in zapier, pass a /collection-url/ in front of the member page url.

Note — that's one sucky thing about it is that you have to manually specify your "collection-url/" directory before your member page url. Can't use collection id. Not a huge deal I guess. But a place where it could break.

You can still have a static page that pulls private memberstack data and options to act as your "dashboard" but call it "Settings" or "Profile" and do things like change password, etc.

What do you think?

I might be understanding wrong, but it looks much the same solution. 

So in my solution I don't have the same content on a static dashboard page and on a public profile.

In my case, dashboard shows information about membership status, some news, notifications. Also there are special links for mentoring session reservation, to community discussion and so on. You can also change password from there.
So the page is pretty much the same for all members and I only change data of membership or notification source based on MS data.

But for public profiles I show kind of info about the member. So you can write about yourself, share your contacts, your projects. The information supposed to be apealing to others.

I really don't see a need to make a member specific page here. To be honest, I have never used that feature yet.

I just tie up MS profile with Public CMS Profile by storing each other's id and it works perfectly.

Still, I was thinking of putting dashboard and profile on the same page and show or hide particularr parts based on wether it is a profile owner who looks at the page right now. It would make things looks more like it is done in facebook or twitter
Thanks for all the detail. Same effect, but different approaches. Learning so much here.

I am interested a lot in your last paragraph. What do you think though, if anything, about all the member info and options showing up for a split second when page loads for the first time before it disappears when memberstack realizes the visitor isn't a current member?


You can make a loading screen for that to hide irrelevant content. So it is going to be a div block with position static and 100 VW and 100 VH to hide everything.
Then you just set its diplay setting to hidden when Memberstack initializes.
You can also not hide the content but completely remove it with .remove action of JQuery.
Vitaliy Gnezdilov  Thats pretty simple actually. Just google somthing like "JQuery remove element" and you will have a bunch of pages with a code already written. Copy and paste. And don't forget to change element's classes/ids to yours))
Igor Voroshilov So it would not load in the element? How different would it look from simply setting display to none?

Do you know how to do seamless page transitions in webflow? I haven't seen any simple examples. Just like a fade-in/fade-out would be really nice. Especially if it could be tied in with memberstack initializing.
Vitaliy Gnezdilov Element will be loaded, but then it will be removed. Visually it is the same as setting display to hidden, but the element will not appear in chrome inspector as well. So I consider it being a bit more secured.
It is fine to just make the display none.

Talking about page transitions, I haven't done anything like that. You may play with Webflow animation with a page trigger on page load, but not sure how it would work. The thing is Webflow is not SPA, so every page in loaded as a whole everytime. Not sure how to make those transitions.
Igor Voroshilov  Awesome, thanks! I'm going to go the jquery route. Still haven't gotten to the page transitions part, so if anyone has any good inspiration examples, post em!

Post a comment

Log in