# Build embedding / onebox support for topic filters

**URL:** https://meta.discourse.org/t/build-embedding-onebox-support-for-topic-filters/375564
**Category:** Feature
**Tags:** topic-filter
**Created:** [July 24, 2025, 4:28am UTC](https://meta.discourse.org/t/build-embedding-onebox-support-for-topic-filters/375564 "2025-07-24T04:28:51Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![thoka](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thoka/32/115652_2.png) [@thoka](https://meta.discourse.org/u/thoka)
#### Post date: [July 24, 2025, 5:30am UTC](https://meta.discourse.org/t/build-embedding-onebox-support-for-topic-filters/375564/5 "2025-07-24T05:30:08Z")

</div>

> [@sam](#):
>
> How many topics should it show (how do you control that)

There could be output formatting options like `limit:5` and `format:with-summaries` to start with.

As

> [@Filtering topic lists in Discourse](https://meta.discourse.org/t/filtering-topic-lists-in-discourse/375558/1):
>
> The feature supports plugin extensions for custom filters

the output could be transformed with other plugins with their own formatting language / options (for example a list of columns to show).

> [@sam](#):
>
> How “dynamic” is the list? How often is it updated

What are current rules for oneboxing regarding this question?

Since the result is filtered with the users individual rights could one consider caching the unfiltered result and a filtered result for anonymous users, applying permission checks on demand for users with more rights?

Current internal oneboxes have the option to be expanded.  
A similar approach might update the cached version on demand (with throttle).

---

_[View the full topic](https://meta.discourse.org/t/build-embedding-onebox-support-for-topic-filters/375564)._