UGRC Website Rebuild

[brigsz]

Benefit

Build UGRC's gis.utah.gov website to adhere to DGO guidelines for agency websites, using the Utah Design System, and other elements outlined by DGO and DTS.

Acceptance Criteria

• Build website using Astro. Create page templates for the types of pages required by gis.utah.gov
  • [x] Landing page
  • [x] Pillar page
  • [x] Level 1 page
  • [x] Level 2 page
  • [x] Data page
  • [x] Blog page
  • [x] Documentation Page

Notes

New website

Lucid board

Meeting notes

Risks

• Communicating with DTS what is needed by UGRC regarding the design system
• Obtain design system elements in a generic form to use in Astro
  • UGRC may not be able to adhere to all guidelines if DTS does not finish this task.
• Determine most important website pages/sections to have completed
• Create (or pull from existing site) content for pillar, level 1 and 2 pages deemed most important for most important pillar, level 1 and level 2 pages
• March deadline
• UGRC staff time to define website content

Issue Reference

refs #

[nathankota]

Sprint 2

For the following products:

• [x] SGID and Discover (@jacobdadams & @gregbunce)
• [x] TURN GPS (@seanfernandez & @DenisePeterson)
• [x] UGRC API (@steveoh)

Create new product page content and/or review and make recommendations to existing pages and content (e.g. SGID) for:

• One sentence statement in Products pulldown
• Intro text (and logo)
• First level pages (3) - page names, description, link text and what it links to
• Popular [Pillar] Resources (4-6)
• More [Pillar] Resources (2-4)
• You might also like (2-4)

https://docs.google.com/document/d/1oN9Pow1m7cbU93fKVQAxqGCficoK5TXJ240_Rvy3GvE/

---

On the homepage

(@brigsz & @nathankota)

• Provide text for the Products, Solutions, and Collaboration pillar cards
• Brainstorm some "You might also like" content

https://docs.google.com/document/d/1rPy4PyDLkXbKXY-6S8DBWtcc51qc_8S8HcgIKtS6LYs/

---

For the Contact page

• Everyone submit an iPhone selfie, and

• Define 5 or so labels/tags that would help a visitor to the Contacts page understand what things you do or resources you manage so they can understand who to contact about what. Some possible tags are:

  • ArcGIS Pro
  • Base maps
  • Geocoding
  • API
  • GPS
  • Spatial reference
  • PLSS monuments
  • Survey/survey control
  • Apps
  • Bugs
  • Imagery
  • Lidar
  • Parcels
  • Discover
  • SGID
  • AGOL
  • Discover
  • Python
  • React
  • JavaScript
  • C#
  • GCP
  • Experience Builder?
  • Configurable Apps
  • Data management
  • Data analysis and management
  • Motorola systems (Spillman)
  • PSAP support
  • 911
  • Data ETL
  • AGOL admin
  • Database admin
  • Data aggregation
  • Roads
  • Address points
  • NGS State Coordinator
  • Broadband?

[nathankota]

Sprint 3

1. Solutions > By Audience

Define content for each of the following pages. Rather than cards, the format will be like https://gis-utah.netlify.app/solutions/for-government/.

• Government Employees (Steve, Matt, Nathan)
• GIS Users (Greg)
• Application Developers (Steve)
• Surveyors (Sean)
• Students (Jake)

2. Discuss how to handle data pages.

A little history, we had the data packages all bundled up in a zip file and then each item available individually. maintaining that was a pain so we got rid of the packages and now we have this awkward middle ground where we have some pages with multiple datasets and some with only one

[nathankota]

Sprint 4

Data Pages

Collaboration (@nathankota)

[nathankota]

Sprint 5

• Finish vision statement (@brigsz , @nathankota, @gregbunce )
• Collaboration > Events and Resources (@nathankota, @MichaelAGRC)
• continue with data pages (@rkelson, @jacobdadams, @gregbunce, @ZachBeck, @DenisePeterson, @mhchou?)
• Documentation (@steveoh, @DenisePeterson)
• Migrating Jekyll and other website construction tasks (@steveoh, @stdavis)
• Sharing pages (@steveoh)
• Imagery & Lidar page (@steveoh)
• Harder data pages (@steveoh)
• Suitability app (??)

Other old website pillar pages to consider here

[nathankota]

The website was launched yesterday. There is more work to do, which will be defined in new PI objectives for Q4 and onward.