Who are you button

ijohn commented

2025-11-12 11:46:43 +01:00

Owner

not a drop down, following categories:

end user (individuals)
policy maker
organizations
developer
IT manager
activist

think of "cool" name.

Filter / sort dossiers based on these options on both project and dossier level.

**not a drop down**, following categories: - end user (individuals) - policy maker - organizations - developer - IT manager - activist think of "cool" name. Filter / sort dossiers based on these options on both project and dossier level.

ijohn commented

2025-11-12 11:47:20 +01:00

Author

Owner

Alex also mentioned

I think we need different metadata fields:

project maturity: alpha, beta, mature

target audience: developers, SMEs, government, etc.

software type: cloud vs local

etc.

Alex also mentioned > I think we need different metadata fields: > - project maturity: alpha, beta, mature > - target audience: developers, SMEs, government, etc. > - software type: cloud vs local > - etc.

puer-robustus commented

2025-11-17 14:50:24 +01:00

Member

@ijohn Thank you for noting this down but I think the metadata fields on the different software we list fits in better in #12, where I've left the same note.

@ijohn Thank you for noting this down but I think the metadata fields on the different software we list fits in better in #12, where I've [left the same note](https://git.ngi-0.eu/tech-dossiers/ngi0-landing/issues/12#issuecomment-61).

ijohn commented

2025-12-02 22:58:19 +01:00

Author

Owner

We discussed the categories further with Pavel Smrž and we came to two main suggestions.

These target groups can act as different tags, which would easily add the option to filter out different categories
Or we could add a prefferedAudience field to each dossier / project, buttons with each each audience category at the top and if selected the project with same prefferedAudience would get bumped up in the list, with the remained being still available, but under a divider.

We discussed the categories further with Pavel Smrž and we came to two main suggestions. 1. These target groups can act as different tags, which would easily add the option to filter out different categories ![image](/attachments/97c1c1b2-230a-429f-8b72-cc7f356bfc67) 2. Or we could add a prefferedAudience field to each dossier / project, buttons with each each audience category at the top and if selected the project with same prefferedAudience would get bumped up in the list, with the remained being still available, but under a divider. ![image](/attachments/d066165a-a9f1-4efc-8b0f-7a90bcc630d5)

image.png

32 KiB

image.png

113 KiB

puer-robustus commented

2025-12-04 22:41:33 +01:00

Member

@ijohn

Thank you for your work on this.

Out of the presented options, I strongly prefer Option 2. Small clarifying question: How do the audience filters work: Are they combined via a logical AND or logical OR if two (or more) audiences are selected?

However, neither option is what I understood (maybe I am mistaken) as the goal from our last TD meeting. IIRC we envisioned, that the different target audiences should have a separate page which can give some general background information tailored to that particular group and list the alternatives in the ranking you describe.

@ijohn Thank you for your work on this. Out of the presented options, I strongly prefer **Option 2**. Small clarifying question: How do the audience filters work: Are they combined via a logical AND or logical OR if two (or more) audiences are selected? However, neither option is what I understood (maybe I am mistaken) as the goal from our last TD meeting. **IIRC** we envisioned, that the different target audiences should have a separate page which can give some general background information tailored to that particular group **and** list the alternatives in the ranking you describe.

ijohn commented

2025-12-08 09:50:16 +01:00

Author

Owner

neither option is what I understood (maybe I am mistaken) as the goal from our last TD meeting

If this is the case we should wait for the next meet and clarify it

> neither option is what I understood (maybe I am mistaken) as the goal from our last TD meeting If this is the case we should wait for the next meet and clarify it

ijohn commented

2025-12-08 14:18:52 +01:00

Author

Owner

But maybe this is compatible with the option two. If the audience text is set per audience group we could just output it bellow the audience selection.

In the place of the red asterisk *. Would this work @puer-robustus ?

How do the audience filters work: Are they combined via a logical AND or logical OR if two (or more) audiences are selected?

Thats up to us, both are possible. Currently the tag filters work like AND (adding more tags makes the selection more specific).

But maybe this is compatible with the option two. If the audience text is set per audience group we could just output it bellow the audience selection. ![image](/attachments/275b198c-bdb2-43e1-98d1-ac211fb4849d) In the place of the red asterisk `*`. Would this work @puer-robustus ? > How do the audience filters work: Are they combined via a logical AND or logical OR if two (or more) audiences are selected? Thats up to us, both are possible. Currently the tag filters work like AND (adding more tags makes the selection more specific).

image.png

288 KiB

image.png

288 KiB

tessel commented

2025-12-10 14:52:27 +01:00

Member

Thanks for working on this. I also strongly prefer option 2.

ijohn commented

2026-06-08 18:34:19 +02:00

Author

Owner

I don' think this moved anywhere for a while. Is this still a feature we want in the app?

puer-robustus commented

2026-06-22 10:28:06 +02:00

Member

@ijohn Before implementing this, we should agree on the page taxonomy (#26, #27). That taxonomy should then drive the filters/tag combinations for the site, IMHO.

ijohn added the

enhancement

help wanted

labels

2026-06-23 12:33:19 +02:00

Rows
Columns

Who are you button #13