Add links to docs and API in the footer #4431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
concept ACK. We should add proper icons (@dstrukt) and I'll take a look how we might handle that it's getting crowded down there :) |
Closed
|
I always imagined a |
|
Will get us some icons here this evening so we can close this out! |
|
Icons sent via DM to @dennisreimann |
|
@pavlenex the bitpay API shouldn't be documented. This is old stuff, we need to let it die. The docs aren't only useful for developers. Just need a link to the API docs. |
dennisreimann
approved these changes
Dec 16, 2022
Kukks
pushed a commit
to Kukks/btcpayserver
that referenced
this pull request
Dec 26, 2022
* Add links to docs and API in the footer * Update icons Co-authored-by: Dennis Reimann <mail@dennisreimann.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The API page isn't linked anywhere, so people can't find it.
We have a documentation page on our documentation website, however, since plugins may add their own API, it's better users go to their own page.
I also added link to the documentation website.