Org chart - ucsf-ckm/ucsf-library-ux-and-web-documentation GitHub Wiki

As of April 2023, the UX Team will be maintaining the staff org chart.

Also update:

  • the library staff directory table
  • news author bio (if applicable)

Background

Created components in Figma for each type of staff box. This means any future changes to color or type can be made at the component library level and will update anywhere the components have been used.

Published those components to a team library (requires prof team) to make them usable across projects. See documentation and video Create a shareable team library.

  • min 1:30 shows how to publish a new library
  • min 2:25 when you create a new document, choose which libraries to turn on, those components then become available in that doc

figma libraries

Colors

Learning #14828C

Technology #007242

Archives #443E8C

Marketing #0F388A

Administration #6C247C

The org chart

The actual chart is built in FigJam using its chart connectors with the Figma components

How to use

  • Add components as needed to build out the org chart in FigJam following steps at Use stickers and libraries in FigJam
  • Replace text with actual names and titles to each component added to page
  • NOTE: drag from the library each time -- don't drag in just one and duplicate figjam more

Making changes

  • If any changes need to be made in future to the color, size, font, etc. it can be done in the library within Figma
  • Must then republish the change
  • Go back to the org chart in FigJam and update and the changes will sync! figjam component update
  • update the text at the bottom to reflect the date of last revision

Save as PDF

  • In Figjam, Main Menu > File > Export as…
  • Rename to ucsf-library-org-chart.pdf so it will supercede the last version in UCSF Box That file is linked from the staff directory page.
  • Final step is to upload the file to Box. Click the three dots and choose Upload New Version

Box version

Accessibility

An org chart PDF is fundamentally challenging to make accessible. Since this is primarily an internal document, we will not be spending time on creating an alternate text version of the whole thing or adding tags, etc. that don't truly make the document accessible anyway.