Renew documentaion site

[marcushohlbein]

No description provided.

In general, when escaping characters for a specific output format, we must ensure that all metacharacters involved in escaping are handled consistently. For Markdown tables, that means not only escaping the pipe (|) used for column separation, but also escaping backslashes (\) themselves. Otherwise, sequences like \| can turn into \\| where only the | is escaped while the backslash changes meaning, or vice versa, leading to confusing output.

The single best fix here is to extend escapeTableCell to escape backslashes before escaping pipes and performing other replacements. We’ll add a .replace(/\\/g, '\\\\') step near the top of the chain (after the initial null/empty check, and before we start dealing with pipes and whitespace). This ensures every literal backslash in the input becomes a double backslash in the Markdown, so it is rendered as a literal backslash and does not interfere with subsequent escaping of |. No imports or additional helpers are needed; standard string replacement is sufficient. The change is localized to docs/scripts/generate-api-docs.ts, within the escapeTableCell function at lines 51–60.

In general, to fix incomplete multi‑character sanitization involving HTML, either use a robust sanitizer library (e.g., sanitize-html) or ensure that any dangerous characters (<, >, &, etc.) are reliably removed or escaped, not just when they appear inside patterns matched by a specific regex. Here, we only control a small helper, and the output is Markdown table cells, so the simplest safe fix is to strip any remaining < and > characters after we remove recognized tags. That guarantees that partial or malformed tags, or strings like <script that don’t match the tag regex, cannot survive.

Concretely, in docs/scripts/generate-api-docs.ts, adjust escapeTableCell so that after removing <br> and other HTML tags we also strip any residual < and > characters. We will add two additional .replace calls in the existing chain:

• replace(/</g, '') to remove any remaining <.
• replace(/>/g, '') to remove any remaining >.

We will insert these right after the existing tag‑removal .replace(/<[^>]+>/g, ''), keeping the rest of the logic (escaping |, normalizing whitespace) unchanged. No new imports or external libraries are required.

[glushkova91]

@marcushohlbein why can't we simply use readme.md file from components folder automatically generated by stencil on build? why do we need this custom api docs implementation

[glushkova91]

do we use these docs.json files? couldn't figure out so far how are they generated and where they are used. if we use it we need to fix relative paths I think

[glushkova91]

why did you remove release please config? we it replaced with smth or?

[marcushohlbein]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts resolved in commit 7f754da. The conflicts were in core/stencil.config.ts (removed browserHeadless/browserArgs settings that were deleted in main) and pnpm-lock.yaml (accepted main's updated lock file).