The track landing page has a code example on it next to the introductory text, in order to give people a taste of what the language looks like. E.g.
Since we have code that knows how to find out which exercise is the first (core) exercise, and which file is the solution file, we can script a PR to each track to create a reasonable default with this file.
In the future, some tracks might want to simplify or choose a different example, which is fine.
The example will ideally be 6-10 lines long and <=40 chars per line, and will be stored in the docs/SNIPPET.txt file.
If intro examples are longer than this, we will automatically cut it off at 10 lines when displaying it on the site.
The track landing page has a code example on it next to the introductory text, in order to give people a taste of what the language looks like. E.g.
Since we have code that knows how to find out which exercise is the first (core) exercise, and which file is the solution file, we can script a PR to each track to create a reasonable default with this file.
In the future, some tracks might want to simplify or choose a different example, which is fine.
The example will ideally be 6-10 lines long and <=40 chars per line, and will be stored in the
docs/SNIPPET.txtfile.If intro examples are longer than this, we will automatically cut it off at 10 lines when displaying it on the site.