Enter your suggestions in details:
The current previous releases page features a limited table that only displays earlier versions of Node.js. We plan to redesign this page to showcase all previous versions, including both major and minor releases, and to provide direct links to their respective download pages.
By default, the table will still only display major versions. It will include information across several columns, such as the N-API version, Major Codename, initial release date, and the last updated date. On the right side of the table, we will redesign the links into a button labeled "Details."
Clicking the "Details" button will open a modal window (cc @canerakdas to bring back the Modal component). This modal, which will function solely on the client side, will contain a table listing all minor versions associated with the selected major version.
At the top of the modal, we will display important and relevant links to blog posts and other resources. Below this, the table will provide a list of all minor versions along with pertinent links, such as "API Docs" and "View Release," which will redirect users to the relevant blog post for each minor version. This approach is similar to how Python manages its minor releases by linking them to blog posts, which include all the download links users typically seek. The links will direct to the bottom of the blog post, specifically to the Download links section.
Of course, this design can be discussed further. Additionally, we would like to incorporate badges such as "EOL," "Maintenance LTS," "Current LTS," and "Current" in the main table. These badges will help inform users about the status of each version, indicating whether it is end-of-life (EOL) or represents the current Long-Term Support (LTS) version.
Enter your suggestions in details:
The current previous releases page features a limited table that only displays earlier versions of Node.js. We plan to redesign this page to showcase all previous versions, including both major and minor releases, and to provide direct links to their respective download pages.
By default, the table will still only display major versions. It will include information across several columns, such as the N-API version, Major Codename, initial release date, and the last updated date. On the right side of the table, we will redesign the links into a button labeled "Details."
Clicking the "Details" button will open a modal window (cc @canerakdas to bring back the Modal component). This modal, which will function solely on the client side, will contain a table listing all minor versions associated with the selected major version.
At the top of the modal, we will display important and relevant links to blog posts and other resources. Below this, the table will provide a list of all minor versions along with pertinent links, such as "API Docs" and "View Release," which will redirect users to the relevant blog post for each minor version. This approach is similar to how Python manages its minor releases by linking them to blog posts, which include all the download links users typically seek. The links will direct to the bottom of the blog post, specifically to the Download links section.
Of course, this design can be discussed further. Additionally, we would like to incorporate badges such as "EOL," "Maintenance LTS," "Current LTS," and "Current" in the main table. These badges will help inform users about the status of each version, indicating whether it is end-of-life (EOL) or represents the current Long-Term Support (LTS) version.