fix issues with v2

[grmbyrn]

• moved posts for index and tracker into TorrustIndexPost.svelte and TorrustTrackerPost.svelte
• Key features list width should be 100% #6
• Review design for table of contents #8
• Minor bugs in homepage #12
• Homepage cards don't have the same padding as design #25
• Top menu padding is not the same as the design #26
• Related Post section does not look like the standard blog post list #27
• Ask the designer how we should implement navigation between blog posts #28
• Ask the designer how to implement share links in blog posts #29
• Remove # prefix from titles #30
• Ask the designer how to implement highlighted terms or sentences in markdown #36
• Font style in feature card is not the same as in the original design #43

[josecelano]

ACK 19437dd

[josecelano]

Good job @grmbyrn, just a couple of comments:

1. I'm closing only the issues I consider finished 100%. I commented on the ones I think there are pending things to do.
2. Make sure the linter passes before opening the PR and fix it if it fails after opening the PR.
3. Make sure to follow the design as much as possible (pixel). I think it's very important to implement exactly what the designers gave us. They have their reasons and in my opinion the final site looks much worse with many mini changes.

[grmbyrn]

Good job @grmbyrn, just a couple of comments:

1. I'm closing only the issues I consider finished 100%. I commented on the ones I think there are pending things to do.
2. Make sure the linter passes before opening the PR and fix it if it fails after opening the PR.
3. Make sure to follow the design as much as possible (pixel). I think it's very important to implement exactly what the designers gave us. They have their reasons and in my opinion the final site looks much worse with many mini changes.

That's no problem. For the linters, I ran them before and had no error. The error after opening the PR indicates an issue in Hero.svelte but nothing comes up when I check it.

[josecelano]

Good job @grmbyrn, just a couple of comments:

1. I'm closing only the issues I consider finished 100%. I commented on the ones I think there are pending things to do.
2. Make sure the linter passes before opening the PR and fix it if it fails after opening the PR.
3. Make sure to follow the design as much as possible (pixel). I think it's very important to implement exactly what the designers gave us. They have their reasons and in my opinion the final site looks much worse with many mini changes.

That's no problem. For the linters, I ran them before and had no error. The error after opening the PR indicates an issue in Hero.svelte but nothing comes up when I check it.

In those cases you can run npm run format and check is there was a git change (git status). I don't know why it's not showing the error.

I guess you mean this: