# Topic embedding needs some love **URL:** \ **Category:** Feature\ **Created:** [April 24, 2023, 10:32pm UTC](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763 "2023-04-24T22:32:35Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\ **Post date:** [April 27, 2023, 5:54pm UTC](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763/5 "2023-04-27T17:54:23Z")
The images are now getting pulled in. I’m not great at “spot the difference” types of puzzles, but I’m still seeing some differences: - **Semantic Related Topics** title missing - **Community Sentiment** title missing - missing unordered list in the **Modules Providers** section - **Installing Discourse AI on your community** title missing Ideally, the “Sign up for our newsletter” prompt would be excluded from the embedded post. > [@Falco](#): > > Yes, at this point we either move to something else that makes it slightly better or just change the embedding strategy into making the Show Full Post into a Read Full Post that is a simple link to the original post. Having the ability to easily quote the embedded post seems important. Thinking about that now, I’m not sure what the expected behaviour is when the “expand/collapse” and “go to post” buttons are clicked for an embedded post’s quotes. > [@Falco](#): > > It may be pointless fighting with all the possible embed problems in every website afterall. It’s a tricky problem. It should be as simple as sanitizing the HTML that’s contained in a post’s `article` or `main` element, but I suspect there would still be issues with that approach. For example, it would require some special handling to prevent duplication of a blog post’s `h1` element if the `header` exists inside of the `article`. --- _[View the full topic](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763)._