Skip to content

Conversation

@steveoh
Copy link
Member

@steveoh steveoh commented Apr 22, 2025

here we go!

@steveoh steveoh requested review from leault and miriamseely April 22, 2025 00:05
@netlify
Copy link

netlify bot commented Apr 22, 2025

Deploy Preview for gis-utah-gov ready!

Name Link
🔨 Latest commit 73d8eac
🔍 Latest deploy log https://app.netlify.com/sites/gis-utah-gov/deploys/6806dd424b43f20007f4c329
😎 Deploy Preview https://deploy-preview-2996--gis-utah-gov.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 96 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@steveoh steveoh mentioned this pull request Apr 22, 2025
3 tasks
<h3>Capitalization</h3>
<p>The following terms are always capitalized:</p>
<BulletedList>
<li>State (when referring to the political entity)</li>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stephanie pointed out that this bit about capitalizing state conflicts with DGO's style guide. Apparently they like 'state of Utah' better than State of Utah, so we can remove this bit about capitalizing state.

</BulletedList>
<h3>Numbers and units</h3>
<BulletedList>
<li>Spell out numbers one through ten. For larger numbers, use numerals.</li>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<li>Spell out numbers one through ten. For larger numbers, use numerals.</li>
<li>Spell out numbers one through ten. For larger numbers, use numerals.</li>

Change to: "Unless a number begins a sentence, use numerals as opposed to spelling the word out", per Stephanie's recommendation.

@miriamseely
Copy link
Contributor

@steveoh I've added in a few notes from Stephanie for the style guide, otherwise I think we're good to go! The only thing I might consider changing, aesthetics wise, is indenting some of the sub-bullet points further in (like the ones that are an example of a previously stated point). I think that would make them look more like a sub-point, and not just that the bullets got a little funky. I like the separation with the colors, I think it looks great overall.

</li>
<li>ArcGIS Pro</li>
<li>QGIS</li>
<li>Lidar (capitalize the L only, rather than LIDAR or LiDAR)</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<li>Lidar (capitalize the L only, rather than LIDAR or LiDAR)</li>
<li>lidar (rather than LIDAR or LiDAR). It should be lower case 'lidar' all of the time, with the exception of when it is at the beginning of a sentence, used in a title, or when the writer feels like emphasizing the word.</li>

This is info that @rkelson sent me. I'm just trying to get it into the doc.

Copy link
Member Author

@steveoh steveoh Oct 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Scott. When we rebuilt the website, Rick chose Lidar for all the uses as shown everywhere in the website. As long as we keep things consistent, what the value is is not important.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I totally agree. I don't care which of the variations we go with as long as a decision is made. The fact that this PR has sat for months without being merged seems to indicate that there is still work to be done.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's my interpretation that most of the work was done in the google doc so I hope we don't spend too many more cycles on it. I think @leault and @chriswnek will help get it across the finish line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants