docs: rename foo/foo.md to foo/README.md in docs, update links

[grepsuzette]

Propose to rename it.

[grepsuzette]

Not sure if good idea, but ChatGPT:

Renaming a foo/foo.md file to foo/README.md within a documentation tree can be a good practice in many cases.

The README.md file is commonly recognized as the primary documentation entry point in many projects. By renaming foo.md to README.md, you are following a standard convention that makes it easier for others to quickly understand the purpose of the file and the content it holds when they navigate through the documentation tree. This can improve the overall clarity and organization of your documentation.

[thehowl]

this makes sense to me, seeing also as the urls on the website are not connected to the filename; but cc @leohhhn.

[leohhhn]

This makes sense 👍

Could you do it for every index file for consistency? Each section has one.

[grepsuzette]

This makes sense 👍

Could you do it for every index file for consistency? Each section has one.

Yep, I'll see if there are others!

[moul]

why removing this file?

[grepsuzette]

This file got removed in c67eff6 (notice it's not in https://github.com/gnolang/gno/tree/master/docs/assets/how-to-guides anymore) but it was still present in my PR.

I got conflicts such as files deleted or removed on master since this PR was opened and tried to solve them manually.

I was actually reading about rebase vs merge workflows because of that.

Will review #2125, thanks.

[moul]

Okay, I see. I think your PR is just unsynchronized with the master branch. You should update your branch.

Essentially, fix the Git-related issues, and this PR should no longer have the following:

[moul]

I noticed you removed several files. Was this intentional?

The PR title no longer matches the changes. Please update it.

I suggest reviewing #2125 as it's related and both are needed.

[moul]

Please review #2125 first, as I believe this PR conflicts with its final purpose.

Once there is a clear action plan for those two pull requests, please let me know, and I'll review this PR again.