paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

Ran prettier:fix

Browse Source 
Signed-off-by: Andre Wanlin <awanlin@spotify.com>
This commit is contained in:
Andre Wanlin
2025-10-15 16:10:34 -05:00
parent 6e2c8b94f8
commit ab86a8f021
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
microsite/blog/2025-10-15-backstage-contribfest-kubecon-guide.mdx
+6 -6
View File
@@ -13,9 +13,9 @@ Pack your laptop and mark your calendars! Backstage will once again be taking pa
## Contrib-what?
Before we dive into preparation for the Backstage ContribFest session we should probably take a detour and answer the question: What the heck is ContribFest?
Before we dive into preparation for the Backstage ContribFest session we should probably take a detour and answer the question: What the heck is ContribFest?
ContribFest is a track at KubeCon where various CNCF projects will host hands-on sessions working with their respective communities on contributions towards their projects. You don't have to be a past contributor to participate — new community members are encouraged to join!
ContribFest is a track at KubeCon where various CNCF projects will host hands-on sessions working with their respective communities on contributions towards their projects. You don't have to be a past contributor to participate — new community members are encouraged to join!
These sessions are 75 minutes long and take place in a room with roughly a dozen circular tables that seat about eight people making it easy to work and collaborate. They usually lead off with some getting started steps and then give attendees the rest of the time to work on their contributions with the aid of experts from the project.
@@ -28,15 +28,15 @@ For the Backstage ContribFest session, there are some preparation steps you can
You'll have the option to contribute to the Backstage repo or the Backstage Community Plugins repo. To get those onto your system, you need to follow the GitHub ["Forking a repository"](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo#forking-a-repository) guide and fork these:
- Backstage: [https://github.com/backstage/backstage](https://github.com/backstage/backstage)
- Backstage Community Plugins: [https://github.com/backstage/community-plugins](https://github.com/backstage/community-plugins)
- Backstage Community Plugins: [https://github.com/backstage/community-plugins](https://github.com/backstage/community-plugins)
### 2. Update Node.js and Yarn
Backstage has [a few prerequisites](https://backstage.io/docs/getting-started/#prerequisites) that you'll need to have in place before you can run Backstage or the various Backstage Community Plugins. Here's what you need:
- Backstage uses Node.js — you'll want to install version 22 for the session.
- To make this easier, we recommend you use Node Version Manager nvm, you can [follow these instructions to install it](https://github.com/nvm-sh/nvm#install--update-script).
- Once you have nvm installed, you can run this command to get Node 22 installed and activated: `nvm install 22`
- Backstage uses Node.js — you'll want to install version 22 for the session.
- To make this easier, we recommend you use Node Version Manager nvm, you can [follow these instructions to install it](https://github.com/nvm-sh/nvm#install--update-script).
- Once you have nvm installed, you can run this command to get Node 22 installed and activated: `nvm install 22`
- Yarn is the package manager used by Backstage — you'll want to install it as well.
- Simply run `corepack enable` to do so.