-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Lidar Blog Post #2916
base: main
Are you sure you want to change the base?
feat: Lidar Blog Post #2916
Conversation
✅ Deploy Preview for gis-utah-gov ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
The lazy eager image stuff allows the page to load faster if the image is expected to not be visible on the initial page load.
Here's an article about writing alt text for images that just came through my feed I found very helpful so I thought I'd share as it's not very intuitive.
src/content/blog/2024-12-13-statewide-lidar-products-now-available.mdx
Outdated
Show resolved
Hide resolved
how do we get this to deploy |
src/content/blog/2024-12-13-statewide-lidar-products-now-available.mdx
Outdated
Show resolved
Hide resolved
a couple misc. edits I think this looking great! The only problem I have is we have covered as much of the state as we can but really do not have "statewide coverage" considering the hole over dugway proving grounds. The hole is in the graphic on page https://gis.utah.gov/products/sgid/elevation/lidar/#2022-western--eastern-utah @miriamseely can you make some adjustments to accommodate this fact?
moving ricks comments out of the commit for easier visibility
|
This PR was automatically created by the "Issue opened (new blog)" workflow.
closes #2915