docs: Homogenize governance (CoC, CONTRIBUTING & HOWTO) across files

[davorpa]

• Homogenize markdown format across files. Solve some linter faults
  • docs(contributing): Homogenize format across translated files #6625
  • docs(howto): Homogenize HowTo's format across translated files #6724
• Add missing crosslinks and docs/README.md #6698
• Sort links according to english text seen in README.md. Addressed in Post-hacktoberfest chore: move docs to folders #6164

Local branch

• Reintegrate Added links to korean docs  #5837
• Reintegrate stalled conflictive added CONTRIBUTING.md in Indonesian (CONTRIBUTING-id.md) #5752 to complete translation. Addressed by: docs(contributing): Merge #5816 with #5752 Indonesian translation #6719
• Reintegrate Added Bengali Language Support for HOWTO #6429
• Reintegrate translating HOWTO.md to Dutch #5831
• Reintegrate docs: Add HOWTO in Turkish #6567

[eshellman]

I'll prepare a PR that

• moves all the instructions files into a docs directory (is that the best name?)
• removes crosslinks from each translated file and adds them to a docs index page so new files only need to add a link in one place.

[davorpa]

I'll prepare a PR that

• moves all the instructions files into a docs directory (is that the best name?)
• removes crosslinks from each translated file and adds them to a docs index page so new files only need to add a link in one place.

See this note in chore posted by you: #6164 (comment)

[eshellman]

so using "docs" works?

[davorpa]

@EbookFoundation/reviewers last step. What do you think about this HowTo's homogeneization?

Performed Tasks:

• Add H1 header
• Read this ... right alignmements
• Split a bit first paragraph to highlight welcome.
• Introduce Pull Request acronym.
• Trademark typos: GitHub, YouTube, Pull Request
• Update GitHub links urls. help/guides subdomain was moved to docs so a 301 Redirect is skipped.
• Details block added, with center align. When clicked, the contributor graphs are toggled.
• Some bolds to highlight common issues (like in CONTRIBUTING)
• Repo name in monospace font
• Re-worded last part of 4th paragraph to explain that no new PR is needed to open if there are linter errors or changes are requested. Now it's more clear, I thought.

It's ok? Aproved to continue apply into the other files?

[SethFalco]

I think this looks pretty nice, but unfortunately, you may want to test it in the mobile app.

I don't think things like the <details> tag work there. (Bear in mind when I tested was over a year ago.)

We could always ignore that technically, since I'd consider that a bug on GitHub's side, though. (Markdown is Markdown, and should work regardless of client.)

[davorpa]

I think this looks pretty nice, but unfortunately, you may want to test it in the mobile app.

I don't think things like the <details> tag work there. (Bear in mind when I tested was over a year ago.)

We could always ignore that technically, since I'd consider that a bug on GitHub's side, though. (Markdown is Markdown, and should work regardless of client.)

https://davorpa.github.io/free-programming-books/ Tested on a Kindle Fire EReader and a Samsumg S5 (Android 6.1). It works as expected 4x4 in both environments: GitHub Preview, GitHub Pages. In anyway, the previous link "large, growing" points to same graph

[SethFalco]

Just checking, you tested in the GitHub Mobile App?
https://play.google.com/store/apps/details?id=com.github.android&hl=en_US&gl=US

[davorpa]

Just checking, you tested in the GitHub Mobile App?
https://play.google.com/store/apps/details?id=com.github.android&hl=en_US&gl=US

yes. it works as well.

Closed	Open

[eshellman]

on the whole, I think this looks great.
I'm ambivalent about monospacing "Free-Programming-Books". The name travels outside of the repo to places where it's not possible (or just more work for me) to monospace it - twitter, the Free Ebook Foundation website, and most particularly, the HTML presentation on github. I've managed to keep the dashes intact, mostly. So while monospacing looks good here, I prefer to use less code-y version.
Have commented in the PR on the text that reveals the usage graph.