Andre Wanlin

You'll want to use a new Backstage instance created following the guide that Adopters would use to start - https://backstage.io/docs/getting-started/ - so the results of running: `npx @backstage/create-app@latest`

Hi @jrkt, TechDocs uses the [DOMPurify](https://github.com/cure53/DOMPurify) library to sanitize HTML and prevent XSS attacks. Pretty sure this is what you are running in to.

You are right, this doesn't even come into play until you run TechDocs: https://github.com/backstage/backstage/blob/6e14fefe5344653c09b80a99de7d73a9882672f8/plugins/techdocs/src/reader/transformers/html/transformer.ts#L39 You are seeing this issue before that based on your description.

Could something in `techdocs-core` MkDocs plugin play into this? https://github.com/backstage/mkdocs-techdocs-core

Unless you are using the `--omitTechdocsCoreMkdocsPlugin` flag the `techdocs-core` plugin gets added to the `mkdocs.yml`. Your comment - "It's like it is ignoring that plugin" - made me think maybe...

So the `techdocs-core` plugin is not optional, you need it for TechDocs to work. The docs for sure don't make that as clear as they could, or really at all....

Hi @jrkt, I've reached out to the TechDocs team to see if they have any ideas.

Hi @Al-Serhan, this makes sense to me. Just so I'm on the same page you mean adding details about running `yarn new` to create the package with things nicely setup...

OK, great, I think this is a great idea. These docs dive right into the deep end so would appreciate you adding some of the steps before you get to...

Thanks @nia-potato 👍