This PR also fixes an issue with `kind` being used in a way that's not
allowed in more recent Hugo versions.
Signed-off-by: Charlie Egan <charlie@styra.com>
In the OPA ecosystem, there are a number of language SDKs for different
general purpose languages, mostly integrating with the REST API. This PR
highlights these at the start of the OPA ecosystem page, adds some other
projects for completeness and clarifies the owner where more than one
SDK for a language exists.
Signed-off-by: Charlie Egan <charlie@styra.com>
At the moment we have some entries with . chars in their ids, this makes
the hugo page look up break, so now these are validated to be
sausage-case-values.
Signed-off-by: Charlie Egan <charlie@styra.com>
This page is intended to be a starting point for users debugging various
OPA issues. It outlines various OPA features that can help narrowing
down issues in one place.
Signed-off-by: Charlie Egan <charlie@styra.com>
* We are having trouble managing the complexity of having ecosystem pages shown in the versioned area of the OPA docs site (see website: link ecosystem from edge #6170)
* We have invested in the OPA ecosystem data recently and it makes sense to make it more prominent.
* The data in the OPA Ecosystem is harder to use when nested in docs as some Hugo functions are unavailable to nested sections.
This PR implements a solution by:
* Pages that were under /docs/version/ecosystem, /docs/version/integrations etc have been moved to /ecosystem and /integrations.
* Redirects have been created for the old pages in the netlify config.
Signed-off-by: Charlie Egan <charlie@styra.com>
* Update awesome opa logo
Signed-off-by: Charlie Egan <charlie@styra.com>
* Add awesome-opa to integrations list
Signed-off-by: Charlie Egan <charlie@styra.com>
---------
Signed-off-by: Charlie Egan <charlie@styra.com>
This is what I have done:
* bring all pages into Hugo structure (security, community, support)
* make styles consistent more consistent with homepage
* merge and try to de-dupe css
* Reduced number of breakpoints to 2, one for mobile and one for larger
This is intended to be a step in the right direction, making the site
easier to maintain and more design consistent. There is much left to do,
some examples of things still to work on:
* The remaining CSS is still very messy and likely has some unused.
* The homepage still has an entirely different Dom for mobile in one section, this is toggled on and off.
* We don't use Hugo to generate any page content from markdown for these pages
* ... the list goes on.
Signed-off-by: Charlie Egan <charlie@styra.com>
Brandt Keller