-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure Julia track is ready for v2 launch #112
Comments
Hello! Thank you for the follow-up.
|
It appears to be missing from the front page of v2.exercism.io as well. The 3 dots logo we use currently updated to the new colours might look better than the full-text logo.
This has been done in #80 and some follow-up PRs. Currently it looks like this:
|
The 2nd paragraph might need an update, I think. It's a bit too technical currently, I think. I'll rewrite it a bit. |
Ah yes! I have an open issue with our designer to get an icon designed that fits with the rest of the icons shown on https://v2.exercism.io (there are several missing icons that we need to add).
Yeah, I think you're right. Thanks for taking that one on! |
* Change the description to be less technical and more friendly (#112) * Extend text mentioning base library with standard library (v0.7 change)
All done, although some parts still need more adjustments (e.g. difficulty, unlock order) but that will be done over time and with more feedback, so I'm closing this for now. |
There are a number of things we're going to want to check before the v2 site goes live. There are notes below that flesh out all the checklist items.
TODO
)core
auto_approve: true
Track landing page
The v2 site has a landing page for each track, which should make people want to join it. If the track page is missing, ping
@kytrinyx
to get it added.Blurb
If the header of the page starts with
TODO
, then submit a pull request to https://github.com/exercism/julia/blob/master/config.json with ablurb
key. Remember to get configlet and runconfiglet fmt .
from the root of the track before submitting.About section
If the "About" section feels a bit dry, then submit a pull request to https://github.com/exercism/julia/blob/master/docs/ABOUT.md with suggested tweaks.
Formatting guidelines
In order to work well with the design of the new site, we're restricting the formatting of the
ABOUT.md
. It can use:Additionally:
<br/>
can be used to split a paragraph into lines without spacing between them, however this is discouraged.Code example
If the code example is too short or too wide or too long or too uninteresting, submit a pull request to https://github.com/exercism/ocaml/blob/master/docs/SNIPPET.txt with a suggested replacement.
Exercise metadata
Where the v1 site has a long, linear list of exercises, the v2 site has organized exercises into a small set of required exercises ("core").
If you update the track config, remember to get configlet and run
configlet fmt .
from the root of the track before submitting.Topic and difficulty
Core exercises unlock optional additional exercises, which can be filtered by topic an difficulty, however that will only work if we add topics and difficulties to the exercises in the track config, which is in https://github.com/exercism/julia/blob/master/config.json
Auto-approval
We've currently made any hello-world exercises auto-approved in the backend of v2. This means that you don't need mentor approval in order to move forward when you've completed that exercise.
Not all tracks have a hello-world, and some tracks might want to auto approve other (or additional) exercises.
Track mentors
There are no bullet points for this one :)
As we move towards the launch of the new version of Exercism we are going to be ramping up on actively recruiting people to help provide feedback. Our goal is to get to 100%: everyone who submits a solution and wants feedback should get feedback. Good feedback.
If you're interested in helping mentor the track, check out http://mentoring.exercism.io/
When all of the boxes are ticked off, please close the issue.
Tracking progress in exercism/meta#104
The text was updated successfully, but these errors were encountered: