Consider wiki/ as the default folder instead of .github/wiki

[jcbhmr]

As stated in #31, the default is .github/wiki because it's specific to GitHub. That was a "why is it this way" post, this is my "rebuttal" or alternative proposal idea as to why I think wiki is better:

It sorta comes down to your semantic opinion. Is it a generic wiki, or is it github specific? Like for instance, would you have a GitLab ↔ GitHub mirror with separate wikis? If so, then .github/wiki/** makes perfect sense to parallel a .gitlab/wiki/** so that each gets a custom wiki deployment. If you'd use the same wiki, then something like a more generic wiki/ that just so happens to get deployed to GitHub wiki makes more sense in my brain 🧠

sorta like how a docs/ folder can be deployed to github pages, but it's not in .github/pages/**. It's like a generic file folder that just so happens to be deployed to Vercel, or Netlify, or in this fictitious scenario, github pages.

That and it improves discoverability if you clone the docs locally like in vscode since most people don't touch the .github folder when working on non-CI stuff

all in all, I think it just makes more semantic sense to have the default be wiki vs .github/wiki since wiki is more generic.

But that's my opinion. 🤷‍♂️

[spenserblack]

One thing to consider is that .github/, and other hidden folders, is often used for files that developers usually don't need to reference, and users never need to reference (directly). For example, assets for the README. Since readers should reference the actual Wiki, and coders will probably make more contributions to the main project than the wiki.

Using GH Pages as an example, yes, you can deploy from docs/ which is visible, but you can also deploy from an orphaned branch gh-pages, which is very hidden, and specific to GitHub 😆

🤔 That gives me an idea for deploying from a gh-wiki branch...

[jcbhmr]

❤ i can concede that there is some legitimate precedent surrounding non-github-specific stuff in .github just to "stash it" out of the way (which is debatable whether or not that's good 🤷‍♂️, but it's a good point that it does exist as a prior convention)

a point in favor of wiki vs .github/wiki is its prevalence in existing repos and the convention of where wiki docs are put: 137,000 in /wiki/**.md vs 154 in /.github/wiki/**.md -- pretty stark difference 🤪

another might be that a lot of the other wiki actions default to docs/ or wiki/ or even ./ for deployments. the most popular one defaults to wiki/ https://github.com/Andrew-Chen-Wang/github-wiki-action/blob/master/action.yml#L11

[jcbhmr]

if possible, itd be nice to have a yes, maybe, or dont-bring-it-up-again answer to resolve #57 which is in limbo

[spenserblack]

Really old discussion, but just thought of this after following discussions on GitHub's new alert syntax. GitHub has now extended their markdown syntax, in a way that is very specific to GitHub and doesn't seem to be compatible with any non-GitHub client right now:

> [!WARNING]
> This will not render properly on another site.

Warning

This will not render properly on another site.

The fact that GitHub is now diverging from popular Markdown syntax and making GFM more unique solidifies my opinion that GitHub wiki files should live under .github/ by default.