Difference between revisions of "ARK2/UX"
(→Site Home Page) |
(→UX) |
||
| Line 1: | Line 1: | ||
= UX = | = UX = | ||
| − | 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 | + | 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 the default Bootstrap web interface which needs to be both feature-complete and flexible, albeit at the cost of some efficiency. | + | 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 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 == | == Website Home Page == | ||
Revision as of 10:04, 12 December 2016
Contents
UX
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 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
User Home Page
List View Screen
Item View Screen
Advanced Search
- Set based queries
User Security
- Register
- Login
- Captcha
- OAuth2 (Facebook, Google, etc)
- Request password reset
- Profile
- Personal details
- Contact details
- Security details
Admin Screens
See Admin Screens. UX required is primarily layout and flow, plus User Admin, Translation and Vocabulary pages.
