Hey all, Bit of a brain tickler and wondering how people may approach this to sort of give me a hand in the right direction 😅 Im in the process of trying to figure out how to create a listing page which uses filters and filter values that are defined by a content editor themselves and "tagged" onto the child pages that will ultimately live in this overview page. Wondering if anyones tackled this sort of issue before? First initial thought was to create a block list on the overview page with a content tab containing the Filter name and potential values, then a setting tab containing the filter "type" settings, such as - its a radio list, or a checkbox list, or a range slider e.t.c However, im not entirely certain if I could then somehow pull through a block list with "pre values" coming from the parent page onto the child pages themselves. Then i thought about doing it with simple node traversal, by having a "Filters" node, individual children for filter types, then allowing a child page to select from any of these children with some sort of content picker. However, that means that the nodes would technicall be routable via URL and I dont think that'd be the ideal scenario but if I could disable that in some way, that'd be top. Final idea I had was to use the Umbraco Tag property, and use some string manipulation in which the editor could type "filter:type:value" as the tag, and I would then take the tags on my overview page and effectively rebuild up the filter options from that, however I could see that being somewhat expensive if the site grows in size and also requires a bit of knowledge from the editor themselves to set up. Ultimately, if anyone knows of "the way" to do this, id really appreciate the advice 😄

I think I remember a project where we just used a node structure (filter > option) the filter had the render type property, and then a multinode picker to choose filters on the list page? beware the editor who has a 50 option radio button list. 😉 think it used to be no template available to be set then no routeable url?

Yeah I remember doing similar back with NuPickers a long time ago. Think it might well be the way I have to go this time as well! Indeed, theres always that danger 😛 Sadly re: Removing urls, seems to (Atleast on 13) create a routable URL regardless of no template set. Id guess that might have changed after the introduction of IPublishedElements

I think Contentment is a great solution for this. You can use custom data lists that you create manually or that can pull from content trees - they can be radio boxes, checklists, or even searchable lists for particularly long options 🙂

Hi Janae! We actually have Contentment installed so definitely a good shout to re-use its capabilities, Just need to figure out how to make the data source "Unroutable" if I were to go the Node based route.

I'm sure there's a clever solution to that, but... we put items we want to allow clients to edit like this in a data folder, and don't assign them templates and they aren't included in the site map so there's not really any content/urls to scrape on the site for them. It's not something we particularly worry about due to that