Fix challenges numbering

[feliperodri]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

[jaisnan]

Thanks!

[carolynzech]

I find the blank page with -- to be a bit odd -- should we just wait until we have another challenge to be challenge 7? The challenges still go 6 -> 8 visually.
I like the changes to make the links to issues consistent. I was planning to write another challenge sometime next week, so I would propose that we avoid making this blank file and instead just wait for that to be challenge 7.

[feliperodri]

I find the blank page with -- to be a bit odd -- should we just wait until we have another challenge to be challenge 7?

@carolynzech when I texted locally, this would lead to the wrong numbering of the challenges until we add the challenge 7 (the sequence didn't obey the numbering order when rendered). Am I missing something? If so, I can remove the blank page. If not, I'm ok with keeping it until we include a new challenge next week.

[jaisnan]

I find the blank page with -- to be a bit odd -- should we just wait until we have another challenge to be challenge 7?

@carolynzech when I texted locally, this would lead to the wrong numbering of the challenges until we add the challenge 7 (the sequence didn't obey the numbering order when rendered). Am I missing something? If so, I can remove the blank page. If not, I'm ok with keeping it until we include a new challenge next week.

Fwiw, i'm okay with the blank page until next week as well. @carolynzech's concern is valid, but this should be fixed shortly when we add our challenge. Feel free to disagree if you have strong opinions about this.

@feliperodri Would it help to add a screenshot of what the index page looks like somewhere in the PR description?

[celinval]

@feliperodri you could also enable your fork to publish documentation from your fix-numbers branch so we can review how it looks like.

I find the blank page with -- to be a bit odd -- should we just wait until we have another challenge to be challenge 7? The challenges still go 6 -> 8 visually. I like the changes to make the links to issues consistent. I was planning to write another challenge sometime next week, so I would propose that we avoid making this blank file and instead just wait for that to be challenge 7.

Which blank page are we talking about?

[feliperodri]

@feliperodri you could also enable your fork to publish documentation from your fix-numbers branch so we can review how it looks like.

@celinval I'll enable it. Meanwhile, here it's an imagine:

Which blank page are we talking about?

I already removed it. I added an unnecessary blank page.

[feliperodri]

@celinval I think I need one more approval to get it merge.

[carolynzech]

@celinval I think I need one more approval to get it merge.

Hm, two approvals should be enough--seems like the check approval action is hanging. I'm going to try revoking my approval and then re-approving to see if that triggers the check.

Dismissing review to re-approve, see comment