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

Clarify Documentation & Prevent Secret Leakage #10

Open
wants to merge 22 commits into
base: master
Choose a base branch
from

Conversation

TurekBot
Copy link

Hey @john-aldridge, after the recent problem we had with programmatic filters, I reviewed this example repo.

I noticed a few things that might be unclear to newcomers to DomoEverywhere (like myself), so I dusted off my Technical Communication degree and tried to clarify the docs a little. I made sure to not change the content wherever I could, but instead just structure it in an easier to digest way.

Here's a preview of what it will look like once merged.

There was at least one substantive change I made, though. I made it harder for people to accidentally commit their .env file.

TurekBot and others added 22 commits August 27, 2024 14:02
Instead of having them all above, I figured it would be clearer to have them next to the one they are referring to.
The markup looks like they intended a list—now it IS a list. This will help make things more readable.
These comments are important enough to be included right next to what they describe, especially for people who aren't as familiar with these concepts as Domo engineers are.
That way they're there if needed, but won't be unexpectedly changing things
Instead of a giant wall of text, let's advise the user of what we're about to do
Unfortunately, the admonition makes the step number reset. Using explicit numbers fixes this.
It was in one level too deep, breaking the formatting
This poses a risk of confusing or tripping up people. It seems better to omit it.
This helps the user read and understand what we've written
Previously, it would've been easy for someone to accidentally commit their client id and secret. Now, we make that mistake much harder to make.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants