Add AST workshop to workshop catalog

[nickschot]

I've written an initial version of the content necessary to add the AST Workshop to the Workshop Catalog on the website.

Couple of points left:

• Images
• Discuss Handlebars name
• Discuss duration of workshop
• Double check what description & introduction fields do (they have the same content right now).

[nickschot]

The workshop still talks about it like this, but I think we have a different name for it nowadays? cc @mansona since I don’t fully recall if the core teams settled on a name for glimmer template syntax.

[mansona]

I mean that can be a topic that we talk about when giving the workshop 🤷 I mean we still use the handlebars parser, we call it htmlbars internally, the package that has info about the syntax is @glimmer/syntax so really it doesn't matter what we call it

[nickschot]

Then let's keep it like this to stay consistent with the current workshop terminology.

[nickschot]

This was originally given as a 1/2 day workshop at EmberConf 2020. There are however a bunch of optional exercises which could stretch it. What do we want to do here? I've never attended nor given the workshop as far as I remember, so I can't really estimate this.

In the future the workshop could also be extended a bit more by adding auto-fixable eslint rules at the end, meaning all concepts are applied to both Handlebars and ESlint.

[KevinBongart]

Let's make it a 1 day workshop

[nickschot]

Preview here: https://deploy-preview-2859--objective-northcutt-37494c.netlify.app/services/workshops/ast-workshop/

For some reason I don't see it appearing under https://deploy-preview-2859--objective-northcutt-37494c.netlify.app/services/workshops yet, is it not automatic?

[KevinBongart]

@avollrath We could use your help to replace the image header here https://deploy-preview-2859--objective-northcutt-37494c.netlify.app/services/workshops/ast-workshop/ @nickschot @mansona any suggestions?

[nickschot]

@avollrath We could use your help to replace the image header here https://deploy-preview-2859--objective-northcutt-37494c.netlify.app/services/workshops/ast-workshop/ @nickschot @mansona any suggestions?

There is some potential inspiration in the slides: https://github.com/mainmatter/ast-workshop#abstract-syntax-forestry

[avollrath]

Option A	Option B
Option C	Option D

I did a few explorations for the AST workshop hero image and narrowed it down to these four. They all explore branching structures and hierarchy, but with varying levels of abstraction.

Thoughts? Which direction feels strongest for the workshop?

Also, who should make the final call on the image selection?

[KevinBongart]

Thanks Andre. Let's go with option D: Mainmatter colors, nice image, not too foggy, and very relevant to the workshop

[avollrath]

I added the new hero image, also made an og:image and added the workshop to the workshops list at last position (can be changed in workshops.njk)

All pushed to this branch

[KevinBongart]

@marcoow Do you want to take a look or should we merge it as is?

[marcoow]

We should make this framework-independent (which was the work that Stan did years ago before this had stalled) – much more valuable if this isn't an Ember-only workshop.

[KevinBongart]

@marcoow There is an old PR (https://github.com/mainmatter/ast-workshop-presentation/pull/12) to make the workshop more generic but we don't know yet how far along this work went, nor its quality. I recommend we ship it as is (Ember specific), since it's ready, and then decide whether we want to invest more 20% time in making this workshop more generic

[marcoow]

I see. We don't actually need to have the workshop to put a landing page online though – we can always make the workshop when someone inquires it. I think this would have substantially higher value as a framework-independent landing page only than as an Ember-specific landing page plus workshop packages