Can I check a couple of things?
With the CMS, I'm only seeing 7 pre-made collection options right now. Is that correct? I.e there's no 'portfolio' or 'projects' or 'case studies' in there...
Client access to sites - what does this look like practically right now? Do we have any control over what a client sees, what they can or can't do? Do they just get an invite as if they were a team member? I tried to see what was available and it looks like that's how it works right now. This would mean the client could see the brief, the site map and wireframes, but in reality that might not be best? Are there plans for a more dedicated client view at some point, or have I missed something somewhere?
Benjamin L. 1. Yeah that's correct but I know the team is working on more collections. I would expect those to be released within the coming days. 2. The "viewer" only sees the sitemap, wireframes, and design tabs - not the prompts or briefs that created them. As for not wanting to show them the sitemap/wireframes - you could also publish the site and put it into something like usepastel.com for feedback outside of Relume.
Hi Matt J., I was more thinking of a way to invite a client once the site is live, and give them some simple editing abilities without access to everything. It's not so much for feedback, more for ongoing management. The client probably wouldn't want to create their own Relume workspace/account. It would be like the 'marketer' role in webflow. Does the Relume 'viewer' role have the ability to make changes to pages and CMS?
Benjamin L. no, but we have an editor role which is also free - which gives the user access to those edits. But gives them access to brief, sitemap, wireframes, and design. But I can see there could be a line drawn here - potentially a different kind of role.
Fair enough. Yeah.. for me, once a client site is launched, I'd typically look to set them up with a login so they can make simple edits without the need to have as much control as I might have. For example, access to the design view only, with the ability to add to cms collections, make page edits, and potentially interact with 1 or 2 agents and see site analytics
yeah makes sense
Benjamin L. good news - and I thought this was true but didn't want to say until I had evidence but it looks like a "content editor" role is already in the roadmap. So it was something the team had already planned for. I'll see where we are with that and go from there! 馃檶
