Now accepting applications for our next session

Positive points

  • You can mostly tell what it is for
  • You can sign up - and sign in
  • The areas that are public are public - and the private areas for the students is visible when signed in
  • There is an underlaying style system in place that can be updated site-wide
  • It works... for the most part... and we're learning more about what to do next from our experience using it
  • Works well on all device sizes

Pain points

  • It's ugly (which doesn't inspire a lot of confidence)
  • Sign in isn't always easy to find
  • Getting back and fourth between lesson and unit isn't very intuitive
  • The style doesn't have a clear opinion - and feels haphazard
  • Videos should be bigger by default

Missed oportunities

  • If the style was more tuned up it might be taken more seriously

Details

  • On the admin panel side of things (the “backend”) (which is really a “front-end” of its own just for administrators…) Things are shaping up nicely.

    There’s a clear set of resources. Editors can quickly find: posts, lessons, stories, etc – and get to work editing or adding new content.

  • Within each resource type, we’ve set up a robust set of options that allow us to drag around various types of content blocks and build unique content stacks.

  • These are some really great scores for barley trying on that front (yet).

  • We’ll talk more about writing accessible code and what that means – in the course. Here’s an example of how Google’s automated tooling (lighthouse) checks over your website to help you improve it.

  • It’s a small thing… but this little icon (the favicon) in the browser tab – looks bad. We just tossed something there to hold place… but it doesn’t inspire confidence – and the little things sure do matter.

Now accepting applications for our next session