Client-First has similar documentation structure built in Webflow.
With the existing URL pattern, there seems to be dynamic nesting of collections — i.e., https://wiki.polygon.technology/docs/pos/reference/contracts/genesis-contracts.
This is not possible in Webflow. Every collection comes with one folder i.e., /blog, /category, etc. If you need to nest, the collection folder can be nested inside of a static page folder.
The static folder name will be fixed. You can nest multiple static folders [screenshot] and then nest the collection template page inside of the static folder [screenshot]. We can’t nest collections inside of dynamic folders, only fixed static folders. More on nesting folders here.
If this will be acceptable, you could set up redirects for entire folders using capture groups for URL patterns that aren’t possible in Webflow (i.e., dynamic nesting).
We don’t have a native solution for switching between CMS items from the collection template page. However, there are a number of solutions, including CMS previous next.
I also noticed dynamic dropdowns in the sidebar. This is also not possible and sort of relates to the dynamic URL structure above. It would require nesting of collections which can only be done once per page and you can only show up to 5 items per nested collection natively. There is a workaround (CMS Nest) to show more than 5 items but the one nested collection per page limitation would still apply. See the following for native dynamic content limitations.
The sidebar navigation would likely be a Component so changes to one instance would apply to all instances/pages, which brings back that limitation of one nested collection per page.
This issue can also be solved with the 301 redirects recommendation mentioned in the URL pattern section.
Custom code would be required to open the relevant dropdown when a link inside of a dropdown is active.
This page could be the category template page which is filtered by the current category. For example, each post can have a reference field to a category and on the category template you could apply a CMS filter to only show CMS items that equal the current category [screenshot]. Next and previous could be used here to switch between the category template pages.
This will also be impacted by the details mentioned in the URL pattern section. You could create your own breadcrumb component by including the path like the home page > category page(s) > post page. Here are some cloneable breadcrumb Webflow sites.
This will require a third-party integration or you could use Code highlighting by finsweet.
This can be done with custom code in rich text or with the Powerful rich text integration which allows you to to insert custom-built elements in Webflow inside of rich text elements. The custom elements can be from the same page or a different page. If from a different page, the page must be live on the site.
This can be done with the table of contents integration by finsweet or using custom code with the intersection observer API + some extra code to look for heading elements inside of the rich text element and create section links accordingly.
I noticed the /search page has an Algolia integration. This is possible with custom code. If you need a reference on how to do this in Webflow, we have demo’s on Algolia autocomplete and instantsearch. We also have related repos explaining how to populate data into the Webflow CMS and how to send and sync Webflow and Algolia data.
You could create an authors collection and have a reference field to it from the posts collection. Then you would select an author for each post.