Todo list of new official website of Mark Text

[Jocs]

• [ ] Add Feature detail page.
• [x] Add sponsor page.
• [x] Click buttons in nav bar will scroll to relative page.
• [x] Change title in theme page.
• [x] Change all pictures in feature page to html, because pictures load slowly and can not change themes.
• [ ] Change log and User Guide.
• [ ] Auto update download link and CHANGE LOG after Mark Text release new version.(auto create a PR?)
• [ ] Add end-user documentation

Optimization:

• [x] load css as string. now we used a js file not a css file.
• [x] Change icon colors.
• [x] typo maxOs and I would write macOS (uppercase S)
• [x] remove the text shadow from the titlebar Mark Text
• [ ] add a download section with all download option like in the image above. Especially for the flathub description for Linux
• [ ] the header download buttons should point to the latest .dmg, setup.exe and .appimage binary and maybe add another button to scroll to download section
• [x] support for mobile/smaller screen sizes (option, not yet important)

[Lisiadito]

Regarding the point of the release links I have an idea. You can use following format: https://github.com/marktext/marktext/releases/latest/download/marktext-setup.exe Then you would just need to change the naming convention and not add the version number into the filename.

[Jocs]

PRs also welcomed.

[Lisiadito]

Sure I can make a PR for the website links. But it must not be merged before the next release because at the moment the naming is e.g. marktext-setup-<version_number>.exe and would need to be marktext-setup.exe in the future in order to work with the links.

[Jocs]

But it must not be merged before the next release because at the moment the naming is e.g. marktext-setup-<version_number>.exe and would need to be marktext-setup.exe in the future in order to work with the links.

I understand what you mean now, it seems that we need the version number, Sorry for misunderstand what you say.

[fxha]

But it must not be merged before the next release because at the moment the naming is e.g. marktext-setup-<version_number>.exe and would need to be marktext-setup.exe in the future in order to work with the links.

I understand what you mean now, it seems that we need the version number, Sorry for misunderstand what you say.

I don't think so because the version was included by default and we kept it. We could remove it without breaking automatic update because all metadata is in a separate file - AFAIK. Or whats the reason to keep it, @Jocs ?

[Jocs]

I don't think so because the version was included by default and we kept it. We could remove it without breaking automatic update because all metadata is in a separate file - AFAIK. Or whats the reason to keep it, @Jocs ?

I thought about it, it seems that just to distinguish it from the previous version, removing the version number will bring some convenience to the release. If you feel that it is feasible to remove it, you can remove version number in this time of release.