Skip to content

Commit 11113c9

Browse files
committed
wip: add new ESP partner
1 parent 209a438 commit 11113c9

File tree

4 files changed

+12
-3
lines changed

4 files changed

+12
-3
lines changed

apps/site/pages/en/about/eol.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Major versions of Node.js are released, patched, and designated End-Of-Life on a
1515
<span>Upgrade to the latest LTS Node.js®</span>
1616
</Button>
1717
<span>or</span>
18-
<Button as="a" kind="warning" href="/esp/herodevs" className="flex-1">
18+
<Button as="a" kind="warning" href="#commercial-support" className="flex-1">
1919
<span>Get security support for EOL versions</span>
2020
</Button>
2121
</div>
@@ -42,3 +42,5 @@ Despite the obvious downsides of using EOL releases, in practice, organizations
4242
Node.js currently partners with HeroDevs to provide Never-Ending Support (NES) for Node.js versions past their official maintenance phase. This includes security patches, compliance assistance, and technical support to help bridge the gap while you plan your upgrade strategy. For more detailed information, visit the [**HeroDevs Node.js NES page**](https://nodejs.org/esp/herodevs).
4343

4444
Using EOL releases through NES should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.
45+
46+
Node.js also partners with NodeSource... `<TODO MARKETING COPY>`

apps/site/pages/en/about/partners.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The program provides access to security patches, compliance assistance, and tech
3535
to help bridge the gap while you plan your upgrade strategy. For more information about
3636
End-Of-Life versions, please visit [End-Of-Life Node.js Releases](/about/eol)
3737

38-
> Using EOL releases through NES should be viewed as a temporary solution, the goal should always
38+
> Using EOL releases through commercial support should be viewed as a temporary solution, the goal should always
3939
> be to upgrade to actively supported versions.
4040
4141
<PartnersLogoList categories="esp" maxLength={null} sort="name" />

apps/site/public/static/partners/constants.json

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,5 +33,12 @@
3333
"href": "https://microsoft.com",
3434
"categories": ["infrastructure"],
3535
"weight": 2
36+
},
37+
{
38+
"id": "NODESOURCE",
39+
"name": "NodeSource",
40+
"href": "https://nodesource.com/",
41+
"weight": 3,
42+
"categories": ["security", "esp", "release"]
3643
}
3744
]

packages/i18n/src/locales/en.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@
183183
"ltsVersionFeaturesNotice": "Want new features sooner? Get the <link>latest Node.js version</link> instead and try the latest improvements!"
184184
},
185185
"eolAlert": {
186-
"message": "Commercial support for versions past the Maintenance LTS phase is available through our <link>OpenJS Ecosystem Sustainability Program partner HeroDevs</link>"
186+
"message": "Commercial support for versions past the Maintenance LTS phase is available through our <link>OpenJS Ecosystem Sustainability Program partners</link>"
187187
},
188188
"eolChip": {
189189
"severity": {

0 commit comments

Comments
 (0)