ScratchAddons/scratchaddons.github.io

Suggestion: merge "website" repo with this one and add CNAME for redirecting

tb148 opened this issue · 4 comments

tb148 commented

So we don't need two repos for one thing.

WL also approached me about this, but I forgot to say it in here, so here it is along with some additional info.

Having the repo name to scratchaddons.github.com has a downside of having your repository name for the website ugly, but then you have scratchaddons.com for every repository on the organization.

For example, I set the hans5958.github.io CNAME to hans5958.me. That would result with my other repositories have their site deployed inside the domain, like https://hans5958.me/Black-MIDI-Meta is for https://github.com/Hans5958/Black-MIDI-Meta

About that, I'm not so sure if it is a good one or a bad one. I think it is good, but then I afraid something happened in the future, like maybe another website rewrite that changes how the domain will be used or some kind, so that's why I separate it.

I actually didn't want this repository to be made again, but because it is already linked, and the bad name the repo has, I have decided to make another one. Perhaps if sometime in the future we lost scratchaddons.com, then it would be okay to move it, because that's the only way we can serve content in our root directory of the domain.

tb148 commented
  1. I don't think we will ever have multiple domains because 1 is enough and of course the .com domain is better than the .github.io domain, so I don't think having everything inside scratchaddons.com is bad.
  2. Even if we lost scratchaddons.com, the fix would be as simple as removing or editing the CNAME.
  3. I don't think that the name is ugly. It is long but very easy to remember and understand.
  1. I don't think we will ever have multiple domains because 1 is enough and of course the .com domain is better than the .github.io domain, so I don't think having everything inside scratchaddons.com is bad.

I'm not talking about of needing other domains. Subdomains exists. It could be anything. One example is when someone wanted to a React/Angular/Vue site instead of this simple Bootstrap.

  1. Even if we lost scratchaddons.com, the fix would be as simple as removing or editing the CNAME.

It is also easy to move one repository to another, and I'm not talking about using Git/a Git client.

  1. I don't think that the name is ugly. It is long but very easy to remember and understand.

The name is not descriptive enough, probably for Scratch user who is interested.

Closing due to inactivity.