I realized that my previous question was somewhat confusing and a bit hard to answer. I have thought about the situation and decided to delete that question and ask this one (which is better set out).
I am building a system where users have access to a
Profile page and an
Account Settings page.
The site administrator can create and edit custom fields in the system. For example, if I run a website about linux, then in additional to the default field of
Display name, I can add fields such as
Favorite linux distribution,
Years using favorite linux distribution,
Linux conferences attended, etc.
Each custom field can be marked as
private by the system administrator. For example, I could have these fields:
Favorite linux distribution (PUBLIC)
Years using favorite linux distribution (PUBLIC)
Linux conferences attended (PUBLIC)
Number of children (PRIVATE)
Relationship status (PRIVATE)
This is what the profile page looks like
Should there be seperate interfaces for editing public and private fields?
Here's a mockup that combines editing public and private fields into 1 interface:
Here's what it might look like if we use separate interfaces:
How should the administrator manage those fields if I have separate interfaces for editing public and private fields? Currently, I have a form editor for just managing public fields:
The editor is
what you see is what you get. If you order the fields a certain way, and edit each field to be a certain way, they are exactly what the user will see when they use the edit profile form.
Problem: If I have separate interfaces for editing public and private fields, I need have an interface that allows me to easily change a field from public to private and vice versa. I should be able to define seperate ordering for public and private fields.
I have thought about an interface like so:
- Users can drag fields within the scrolling list to reorder them.
- Users can drag fields between the scrolling lists to turn them into public or private fields.
The problem with the above interface is that is is much inferior to the
What you see is what you get interface I have outlined earlier. It is also more abstract and harder to visualize the fields.
Is there a better way to do this?
Finally, what should the private fields be called? The term
private fields by itself does not really tell the user how the site owner will use that information and merely states that it won't be visible to public.