Open RosaWagner opened 4 years ago
Sounds like a good idea but I'm worried we'll break the hyperlinks by doing this. If we're able to redirect then I have no problem.
Actually, some of the hyperlinks need to be refreshed too, it could be the opportunity to check them all (a lot of work though). But I mostly wonder if it will create conflict with other non-merged branches.
a lot of work though
could maybe be automated. There might even already be a project that checks md files in github repos for broken links.
There might even already be a project that checks md files in github repos for broken links.
The overall structure is good. Rather than numbered files, I propose taking these files into a gh-pages branch and Jekyll website format, and using the jekyll frontmatter to provide the order.
Couple of examples:
The overall structure is good. Rather than numbered files, I propose taking these files into a gh-pages branch and Jekyll website format, and using the jekyll frontmatter to provide the order.
I have no idea how to do that but will make some research and propose something.
Is there a way to create some kind of a structured bibliography with the links used in different md files? And the concerned md and the one in the bibliography would be also linked (if you change one, the other is also modified).
So I think we agree the docs and the spec are delivering a lot of useful informations, although it is kind of overwhelming and could need a bit more structure. As a first step of reviewing the docs I would like to suggest this structure:
Agree, disagree, PR, not PR ?