Expected: On the photo preview page, pressing Esc key should navigate back to the grid.

Actual: On Edge browser, this works only at random.

Additional details: Only tested in Edge and Safari and no issues noted in Safari.

Node 20.6 supports env variables.

This would help remove dotenv package and keep deps light

Tried enabling Netlify Lighthouse plugin, which

1. Runs Lighthouse after every build
2. Defaults to mobile test
3. Yields low score for SEO as Netlify runs it on deploy permalinks which has noindex for crawlers (known issue)

Some of this can be changed with a netlify.toml file, but it may not be ideal to commit a host specific file to the repository.

Solution for now is to use pagespeed.web.dev

https://www.npmjs.com/package/prettier-plugin-jinja-template

• Setup Monorepo
• Setup 11ty
• Setup Tailwind
• Setup Linters
• Setup Githooks
• Setup Browserslist
• Setup Sanity Studio
• Update Readme
• npm-run-all
• Create photo-grid config file in root

Causes prod site resulting in 404 errors for JS in photo page

Expected: Visiting localhost:3333/admin should automatically redirect me to localhost:3333/admin/.

Actual: Visiting localhost:3333/admin does nothing and stays in the home page. This also breaks post-login redirect where it ends up in the homepage with a token in the address bar as opposed to being in the admin page.

• Should not have a requirement on providing changesets when committing as this can negatively affect UX for consumers
• Github has an option to only create release note
• Create actions for releasing major, minor and patch releases
• npm version bump minor
• Test this on a separate repo to make sure

Ref:
https://www.youtube.com/watch?v=_ueJ3LrRqPU

• Load Data with Sanity
• Handle color Scheme preference
• Create grid layout

Descriptions, titles and tags

https://metatags.io/

Update wiki about adding/using the vision plugin tho

Clicking on the ellipsis uncovers more text but its not clear to the MacOs user that you have to scroll without the scroll bars showing up.

https://stackoverflow.com/questions/50037663/how-to-close-a-native-html-dialog-when-clicking-outside-with-javascript

During installation, there's dependency warning for Styled components coming from Sanity Media plugin.

Plugin has to fix this issue in order to resolve warnings.

with&dl param

New Sanity free pricing model is pretty generous and won't need to be so frugal

https://www.11ty.dev/docs/plugins/rss/

https://developers.google.com/search/docs/crawling-indexing/block-indexing

Seems a lot of packages are standardizing on where cache files are stored and we should align with this by placing 11ty's fetch data inside node_modules/.cache/11ty

https://www.sanity.io/docs/webhooks

https://www.sanity.io/blog/introducing-groq-powered-webhooks

https://www.sanity.io/plugins/vercel-deploy

https://www.sanity.io/plugins/sanity-plugin-dashboard-widget-netlify

https://www.sanity.io/answers/triggering-netlify-redeploy-from-sanity-and-setting-up-live-preview-in-next-js-with-sanity-

https://explorers.netlify.com/learn/angular-dynamic-data-with-sanity-io/sanity-io-netlify-build-hooks

Thank you for photo-grid, which looks nice.

Is that possible to not use sanity and netlify to host it?

I tried to use it locally, but I need a Sanity account, even on localhost...

Expected: Should be able to use arrows keys to go forward and backward within photos. Also add other key bindings for escape and viewing details.

Issue:
Right now, the author would have to create a .env file to set values required for Sanity. This might introduce friction to getting things started.

Solution:
These values get bundled up in the Sanity JS and you would still need an authorized account to make any changes to the dataset. Therefore, move these settings to photo-grid.json config file and add a recommendation to use environment variables in the readme.

Create a Github Wiki for the following:

• Local development
• Contributing
  • Link to board with todos (create a separate view?)
• Setting up Netlify deployments (serving admin in a subdirectory, Sanity CORS, ENV variables)
• Design thinking - Sanity API calls during build to run it as cheaply as possible. Considered client side JS as well
• Photo vs image naming
• How to choose a hosting platform (should support build hooks)
• Github board
• Adding content and publishing

• Add links in README to "deploy with Netlify" or Vercel (or both)
• Update Readme with a link "Add yours" that users can share their Photo Grid links

Admin (Sanity Studio) uses the Media plugin and it currently does not honor the "Appearance" setting:

Perhaps remove the "Appearance" setting from the menu until that is supported by the Media plugin.

Sanity Studio can embedded into an existing app. This would make things much simpler and reduce package dependencies.

Refactor the code to nix monorepo setup and just setup Photo Grid as a single project with Sanity embedded as a subdirectory (/admin).