-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move older shader versions to new .md #37
Comments
It doesn't seem necessary to separate the documentation for the old and new versions of the shaders. (From a management perspective, separating the documents would make it harder to manage.) |
makes sense. i went through the readme today and i felt that links to older version makes the md look messy. i mean lets assume a shader has 100 older versions, then you will have to add 100 extra lines in the same md. instead what i wanted is something like this
in README it would look like this:
and in oldversions.md
i suggested this because:
|
Although I am in a fast internet environment with 5G, I am not sure if having many links or lines significantly slows down the loading speed of the document. If this truly causes a noticeable lag, it is certainly worth considering. From a management perspective, although these aspects can make pull requests challenging, this is not a concern for the majority of users. As long as the document loading speed is not slowed down, I do not currently plan to change this aspect. |
Most people will download only the latest version and not care about older versions.
You may want to move all the older version links to another .md
and also leave a link to the same #title of the new.md
by doing this, the readme.md will become easier to read and write. currently, it's easy to get lost in dozens of older links.
The text was updated successfully, but these errors were encountered: