search

foundeo / cfdocs

Repository for the cfdocs.org site.
https://cfdocs.org/
Other
180 stars 341 forks source link

By Engine #583

Open shaedrich opened 6 years ago

shaedrich commented 6 years ago

Should we add "functions and tags by engine" to navigation?

Then we would have something like

but just the supported ones grouped by their engine.

KamasamaK commented 6 years ago

This sounds like a great idea

shaedrich commented 6 years ago

@pfreitag @KamasamaK We only have engine version listings but no engine listing. Should we have a listing, which have sub listings?

We cannot render all functions and tags by engine to the navigation dropdown.

pfreitag commented 6 years ago

Not sure exactly what you are asking here. Is it the ability to have a parent child listing relationship?

shaedrich commented 6 years ago
  1. Yup, the engine listings would be parents for the version listings
  2. As you see in my comment from October 11 I thought of the result as a structure like mentioned above. But this does not work with plain bootstrap. So we have some possibilities:
    • Extending bootstrap for sub nav items
    • Use headers for engines
    • Only render engines as items and link to the listings

The first two points should only take a list of approximately five items plus an item like "more…". Otherwise the list could become very long.