-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
My opinions (and also additional info):
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. |
Do we prefer:
https://blog.runners.sh
orhttps://runners.sh/blog
? (orhttps://runners.sh/blog/
, with the trailing slash)https://zine.runners.sh
orhttps://runners.sh/zine
The text was updated successfully, but these errors were encountered: