Skip to content
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

[Website] Create a view per version on the website #41

Open
Baklap4 opened this issue Dec 13, 2023 · 2 comments
Open

[Website] Create a view per version on the website #41

Baklap4 opened this issue Dec 13, 2023 · 2 comments
Labels
in-discussion This suggestion is in discussion

Comments

@Baklap4
Copy link
Collaborator

Baklap4 commented Dec 13, 2023

Suggestion

Currently the latest version is shown on the website. However it'd be nice to add previous version also to the website
So we can direct everyone to the correct pages for each specific version

Use case

  • All tags used within a version are made clear
  • it's good for historical purposes

Extra info/examples/attachments

No response

@marwin89 marwin89 added this to the Website is built milestone Dec 14, 2023
@marwin89 marwin89 changed the title Create a view per version on the website [Website] Create a view per version on the website Dec 14, 2023
@Baklap4
Copy link
Collaborator Author

Baklap4 commented Dec 30, 2023

Hmmm to make this easy i think we can create folders per version:

Latest (1.1.0): `/docs/index.html
0.1.0: `/docs/0.1.0/index.html
0.2.0: `/docs/0.2.0/index.html
0.3.0: `/docs/0.3.0/index.html
1.0.0: `/docs/1.0.0/index.html

I guess we can keep the assets (css, js, images, fonts) within the root docs directory and reference them correctly from our index.html

@codello
Copy link
Contributor

codello commented Jan 29, 2024

Is there currently a proposed or accepted feature that significantly changes the syntax of the format? If not I think it would be easier to annotate each of the header fields and note types with a Since and/or Deprecated and/or Removed. For example:

#TITLE
Since: Version 0.1.0

#ENCODING
Since: Version 0.2.0
Deprecated: Version 0.3.0
Removed: Version 1.0.0

This would avoid duplication and still make clear which features are available in which version of the format.

@marwin89 marwin89 added the in-discussion This suggestion is in discussion label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in-discussion This suggestion is in discussion
Projects
None yet
Development

No branches or pull requests

3 participants