* 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>
This PR makes it possible to browse integrations, organizations and related softwares. Previously, these details were only available as modals on the ecosystem page.
There are also some changes to the policy enforcement on the docs content, the validation rules are much the same but have been updated to reflect that the content is stored in a new place. I have used some generated JSON in Hugo rather than using GitHub api requests to validate the files since it's A) faster, B) I think more simple, and C) easier to get Hugo to process the markdown frontmatter.
Much of the hackery in this PR (Hugo function partials to look up sets of files and get the data from them) is due to the fact that we can't use Hugo's native sections feature. All of our content is nested under docs, this means that all our pages are in the same section so custom lookups have been implemented as function partials instead to work around this.
Signed-off-by: Charlie Egan <charlie@styra.com>
* [docs/website] Link to OPA Ecosystem from docs
This PR makes the following changes to the website Ecosystem content and
linking:
* Creates and assigns categories to various projects where information
is available.
* Displays top level categories on Ecosystem page
* Links to categories from various relevant locations within the docs.
* Embeds related Ecosystem projects at the ends of some docs pages where
there are fewer than 6 and all have related content to the page in
question.
* Implements Hugo partials and shortcodes to make this extensible in
future.
* Updates to ecosystem projects to keep them current
* Adds various, previously unlisted, OPA ecosystem projects
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>
I have used JPGs to make the images smaller.
A wider image is used for the larger breakpoint.
Menu moved into header to make spacing easier to
achieve without height: 0 and other hacks.
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>
This commit migrates the security policy to the OPA website. Also, it is
deliberately not part of the versioned docs; we don't want anyone to find old
information when it's important to get up-to-date information.
Fixes#4272.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
* Fix inconsistent spacing in community.css
* Fix background on community page so it doesn't become white when scrolling
The white background happened because it was forced to a height of the viewport,
but the overflowing child elements were still visible. Because its a parent
element that scrolls, the background would scroll with the page causing the
white background to appear.
The culprit is setting `height: 100%`, which means it won't pick up the height
from its child elements. If instead we set `min-height: 100%` it'll be at
minimum the height of its parent (`<body>`, which along with `<html>` is set to
be `100%` of the viewport width and height – this is probably not ideal) but it
can still expand to fit all its child elements.
There are other ways to fix this, but this is probably the minimally invasive.
* Make dividers no push beyond the viewport width, and more responsive
The dividers will no longer push beyond the viewport width with these changes
(key culprit: the `-1em` left/right margins) and also will disappear on smaller
screens so they don't become very thin.
Signed-off-by: Marcus Stade <marcus@styra.com>
This PR adds the Emissary ingress to the Ecosystem page.
The blog section contains link to an article which guides on Emissary ingress and OPA integrations.
Signed-off-by: Tayyab J <tayyab.jamadar@styra.com>
* remove hugo templating
This page doesn't go through hugo at all, so these things would
end up on the website.
A quick fix is reverting the bits that added the templating. The
downside is that local dev and PR previews will link to
/docs/latest/ecosystem, which doesn't exist there.
* link Documentation and Download to /docs
For /docs/ (not /docs/latest) we have a redirect in local dev and
PR preview mode:
/docs -> /docs/edge
so this will be a little less broken: only ecosystem is a 404 link
on the preview.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
With this change, the work done for local development, and the per-PR netlify preview changes:
It will no longer include the website stuff for versions other than edge, the current working tree.
We thus save us the time, and the flakiness, involved with
- checking if github has release binaries for all the versions
- checking out their sources
- fetching the release binaries to pre-hydrate old versions' live-blocks.
The previously-used, documented make target should still be intact.
Fixes#4379 to some extent, I hope.
* docs/website: remove "latest" binary from opa versions cache
Having a stale binary here -- one called "latest" but not actually
being "latest" -- causes issues like this: when building the website
content for the (real) latest version, the script would take the
old (previous-latest) binary, and fail because that binary didn't
know the latest future keywords.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
Matthew A Johnson