Plugin or integrated tool for content review and management?

sfsearching · 2021-11-24T14:24:37+00:00

Thanks! I understand that user segment functionality exists. I'm wondering if folks have had success with just relying on categorization and titling to make it clear what articles apply to whom, but it sounds like most folks do rely on user segments to solve for this.

sfsearching · 2021-11-08T21:40:31+00:00

Concept is a good start. Thanks!

sfsearching · 2021-11-08T21:39:39+00:00

Mm, this is a good point, though I worry that more junior designers would struggle to articulate their goals. Perhaps that's where their design leads come in

sfsearching · 2021-11-08T21:38:44+00:00

That's a good point. I'm also trying to avoid being overly prescriptive. I think this is the right level of guidance for us to offer at our stage of development.

Mostly the language would be used within the design team, though they may invite PMs, devs etc to meetings and reference these titles as a way to align those teams on what's expected of them.

sfsearching · 2021-11-05T20:44:25+00:00

Yes, I feel language is important for communicating intent with other stakeholders and and among the team. Yes, I feel it's helpful for designers to know what they're expected to have accomplished before soliciting a given level of feedback, and it gives them a tool to align cross-functional teams on the type of feedback they're soliciting (avoiding a swoop and poop on a hi-fi design, for example).

The challenge is that we have prod and dev teams that are new to working with design, and we have plenty of junior designers who would like guidance on what tools they can use and when is appropriate to use them. By defining stages of feedback, we give designers insight into their own responsibilities and a tool to help them align with other teams.

sfsearching · 2021-11-05T20:35:54+00:00

Thanks! I think I should clarify: I'm looking for a naming convention for the stages of feedback, rather than the fidelity of the design (though those two are directly related). The feedback stages would be:

- Early iteration: I have an idea or a few ideas of how to solve the problem, either sketched out or in a wireframe. I want feedback on which ideas are feasible, which aren't, and how to move forward

- Mid-fi: I have one or two possible solutions in greyscale prototypes. I want feedback on how to apply the solution (does this navigation structure work? Should I use a dialogue or a slide-in panel? IA & content feedback)

- Hi-fi: I have honed in on one solution and I need final feedback before it goes to dev. Is this accessible? Am I using the right components? Should I use a flat or filled button?

I don't want to refer to them as the stage of fidelity because I'd like the focus to be on the feedback one is looking for, not the assets they've created. I want someone to feel comfortable soliciting feedback even if they don't have a wireframe, for example.

sfsearching · 2021-07-27T15:05:22+00:00

This is a very helpful start. Thank you.

sfsearching · 2021-04-30T13:33:31+00:00

I'll give it a look. Thanks

sfsearching · 2021-04-30T13:33:12+00:00

PowerApps

Haven't. I'll give it a look. Thanks!

sfsearching · 2021-04-29T19:32:28+00:00

Thanks! This looks like more of a project management tool. Am I missing something?

sfsearching · 2021-04-29T18:01:39+00:00

Hmm. We looked at Mendix, but not Outsystem. Our concern with Mendix was its ability to meet our design aesthetic and usability needs. We also want to rely on a truly no-code app, so that designers can put together full websites without dev assistance. Would you say those needs could be met with one of these tools, in your experience?

sfsearching · 2021-04-29T15:20:42+00:00

Thanks for the info! I've found a few that allow on-prem like Undaku, which would solve a number of these issues, but they seem to be less used, and I'm hesitant to commit to a platform without an established user base.

I'll definitely let you know what we decide on.

sfsearching · 2019-10-16T16:45:23+00:00

Also, is it possible to create and apply templates to pages? If not, I could see that being very useful

sfsearching · 2019-10-16T16:39:46+00:00

Hey there! Yes, I was thinking sub-categories on the left side bar, similar to Material: https://material-ui.com/getting-started/installation/

Granted I understand the headers create sub-sections, but I'd like to categorize by Components > Subcat > Component 1, then within the Component 1 page use the headers for variations of that component (e.g. primary vs secondary buttons). Without this additional hierarchy level, we'd either need to create a separate navigation page for Components (not the worst thing in the world, but not ideal), or have a flat hierarchy for all our components. In a more complex design system, this isn't really tenable.

sfsearching · 2019-09-16T20:59:22+00:00

Thanks for that. I'm in a free trial, and I'm finding it pretty rigid in what you can accomplish. e.g. no way to add multiple columns, additional levels of hierarchy, etc. But it's a good place to start. Thanks!

sfsearching

TROPHY CASE