ARK provides a very flexible platform akin to a CMS to allow different clients to configure their site to meet their data recording needs. This flexibility applies to the UX and UI as well as the data schema. ARK2 is a ground-up rewrite to bring ARK into line with modern web technology including a REST API, while also making it easier to configure and maintain.
While clients are able to build custom web or app interfaces using whatever technology they prefer, most will choose to use and possibly adapt the default Bootstrap/Twig web interface which needs to be both feature-complete and flexible, albeit at the cost of some efficiency. They are also likely to use variations on the standard 'Site Recording' data schema with 'Sites' or 'Projects' at the top level, as will the hosted ARK-as-a-service, so the default UX should be weighted towards that scenario.
Website Home Page
Landing page for a Website, usually some project brochure-ware.
User Home Page
Landing page for user after logging in, usually some kind of dashboard, but may be User Profile page.
Collection View Screen
- List Items by Module
- View modes: Text, Table, Thumbnails
- Filter Items by properties
- Select properties to view
- Integrate Advanced Search? (see below)
Version of Collection View with more advanced search tools, possibly same page with mode switch or hidden panel?
- Cross-module search
- Set based queries
- By Module / Type
- By Property
- By Actor
- By Period
- By Spatial
- Free Text
Site Recording Pages
ARK2 will provide a very flexible User Security system using an RBAC model. Website admins will have a choice of registration and authentication options and the UX/UI should adapt to these as configured.
- Optional OAuth2 (Facebook, Google, etc)
- Request password reset
- Personal details
- Contact details
- Security details
See Admin Screens. UX required is primarily layout and flow, plus User Admin, Translation and Vocabulary pages.