Josemar Luedke

Yeah, so in Ember, the demos are inserted automatically before the second heading found on the owner page. I could see the benefit of choosing where each demo goes, but...

@bertdeblock That does sounds like a good option.

cc/ @knownasilya.

Is the build time due to Ember or Docfy specifically? I would probably guess this is because of Ember build pipeline. Probably using Embroider + Vite would improve the experience...

Yeah, I thought about this, but I don't like the idea of sending the JSON with HTML/Handlebars over. It would also mean we need to compile templates on the client....

Do you have any resources about this change? We will need to investigate. Probably will restrict what node versions are compatible at least.

@NullVoxPopuli have you seen how the move to ESM affects Docfy? Regarding highlight, it seems we should be using [rehype-highlight](https://github.com/rehypejs/rehype-highlight) moving forward. Have you had success using it?

@NullVoxPopuli I think we should try to upgrade yes. It would be awesome to get the new features. Any change you have cycles to get that going?

@kiwiupover thanks for your interest in looking at this. For development, you do need to build the core first for the types to be generated. 1. `cd packages/@docfy/core` 2. `yarn...

Interesting. I think we need to introduce some type of caching using Broccoli. We probably should also avoid rebuilding Docfy if no markdown files changed, this could be the ultimate...