Closed aepfli closed 1 year ago
Name | Link |
---|---|
Latest commit | 46735cd58230f64add437781f4211f00ccc3e16b |
Latest deploy log | https://app.netlify.com/sites/lucky-creponne-baf9b3/deploys/6422ba8a7336890008ba3e5c |
Deploy Preview | https://deploy-preview-301--lucky-creponne-baf9b3.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
created a suggestion pr for htmltest - to handle this issue with the dropdown - https://github.com/wjdp/htmltest/pull/213
Hey @aepfli, I talked to the GC about this last week. We think that it would make sense to create another top-level category called "Ecosystem". This would be an ideal place to put documentation for OpenFeature Operator, Flagd, and supported vendors.
I've put together an extremely high-level mock to try and move the discussion along.
I can help with the copy. Adding the vendors can be handled in a separate issue.
FYI, @open-feature/governance-board
I looked, and it seems like it is more challenging than we would like to have multi-instance docs within the sidebar. Whereas within the navbar, it is easy.
Additional remark, within the navbar, we can only have one level of navigation, so my suggestion would be something like
It is a compromise between both approaches, what do you think?
I've created an issue to create an ecosystem page. I think we can explore this PR again once that page is available.
Added flagd via dropdown to the official documentation page, like we already did with community etc.