-
Notifications
You must be signed in to change notification settings - Fork 3
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
Sample updates, trying new formatting and content flow #654
Sample updates, trying new formatting and content flow #654
Conversation
Bumps [postcss](https://github.com/postcss/postcss) from 8.4.29 to 8.4.30. - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.4.29...8.4.30) --- updated-dependencies: - dependency-name: postcss dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
@@ -202,10 +197,39 @@ The header and payload of the `TOKEN` may be examined with the following command | |||
|
|||
```shell | |||
# Header | |||
echo -n $TOKEN | cut -d '.' -f 1 | base64 -D | |||
echo -n $TOKEN | cut -d '.' -f 1 | base64 -d | jq |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-D
seemed a typo for-d
- Added
| jq
to format the output a little cleaner. Although, it does assume the developer hasjq
on their machine. Not sure if we want to have a doc for common tools that are assumed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have a doc for common tools but jq is mentioned earlier in this article.
# Payload | ||
echo -n $TOKEN | cut -d '.' -f 2 | base64 -D | ||
echo -n $TOKEN | cut -d '.' -f 2 | base64 -d | jq |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Split the header and payload out to separate copy/paste commands. Although, with the jq output, it might be ok to merge back to one block copy/paste
@@ -32,35 +32,23 @@ When enabling non-interactive access to RKVST, you ***must*** create your first | |||
|
|||
### Using the RKVST UI to create an App Registration (First-Time Setup) | |||
|
|||
1. As an Administrator, open the `Settings` interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This block is mostly indentation formatting to tighten up the whitespace and make the imagery indented under the numbered lists.
{{< img src="RecordClientIDandSecret.png" alt="Rectangle" caption="<em>Record your Client ID and Secret</em>" class="border-0" >}} | ||
|
||
5. Now that you have created your App Registration, follow the steps below to [test generating a token](./#getting-a-token-with-your-app-registration) and [ensure you can access the RKVST API](./#testing-your-access). | ||
1. As an Administrator, open the [RKVST Portal](https://app.rkvst.io/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Called out the URL so users can click directly. I haven't figured out how to get HUGO to open a link in a new tab, similar to just the docs does with a {:target="_blank"} addition
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this, but we should still be able to tell the story if we don't have screenshots. They are an overhead in the docs and we are aiming to reduce the use of them, where we can.
…postcss-8.4.30 Bump postcss from 8.4.29 to 8.4.30
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
I've done a first pass of validation. The multiple steps could be converted to a script, creating the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like where this is going. Is it possible for me to pull down a local copy of this that so that I can see how it would look for a customer?
Signed-off-by: steve lasker <stevenlasker@hotmail.com>
Moved to using #669 |
A work in progress for trying a different, more detailed flow
Includes a few typos
Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.