Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Envoy Documentation Update #160

Merged
merged 6 commits into from
May 9, 2024
Merged

Envoy Documentation Update #160

merged 6 commits into from
May 9, 2024

Conversation

bbengfort
Copy link
Collaborator

This PR adds some documentation for Envoy to help users get started with their Envoy node.

@bbengfort bbengfort requested a review from rebeccabilbro May 8, 2024 18:11
Copy link
Collaborator

@rebeccabilbro rebeccabilbro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great @bbengfort! This will serve as an excellent starting point for the user-facing Envoy docs. I've pushed up some minor edits, and have noted a few follow up tasks to populate in the future (cc @BeciLambrecht):

  • In the API reference, the link to the Terms of Service (trisa.io/terms) returns a 404 (screenshots below)
  • On the deployment page, there are placeholders for using kubernetes and systemd which look like they should be populated in the future
  • Nice to haves:
    • Some visual representation of the UI that will help a non-technical compliance officer grok Envoy, e.g link to a video tour of the UI
    • Graphical/abstract representation of what work Envoy is doing (e.g. a mermaid diagram), e.g. using a hypothetical transfer
    • FAQ / Troubleshooting transfers / Envoy support (e.g. what are some common xfer errors/user mistakes and what to do if you observe them)

Screenshot 2024-05-09 at 11 25 43 AM

Screenshot 2024-05-09 at 11 25 20 AM

@bbengfort bbengfort merged commit 4d23c2b into main May 9, 2024
5 checks passed
@bbengfort bbengfort deleted the envoy-docs branch May 9, 2024 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants