docs/8.0/ayanova/docs/ay-start-changes-from-v7.md

@@ -20,6 +20,10 @@ For those that would prefer to keep their AyaNova installation in-house or even
 
 ## User interface changes from v7
 
+![v7](img/ay-start-changes-v7.png)
+
+![v7](img/ay-start-changes-v8.png)
+
 AyaNova 7 had several different user interfaces: the main interface was a Windows desktop application and as optional add-on products we had several different web browser interfaces for varying levels of devices. Each web interface had a limited sub-set of the full features in the Windows application and required separate installation and configuration procedures.
 
 AyaNova 8 has a single web application interface that adapts itself automatically to the device format. Any device on any platform with a modern web browser from a smart phone to a full sized desktop computer can use all features of AyaNova equally. This means you can use AyaNova on an iPhone, Android, Windows desktop, iOS, Linux etc.
@@ -28,6 +32,16 @@ Having one web application interface means there is nothing to install or update
 
 In order to support the front end "client" devices using AyaNova, there is now a back end self contained [AyaNova server](ops-intro.md) that handles all requests and can be hosted on Linux or Windows, either onsite or with a web hosting provider.
 
+### Design changes
+
+AyaNova 8 interface features a familiar layout that has been re-designed to improve usability over AyaNova 7.
+
+-   modern, clean uncluttered interface
+-   simple, sharp scalable SVG icons that look sharp on any device
+-   now _every_ form can be easily [customized](ay-customize.md) to remove unused fields
+-   more working area screen space freed up
+-   simplified work orders, quotes and PM's with more features but only visible when you use them
+
 ## Existing feature changes
 
 One of our main goals with AyaNova 8 was to make AyaNova easier to use and add many new features and improvements based on feedback from our customers.
@@ -146,10 +160,10 @@ For this reason the v7 templates feature is no longer required and has not been
 
 The [work order status](svc-work-order-status.md) feature has been greatly expanded into a set of powerful features that can support process control with:
 
-- tracking of every change of status (who and when visible right inside the work order)
-- restrictions by security role of who can set or unset any status (this allows for controlling the entire service process from creation to final billing or follow up)
-- locking status which when selected freezes a work order (replaces the v7 "Service completed" checkbox)
-- completed type status to indicate a work order is completed which can be used with notification etc (replaces the v7 "Closed" checkbox)
+-   tracking of every change of status (who and when visible right inside the work order)
+-   restrictions by security role of who can set or unset any status (this allows for controlling the entire service process from creation to final billing or follow up)
+-   locking status which when selected freezes a work order (replaces the v7 "Service completed" checkbox)
+-   completed type status to indicate a work order is completed which can be used with notification etc (replaces the v7 "Closed" checkbox)
 
 These new features are optional and not necessary to use if just a simple status indicator is desired and it can be used in much the same way as in v7 if there isn't a need for the extra features.
 
@@ -283,17 +297,17 @@ In v8 we have expanded this feature into a full [Event log](adm-history.md) that
 
 The following objects from v7 have been replaced by tags in v8:
 
-- User certification
-- User skill
-- Client group
-- Dispatch zone
-- Part category
-- Regions
-- Scheduleable user group
-- Unit service type
-- Unit model category
-- Work order category
-- Work order item type
+-   User certification
+-   User skill
+-   Client group
+-   Dispatch zone
+-   Part category
+-   Regions
+-   Scheduleable user group
+-   Unit service type
+-   Unit model category
+-   Work order category
+-   Work order item type
 
 [Migrating from v7](ops-import-v7.md) will automatically create tags for these objects and will then tag the corresponding objects that were set to these category items with the new tags created.
 
@@ -325,10 +339,10 @@ In v8 we have expanded and improved this into it's own separate [Attachments](ay
 
 All v7 "Assigned docs" and wiki embedded file features have been consolidated in v8 into a new [Attachments](ay-start-form-attachments.md) feature:
 
-- in v7 embedded wiki files were stored _inside_ the database, now Attachments are stored in a special AyaNova controlled folder in the file system to avoid bloating the database
-- In v7 Documents were simply links to existing files visible to the workstations / server; file attachments are stored in a special folder managed by the AyaNova server making it easier to backup and restore and ensure all data is consolidated in one folder
-- Rename - can now rename an attached file
-- Notes - there is now a notes field
+-   in v7 embedded wiki files were stored _inside_ the database, now Attachments are stored in a special AyaNova controlled folder in the file system to avoid bloating the database
+-   In v7 Documents were simply links to existing files visible to the workstations / server; file attachments are stored in a special folder managed by the AyaNova server making it easier to backup and restore and ensure all data is consolidated in one folder
+-   Rename - can now rename an attached file
+-   Notes - there is now a notes field
 
 ### Display formats