githubpage

[tylerrowsell]

No description provided.

[caution-tape-bot]

👋 This PR might modify or add cookies to Shopify, and these changes might be subject to privacy regulations. If your PR is not related to cookies, feel free to ignore this message.

Please avoid adding any new cookies to merchant storefronts unless absolutely necessary, we are undergoing an effort as a company to reduce our cookie footprint for legal reasons.

If you're adding/removing cookie(s) to storefronts, admin or checkouts, reach to us in #help-cookie-compliance so we can study your use case. After that, update this cookies list.

Instructions on updating the cookies list can be found here.

If your repository is not related to storefronts, and instead is related to other surfaces like shopify.com, shop.app, etc. our tooling can't support purpose-based blocking for you yet. This means that we would still like you to add the cookie to the allow list so we can keep track of it, but you should:

• Choose strictly_necessary as the purpose
• Explain in the description of the cookie that you chose strictly necessary because there is no visitor consent available in the client surface of your cookie.
• Use ["other"] for the surface of the cookie.

If you have any other questions, reach out to #help-cookie-compliance in slack so we can help you.

Thanks!

---

This comment was added by the CookieCompliance::CookieBlaster Caution Tape Bot rule.
View the source of this rule in Services DB

[caution-tape-bot]

👋 This PR might modify or add cookies to Shopify, and these changes might be subject to privacy regulations. If your PR is not related to cookies, feel free to ignore this message.

Please avoid adding any new cookies to merchant storefronts unless absolutely necessary, we are undergoing an effort as a company to reduce our cookie footprint for legal reasons.

If you're adding/removing cookie(s) to storefronts, admin or checkouts, reach to us in #help-cookie-compliance so we can study your use case. After that, update this cookies list.

Instructions on updating the cookies list can be found here.

If your repository is not related to storefronts, and instead is related to other surfaces like shopify.com, shop.app, etc. our tooling can't support purpose-based blocking for you yet. This means that we would still like you to add the cookie to the allow list so we can keep track of it, but you should:

• Choose strictly_necessary as the purpose
• Explain in the description of the cookie that you chose strictly necessary because there is no visitor consent available in the client surface of your cookie.
• Use ["other"] for the surface of the cookie.

If you have any other questions, reach out to #help-cookie-compliance in slack so we can help you.

Thanks!

---

This comment was added by the CookieCompliance::CookieBlaster Caution Tape Bot rule.
View the source of this rule in Services DB

[elsom25]

I don't imagine we can do a glob in JS somehow? Or can leave this for when we switch to GH pages?

[tylerrowsell]

I don't think so... since github pages is client side. They do have a github actions pipeline though.

We could also move it to dist we could rely on a single categories.yml instead though.

[elsom25]

We could also take the approach of generating /docs in a way that fits well with this file?

[tylerrowsell]

Yah... take a look at the latest push...

I've switched to use liquid and read from _data which can be automatically regenerated using a github action push on main.

[elsom25]

🚀

[elsom25]

If we're gonna have a file in bin, let's make them executable:

• Drop file extension: mv bin/generate_data.rb bin/generate_data
• chmod +x bin/generate_data
• Add shebang

Suggested change

	require 'yaml'
	#!/usr/bin/env ruby
	require 'yaml'

[elsom25]

After this is in I'll start a PR to start extracting some of this to lib/ which can let us start splitting generation from file manipulations, etc etc

[elsom25]

Liquid feels like a good use too given Shopify and all 😅 Love this thank you