Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embed view - allow filtering by Status #628

Open
jmertic opened this issue May 13, 2024 · 4 comments
Open

Embed view - allow filtering by Status #628

jmertic opened this issue May 13, 2024 · 4 comments

Comments

@jmertic
Copy link

jmertic commented May 13, 2024

It would be great if the same filters on the main view could be applied to the embed view. One in particular is 'Status'; this lets us embed a list of projects in a specific foundation, which landscapeapp can do. LMK if you have any questions on this - thanks in advance!

@tegioz
Copy link
Collaborator

tegioz commented Jan 8, 2025

Adding a status filter sounds interesting @jmertic, we're running some tests to see how it might fit.

Quick question: would this be something you'd like to use in the context of a category or across multiple categories? At the moment the embed view is restricted to display a single category, but we understand a feature like this would be more useful if it worked across categories.

Please note that the landscape is a fully static site, with no backend at all. At the moment the embed views are powered by a number of datasets that we generate during the landscape build (per category and subcategory). This way embed views only pulls the data they need, based on the category/subcategory that will be displayed.

Any sort of filtering we introduce will need to take place in the client side. And pre-generating datasets won't be an option anymore, as the number of combinations will explode. So unfortunately, we may need to pull a larger dataset (even all items, if we make it work across categories), to just display a subset of them.

We'll you know how the tests go 🙂

@jmertic
Copy link
Author

jmertic commented Jan 8, 2025

Status is a common filter which if you wanted to do any one, that would be the one to do :-)

@tegioz
Copy link
Collaborator

tegioz commented Jan 9, 2025

We've been playing with this a bit but we're not very happy with the results. Applying the status filter on a single category / subcategory is very limiting and not very useful. Applying it across all categories requires pulling a lot of data to handle the filtering on the client, which isn't very efficient. On top of that, in the UI doesn't look great either, as the current classification is per category/subcategory, so depending on the status selected, many of them show almost empty.

We need to find a better way to handle this, a way that can work well with pre-generated datasets.

Maybe, instead of a filter, we could consider adding support for additional classification options. At the moment the embed is fully based on categories, but we could have an additional classification, by maturity (aka status). This would be pretty similar to what we do in the card view mode at the moment (screenshot below), and would allow to easily embed all items that match a specific maturity or all of them. The header of each block would be the maturity, instead of the category. And we'd be able to generate a dataset for each maturity in advance, which would allow us to only pull the data we need.

Image

@jmertic
Copy link
Author

jmertic commented Jan 9, 2025

As long as this could be able to be a filter for the embed, this would be perfect. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants