2

I have three text sections where the first is available to all, the second is available to a group, and the third is available to a subgroup.

The back-end user needs to be able to edit each, and understands that each section represents something different. A front-end user, however, will see each of the three as one continuous text block, and should not know that there are three sections, and should think there is only one.

How should the back-end user be able to edit (or add to if initially empty) the three text sections? Should the three sections take up screen space on the back-end if they are initially empty? How should the back-end user know that the first is for all, second for group, and third for sub-group?

mockup

download bmml source – Wireframes created with Balsamiq Mockups

1

The final text may be read as a whole by the subgroup users; this should be clearly understandable. Therefore, I would display a the final resulting text in continuity. Preferably you could use inline editing, but you can also use three textareas next to the end-result.

Check this:

enter image description here

Of course, you should use a proper label for blocks 1,2,3.

Also, if you have several kinds of groups and subgroups, this solution would have to be updated to allow choices between alternative texts.

  • Your solution uses a bit of real estate, but do like it. If a block was initially empty, how should it work? – user1032531 Mar 21 '16 at 12:35
  • With an empty block, you can just use placeholders (with a lighter color). You can figure many solutions to save space (I don't know how is the rest of your wireframe). For instance, you can replace the help-labels by help-icons, or just remove them and add a contextual help when editing. – Yako Mar 21 '16 at 15:13
2

Yes, the back end should have three separated sections to edit, with correct labeling for each one.

Something like this:

mockup

download bmml source – Wireframes created with Balsamiq Mockups

  • Should the textarea be open, or should there be an edit/add call to action next to each? Inline editing? One or 3 save buttons? Should each take up the same amount of space regardless of content? PS. I meant to add requirements to letting user know which one was all/group/etc, but you did so in your answer :) – user1032531 Mar 19 '16 at 17:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.