-
Notifications
You must be signed in to change notification settings - Fork 26
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
Documentation Re-org #115
Documentation Re-org #115
Conversation
Codecov Report
@@ Coverage Diff @@
## master #115 +/- ##
==========================================
+ Coverage 67.66% 70.27% +2.61%
==========================================
Files 32 36 +4
Lines 1976 2493 +517
==========================================
+ Hits 1337 1752 +415
- Misses 570 646 +76
- Partials 69 95 +26
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
My usual nit regarding adding a line between the end of each paragraph and the following code block plus a question regarding whether we should resolve the introduced TODO's in this PR.
README.md
Outdated
Once configured, start Conduit with your data directory: | ||
```sh |
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.
Once configured, start Conduit with your data directory: | |
```sh | |
Once configured, start Conduit with your data directory: | |
```sh |
Co-authored-by: Zeph Grunschlag <tzaffi@users.noreply.github.com>
noop - noop exporter | ||
postgresql - Exporter for writing data to a postgresql instance. | ||
``` | ||
First we need to make sure we have Conduit installed. Head over to the installation section of [the README](../../README.md) for more details. For this tutorial we'll assume `conduit` is installed and available on the path. |
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.
just noticing that one of our two tutorials recommends going to the installation section of the README for install instructions (this one) and the other one just tells you how to do it from the binary. Should we try to be consistent across all our tutorials?
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.
It looks like "IndexerWriter.md" directs people to the release page for a download.
we can again use the list command. For example, | ||
`file_writer` exporter. | ||
To get more details about each of these individually, and their configuration variables, | ||
use the list command or check the [README](../../conduit/plugins/exporters/filewriter/). For example: |
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.
is this the right link? Maybe it should be to the top page of the plugins? And also maybe we should call it "plugins readme" or something?
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.
use the list command or check the [README](../../conduit/plugins/exporters/filewriter/). For example: | |
use the list command or check the [plugins README](../../conduit/plugins/). For example: |
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.
Updated to reference the plugin TOC. I guess it could have links to each of the plugins instead.
Now we will fill in the proper fields for these. I've got a local instance of algod running at `127.0.0.1:8080`, | ||
with an API token of `e36c01fc77e490f23e61899c0c22c6390d0fff1443af2c95d056dc5ce4e61302`. If you need help setting up | ||
Now we will fill in the algod importer configuration. I've got a local instance of algod running at `127.0.0.1:8080`, | ||
with an API token of `e36c01fc77e490f23e61899c0c22c6390d0fff1443af2c95d056dc5ce4e61302` and aan admin API token of `2d9ceaf47debb8aff77c62475b8337f6ecef75c2aa8aa02170a8d38b9126b75a`. Find these in the `algod.token` and `algod.admin.token` files from your algod data directory. If you need help setting up | ||
algod, you can take a look at the [go-algorand docs](https://github.com/algorand/go-algorand#getting-started) or our | ||
[developer portal](https://developer.algorand.org/). |
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.
Hmmm I'm just thinking about how to help people get algod set up properly for conduit. In the other tutorial (Indexer Writer one) we do just walk them through how to do it. I wonder if that snippet could be included in the algod importer plugin documentation page, and then we could point to it from anywhere? Because there are specifics for the importer (in particular the follow mode) that people need to know. Here they wouldn't get that information.
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.
Agreed, this link is not very useful to someone new.
Co-authored-by: algoanne <90275860+algoanne@users.noreply.github.com>
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 think there's still work to be done, but everything in this PR is a major improvement. We can follow-up with further updates in future PRs.
Summary
There is a lot of good content in the docs, but they are spread out a little too much, and the organization is overly influenced by some limitations of the developer portal website.
This PR is intended to re-organizes and re-write the documentation.
Some of the major changes:
README
is now theGettingStarted
page.Configuration
page does not have enough content to justify its existence and has been removed.Test Plan
N/A