The TSC has undertaken to review the TrustedFirmware.org website and propose changes. Some TF website review headings and criteria are listed below. Please edit this document to add review inputs. It would be helpful if you could add your initials to contributions. Version history is also tracked. **TF Website Review** **Identity** - Branding - Key message(s) **Navigation** - Primary menu location and structure - Other menus (footer) - Other thoughts on navigation **Content** - Information about the project - Posts **Images** - Relevant - Quality - Affect on loading times **Typography** - Effective use of different fonts and sizes **Action/Engagement/Involvement** Supported actions: - Access a document or recording - Subscribe to a mailing list - Contact the project - Subscribe to a calendar event **Consistency** - Cross-platform issues

The TSC has undertaken to review the TrustedFirmware.org website and propose changes. Some TF website review headings and criteria are listed below. Please edit this document to add review inputs. It would be helpful if you could add your initials to contributions. Version history is also tracked. **TF Website Review** **Identity** - Branding - Key message(s) **Navigation** - Primary menu location and structure (BillF) I suggest that the majority of users of the site will either be interested Cortex-M or Cortex-A but definitely not both. A smaller number of senior technical people will want the whole site view, and then some execs will want to see a top level summary of the project. Maybe we should move to manage these 4 user types. We could offer a quick selection of "mini-sites" for Cortex-A and Cortex-M, sitemap for expert users, and an exec overview/summary including legals etc. Mixing Cortex-A and Cortex-M throughout the site means that the menus are overloaded. - Other menus (footer) - Other thoughts on navigation **Content** - Information about the project - Posts **Images** - Relevant - Quality - Affect on loading times **Typography** - Effective use of different fonts and sizes (BillF) I have a note from a TSC meeting that the navigation font is too small and the content font is too large. **Action/Engagement/Involvement** Supported actions: - Access a document or recording - Subscribe to a mailing list - Contact the project - Subscribe to a calendar event **Consistency** - Cross-platform issues

The TSC has undertaken to review the TrustedFirmware.org website and propose changes. Some TF website review headings and criteria are listed below. Please edit this document to add review inputs. It would be helpful if you could add your initials to contributions. Version history is also tracked. **TF Website Review** **Identity** - Branding - Key message(s) **Navigation** - Primary menu location and structure (BillF) I suggest that the majority of users of the site will either be interested Cortex-M or Cortex-A but definitely not both. A smaller number of senior technical people will want the whole site view, and then some execs will want to see a top level summary of the project. Maybe we should move to manage these 4 user types. We could offer a quick selection of "mini-sites" for Cortex-A and Cortex-M, sitemap for expert users, and an exec overview/summary including legals etc. Mixing Cortex-A and Cortex-M throughout the site means that the menus are overloaded. - Other menus (footer) - Other thoughts on navigation **Content** - Information about the project - Posts **Images** - Relevant - Quality - Affect on loading times **Typography** - Effective use of different fonts and sizes (BillF) I have a note from a TSC meeting that the navigation font is too small and the content font is too large. **Action/Engagement/Involvement** Supported actions: - Access a document or recording - Subscribe to a mailing list - Contact the project - Subscribe to a calendar event **Consistency** - Cross-platform issues