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

blog.runners.sh or runners.sh/blog? #1

Open
ucubic opened this issue Jan 9, 2025 · 2 comments
Open

blog.runners.sh or runners.sh/blog? #1

ucubic opened this issue Jan 9, 2025 · 2 comments
Labels
question Further information is requested

Comments

@ucubic
Copy link

ucubic commented Jan 9, 2025

Do we prefer:

  • https://blog.runners.sh or https://runners.sh/blog? (or https://runners.sh/blog/, with the trailing slash)
  • Same with https://zine.runners.sh or https://runners.sh/zine
@ucubic
Copy link
Author

ucubic commented Jan 9, 2025

My opinions (and also additional info):

  • We've basically confirmed that the projects page is gonna be on a subdomain (projects.runners.sh), because it's the only subdomain (for now) that contains JavaScript. I'm leaning towards separate subdomains for everything for consistency.
  • If we do use the URL non-subdomain thingy, I prefer the trailing slash for... reasons. It's a "directory" of items whereas blog posts are standalone items which wouldn't have the trailing slash.

What do you think?

@XeynQ4 XeynQ4 added the question Further information is requested label Jan 9, 2025
@kedislav
Copy link
Member

kedislav commented Jan 11, 2025

My opinions (and also additional info):

* We've basically confirmed that the projects page is gonna be on a subdomain (`projects.runners.sh`), because it's the only subdomain (for now) that contains JavaScript. I'm leaning towards separate subdomains for everything for consistency.

* If we do use the URL non-subdomain thingy, I prefer the trailing slash for... reasons. It's a "directory" of items whereas blog posts are standalone items which wouldn't have the trailing slash.

What do you think?

I agree with what you're saying about the trailing slash for directories (as "containers of things"), however I don't think we should separate everything into subdomains; the "projects" page is separate since it's big enough as it is (or will be). It runs code or hosts our own interactive stuffs and as such, a subdomain is preferrable (relying on the size of the content we're serving). I want to reserve subdomains for big things, but a blog (containing our CTF writeups, exploits and other fun stuff) is smaller, and it probably will require tags from us, so it can just be runners.sh/blog/... or /blog/<date>, or /blog/<tag>, etc.

Besides, if we moved the blog to a subdomain as opposed to a link, what would our homepage contain? just be a "click here for fun things to happen" I'd like to keep text blogs or our "currently doing" thing alongside the homepage, and bigger, more complex services into subdomains (game servers, hosted stuff, zine, etc).

LMK what you think about this idea, maybe I'm confusing stuff more this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants