GitLab

Add missing extensions and images

Issue/2281 gettingstarted

2018 Hour of Code Banners

Fix wedo-legacy translations

Redo the credits page.

Move sharing to special endpoint.

Hide backpack for logged out users

Update microbit hex file version

Pass authorId and authorUsername to gui

The API endpoint will return just the updated slice of the projectInfo, so just update the projectInfo instead of replacing.

This makes a couple of assumptions about the shape of the endpoint:
- Route is /proxy/projects/:id/share.
- Returns the full (updated) project info on success, just like the project update endpoint does.

I reviewed these with colby since this is frontrunning the actual API, but I can update once the API is finalized.

The translation generatation script uses the view name from the routes file when generating the translations files. So the route `name:` and `view:` must match.

Symptom: when generating translations there were warnings that there were no translations for `wedo-legacy`.

- `create` on the navbar opens the getting started tutorial if the user is not logged in
- replaced any other use of `tip_bar=getStarted` with `tutorial=getStarted` (with the exception of Tips page)
- did not replace other uses of `tip_bar=home` as those should probably go to the new tips/ideas page.

Preview needs to be able to handle query parameters for tutorials.

Removes Full Stack Job Listing

Use https for ScratchJR links

Add "project not available" view for when project body cannot be loaded

* add Top and Middle HoC banners
* banners share styles
* add new assets for banners
* update presentation to check date to determine whether to show the HoC banners.

This happens when the project id does not exist, or is not visible to the given user.

Avoid displaying an error when /news returns a 500

Update chromedriver so tests pass more reliably

Add IP Mute message to project comment errors

Add new strings in preparation for Hour of Code

This situation probably occurs most frequently when running dev servers while offline, but could also happen if the API is having issues. 500 responses from the API should not take down the homepage so drastically, and are also sometimes unavoidable while working offline.