Developer forum

Hi Carsten,

Yes. Awesome. That's exactly what I need.

Thank you guys.

Adrian

I'm working with it myself these days, leading up to a planned rewrite of the indexing documentation. And of course to make searches on this portal less cumbersome. So I expect I will encounter quite a few bugs along the way - let me know if you find any :)

Hi Carsten,

That very nice to hear. Looking forward to your findings.

Can you share with me how you managed to handle large amounts of content/pages in this documentation site?

Have you found a way to exclude the pages from the tree menu and make it easier for you to find them/sort them in the structure?

I am just starting the analysis for a publishing project and they currently have about 3000 articles with plans to reach 10.000 articles in the next 6 months.

That's a challenge for the current way of working with content. I assume you have similar challenges.

Thanks,

Adrian

I haven't gotten that far with the actual query yet, as I am waiting for a bug to be fixed - but here's a rundown of how I built a data structure to help me out.

• On the docsite, each area (Getting started, DW8 manual, DW9 manual, etc.) is a separate website - so that's the first thing I can create a facet on
• All regular content (non-forum, non-template tags site) is based on a page item, and I use a radio button list to mark content as either:
  • an article 
  • a container (with no content, excluded in my query)
  • a how-to (placed in a folder and published in different ways using an item publisher).
• All articles are categorized using item-based category and keyword page items (with a single text field):
  • Categories (e.g. Ecommerce, Users, Marketing) may have keywords under them. For instance, the Marketing category has the keyword items Email Marketing, Leads, Personalization, Split tests, & Social media under it. I build a sort of hierarchy in the tree structure (see attached)
  • On the page item type, I created a list of checkboxes corresponding to the categories - and a matching number of groups of keywords which fold out if the appropriate category is checked (see attached)
• On a page item, the editor will then be able to categorize and tag the article as they see fit (see attached)

All of this gives me a large degree of control over what I want to display in my search results using the query publisher. I built this when I started here about two years ago, and it has only now become useful to me - but you know, I like to keep all my ducks in a row, so I have been strict with keeping things categorized and tagged from the beginning, which lessens the workload now. If you have to build this from scratch with a large amount of content it's going to take a while.

The idea is that tags may be created more or less freely by editors, wheras categories are a way of forcing the data structure to be a little more strict than I imagine it would otherwise be a few years down the line.

Originally I wanted how-tos to be published in appropriate locations on the docsite by auto-matching the categorization of the article and the how-to, but I have better ideas than I have implementation skills ;)

@Carsten @Adrian - I am working on a similar search using the new index, query and querypublisher to show categorized search results.

Any news regarding how to build these searches as of now?

BR Hans

Unfortunately I have not had the time to work more on this recently, but we do have an improved ContentIndexBuilder in the works which should make it easier to do cool things with indexed item content.