Hi Pragun,
The mockups look good. I noticed that editing actions are put first in comparison to content. Since Wikidata is already quite dense in terms of data (which is expected), adding actions for each piece of data may crowd the UI too much.
I explored some ideas to reduce the density of actions and content:
- Display information first and provide editing actions in a separate detail view. In the current mockup you can edit a statement such as "main type", modify its value and add more sources (all from the top-level view). Alternatively, in a simplified top-level view you can just show the information, and allow edit actions once the user accesses to it.
- Allow for richer content. The current format is text based. Statements can be represented in a way that allow for images to be used.
I created a couple of mockups to illustrate the ideas:
Note that:
- The description of the item is grouped together. At a detail view the user can chose which parts to edit. For the case when some part is missing, it may be considered to make the indicator of the lacking information into a call to action for editing such element.
- I also used text statements but the layout of the statements also allows to fit an image if it was the case.
I hope this helps.
Pau
