Skip to content
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

https://seagl.org/press/ does not work #337

Open
nhandler opened this issue Aug 10, 2022 · 1 comment
Open

https://seagl.org/press/ does not work #337

nhandler opened this issue Aug 10, 2022 · 1 comment

Comments

@nhandler
Copy link
Contributor

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

@AndrewKvalheim
Copy link
Member

AndrewKvalheim commented Aug 12, 2022

Quick count of how many paths we’re publishing in each format:

  • Plain path: 451
    • /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
  • Path with filename extension: 207
    • /code_of_conduct.html
    • /code_of_practice.html
    • /get_involved.html
    • /maps/….html
    • /news/…/….html
    • /schedule/….html
  • Path with trailing slash: 7
    • /fliers/…/
    • /news/

Do we just need /press/ because e.g. it’s been linked somewhere? Or you want everything to match /news/?

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

No branches or pull requests

2 participants