Maximilian Franzke

@ringods first of all thanks a lot for your work that you did so far regarding this topic. I tried to follow up on the feedback by @JosefBredereck and checked...

We're mentioning preprocessed files like SCSS now in the docs: https://patternlab.io/docs/managing-pattern-assets/#heading-preprocessed-files

So we need to further add informations that are defined in the section https://github.com/pattern-lab/patternlab-node/tree/dev/packages/cli#configuring-your-project-to-use-the-cli as well as the following one called "API & Usage"

> Actually this would be really neat and has a lot of potential. I imaging that the export as HTML could/should even include semantics helping developers and designers to increase...

To my impression code highlighting just wasn't expected to work / targeted at anything else than the code panels so far. So we most likely only need to decide on...

@JosefBredereck maybe I do have a misunderstanding here, but if I do open e.g. https://patternlab-handlebars-preview.netlify.app/?p=all the HTML code gets its highlighting:

> Yes, but not the content of the description. > > Take this for example: https://lab.n8d.studio/htwoo/htwoo-core/?p=atoms-grid > > > > It has somewhat rendered syntax highlighting, just the 'code' styles...

> remove outdated packages (uikit-polyfills, engine-react, development-edition-engine-react) Is removing `engine-react` and related packages very important to you? I could think about that actually updating and finalizing these react related packages...

> @mfranzke how can we find the remaining cases? The regexp you posted doesn't work with `git grep -E`. sorry, I should have mentioned this (and just adapted it to...

I've only found one remaining occurance: https://github.com/mdn/browser-compat-data/pull/22287