We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://seagl.org/press/ doesn't actually work, only https://seagl.org/press does (likely because it is a file rather than a directory). However, we use https://seagl.org/news/ for our blog. It would be nice if we could add a redirect or something similar to route https://seagl.org/press/ to https://seagl.org/press
The text was updated successfully, but these errors were encountered:
Quick count of how many paths we’re publishing in each format:
/archive
/archive/…
/archive/…/…
/cfp
/code_of_conduct
/code_of_practice
/faq
/feedback
/maps/2022
/meet
/news/2021/06/24/cfp
/press
/sponsors/…
/style_guide
/watch
/code_of_conduct.html
/code_of_practice.html
/get_involved.html
/maps/….html
/news/…/….html
/schedule/….html
/fliers/…/
/news/
Do we just need /press/ because e.g. it’s been linked somewhere? Or you want everything to match /news/?
/press/
Sorry, something went wrong.
No branches or pull requests
https://seagl.org/press/ doesn't actually work, only https://seagl.org/press does (likely because it is a file rather than a directory). However, we use https://seagl.org/news/ for our blog. It would be nice if we could add a redirect or something similar to route https://seagl.org/press/ to https://seagl.org/press
The text was updated successfully, but these errors were encountered: