Ok, this is another topic. I made it dark since the forum and the store have dark theme and i thought the home page was going to have it too. I think you can open a poll or something, honestly it’s the same for me.
This is the css that gets injected into the doc when it is generated.
Yes you are right. So, how should we solve this now that the doc is updated automatically?
Maybe write some code to detect the higher version number (instead of using the github /latest api)?
Or have something in the wiki (eg. a property or a global variable (not sure what our wiki uses)) to update the links when there is a new release?
I don’t know what the process is so I can’t really comment. But in an ideal world, real releases would be marked as such and the docs would either be the latest release (version-wise) or just master.
Edit: and by “marked as such”, I mean that 3.2.5 would be under /3.2.5 and 3.3.0 would be /3.3.0… or if we don’t want to have a ton then just the latest from each branch.
The variable is localized to the document. So all docs with links to wiki would still require updates, basically still at square one unless travis can do it on commits.
Edit: I can set one variable to update them all I believe. Will have to experiment some.