* 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>
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>
- Added two more community champions
- Removed enterprise support from community page
- Changed blurry line to solid line
- Updated newsletter signup from Medium to Mailchimp
- add hugo lock to gitignore
Signed-off-by: Peter ONeill <peteroneilljr@gmail.com>
- remove my-item (unused)
- remove aria-pressed="true"
- use FA for twitter/github icons
- cleanup footer
- drop txt templates
For now, maintaining an extra manual templating mechanism does not
seem like the right move: if we find ourselves in the need to replace
the static HTML page, we can move stuff over to Hugo's data templates.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
Correct CSS for easy local static viewing
With this tweak, can just open local support.html in the browser
Revise flex container for 2-up
Define tile layout
Add page header (with suggested text)
Swap Community for Support across site
Swap anchor for button
Advantages:
- removes JavaScript dependency; now pure HTML
- more accessible; confusing to have a button act like a link
Add stylized horizontal rule
Fill out remaining horizontal rules
Add data and images for the page
The data has been normalized to allow a semi-automated fill of an HTML
fragment template in the next commit.
Semi-automated template for data generation in vim
Fill out page from semi-autogenerated content
Now take the generated content and cut-and-paste the content
for each section into the support.html file.
Refine layout with actual content now present
Have to make the section headers readable on the two
backgrounds: near the top--where the background image
appears--we use white text, but in the remainder
of the screen (with a white background) we use blue text.
Add connection to existing newsletter sign-up
Accessibilty refinements
Ran axe accessibility checker (Chrome extension) and fixed:
- All content in landmarks
- Main landmark present
- Content structured with <h1> and <h2>
- Images have alternate text
- Links have discernable text
Add back original support blurb
Improve responsive design
Switch from bootstrap to CSS grid to better handle reflow
into narrow screen width
Move new page to community.html
Reinstate original support page
Correct relative addresses
Add reference to new page in old page
Refine responsive design
On mobile, last pass reduced to one column,
but the individual cards were still truncated.
Fixes near bottom: action buttons and page margin
Spruce up the background image a bit
Per @srenatus' suggestion, keep the background image
(actually, two images)
stationary--with a bit of a color shift
that came along for the ride! :-)
Add github and twitter logo links for champions
Signed-off-by: Michael Sorens <msorens@styra.com>
Previously, there were no links from the homepage to any of the
more detailed docs about use cases and even mention of use cases
was below the fold.
This change adds links to use cases at the very top of the page,
along with pointers to core docs and the OPA summit.
Signed-off-by: Tim Hinrichs <tim@styra.com>
Charlie Egan
