Launch Tracker 🔴

[ErikSchierboom]

This issue is part of the migration to v3. You can read full details about the various changes here.

To get your track ready for Exercism v3, the following needs to be done:

• Configure online editor
• Add key features
• Add tags
• Add prerequisites to Practice Exercises
• Update status of track
• Update status of Concept Exercises
• Pass linting checks
• Build Test Runner
• Build Analyzer and Representer (optional)

This issue may be automatically added to over time. While track maintainers should check off completed items, please do not add/edit items in the list.

Tracking

exercism/v3-launch#7

[lpil]

Hi @ErikSchierboom ! What's the recommended number of practice exercises to have prior to launch?

[ErikSchierboom]

@lpil 20-ish. I've just checked, and there are 24 already:

erik@schierheim:~/exercism/gleam$ jq '[.exercises.practice[] | select(.status == null or .status == "active")] | length'  config.json
24

[lpil]

Fab! Is there anything left to do?

[ErikSchierboom]

Nothing that blocks launching I think! 🎉

Looking at the new tracks docs, after launching the track, I think the next steps would be:

1. Add more practice exercises
2. Configure lines of code counter (https://exercism.org/docs/building/tracks/new/configure-tooling)
3. Configure snippet extractor (https://exercism.org/docs/building/tracks/new/configure-tooling)
4. Create highlightjs plugin
5. Create codemirror plugin
6. Build representer (will only really become useful once you have a fair number of submitted solutions)
7. Build analyzer

The first one is the most important one, but you might want to choose other steps to work on in parallel. From a student's viewpoint, the highlightjs plugin and codemirror plugins are probably the most impactful ones. We have people that have built these plugins for other tracks, so feel free to ask for help on the forum.

[lpil]

Wonderful! Thank you!

[ErikSchierboom]

@lpil Is there anything you'd like to do before going live? From my viewpoint, we're ready!

[lpil]

All good to go I think! 🥳

[ErikSchierboom]

@lpil Then I'd like to give you the honor of opening the PR to set the active property to true in the config.json file.

[lpil]

@ErikSchierboom There is a highlightjs plugin for Gleam here on npm

[lpil]

I've had a look at the lines of code counter repo and I believe there is nothing to do for Gleam as the test module path is in specified in the config json file.

[ErikSchierboom]

There is a highlightjs plugin for Gleam here on npm

I'll get that sorted out next week

I've had a look at the lines of code counter repo and I believe there is nothing to do for Gleam as the test module path is in specified in the config json file.

You're right, it is indeed listed in the supported languages: https://github.com/XAMPPRocky/tokei/blob/master/languages.json

[ErikSchierboom]

@lpil PR opened: exercism/website#3411