feat(stacks): rework pages + new Jekyll tag - #3812
Draft
Frzk wants to merge 8 commits into
Draft
Conversation
EtienneM
approved these changes
Jul 31, 2026
EtienneM
left a comment
EtienneM
left a comment
Member
There was a problem hiding this comment.
Sorry I missed your request for comments on this PR
A bunch of questions and suggestions but already approving
Member
There was a problem hiding this comment.
I like it! It displays nicely and makes it clear the status of the mentioned stack
Comment on lines
+38
to
+39
| * `resolute` for `scalingo-26` (default) | ||
| * `noble` for `scalingo-24` |
Member
There was a problem hiding this comment.
question: do we want to mention the "default" on this page? I'm pretty sure we will always forget to update it..
Comment on lines
+38
to
40
| * `resolute` for `scalingo-26` (default) | ||
| * `noble` for `scalingo-24` | ||
| * `jammy` for `scalingo-22` |
Member
There was a problem hiding this comment.
suggestion:
Suggested change
| * `resolute` for `scalingo-26` (default) | |
| * `noble` for `scalingo-24` | |
| * `jammy` for `scalingo-22` | |
| * `resolute` for {% scalingo-26 %} | |
| * `noble` for {% scalingo-24 %} | |
| * `jammy` for {% scalingo-22 %} |
|
|
||
| Since the stacks are shared across all applications hosted on the platform, | ||
| they are designed to remain **generic** and **unspecialized**. | ||
| {: #para-one} |
Member
There was a problem hiding this comment.
issue: I don't think this is used
Suggested change
| {: #para-one} |
| stack is identified, a new version is released as quickly as possible. | ||
|
|
||
| - Roughly a year **before** support for the base distribution ends, the stack | ||
| enters its End-Of-Life (EOL) phase. Its status changes from Supported to |
Member
There was a problem hiding this comment.
suggestion:
Suggested change
| enters its End-Of-Life (EOL) phase. Its status changes from Supported to | |
| enters its End-Of-Life (EOL) phase. Its status changes from <span class="stack supported">Supported</span> to |
Comment on lines
+117
to
+119
| | Supported | The stack receives regular updates and can be used for new deployments. | | ||
| | Deprecated | The stack is still supported. Users are encouraged to migrate to a newer supported stack. | | ||
| | Discontinued | The stack no longer receives updates and cannot be used for new deployments. | |
Member
There was a problem hiding this comment.
suggestion: I would style the stack status with the proper class in this table
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
During the work related to the release of scalingo-26 and deprecation of scalingo-22, we noticed with @benjaminach that it was sometimes "hard" to understand what exactly lies behind "supported", "deprecated" and "discontinued".
This PR aims at making this clear by:
Tag usage (notice no
-betweenscalingoand the number!):