Conversation
|
|
||
| **NOTES** | ||
| Skeleton doc. | ||
| Actual doc is in review. |
There was a problem hiding this comment.
This is fine for now, but I don't recommend merging placeholders like this to the main branch. In practice, I think most placeholders or "coming soon" messages end up sitting around indefinitely until they're removed without actually being implemented.
There was a problem hiding this comment.
I will get all the content in before merging, and I won't leave any placeholders. I prefer to omit the topic entirely if I had to (and this doc does exist now).
| sidebar_label: PayID CLI | ||
| --- | ||
|
|
||
| **NOTES** - This doc will be cut up into tutorial and concepts. |
There was a problem hiding this comment.
I suggest concept and reference. Usually a CLI is a (particularly boring) means to an end, so it may come up in the context of other tutorials but anything beyond the most basic of examples probably needs more of a task-oriented context. (e.g. "Here's how to delete old PayIDs using the CLI")
There was a problem hiding this comment.
I agree, as the Verifiable PayID tutorial actually covers PayID CLI tutorial content anyway.
| - You can use [AWS and nginx](remote-deployment) to set up your PayID server, or adapt those instructions to other cloud providers. See the [PayID server requirements](payid-server-requirements) to learn about what types of resources you should deploy. | ||
|
|
||
| To experiment with PayID, you can quickly spin up a local server. First, clone the [PayID reference implementation](https://github.com/payid-org/payid). Then once you are inside the repository you can run `npm run devEnvUp`, which uses the local `docker-compose.yml` file to set up docker containers running a Postgres database and PayID server. | ||
| To experiment with PayID, you can quickly set up a local server. First, clone the [PayID reference implementation](https://github.com/payid-org/payid). From inside the repository, run `npm run devEnvUp`, which uses the local `docker-compose.yml` file to set up Docker containers running a Postgres database and PayID server. |
ryangyoung
left a comment
There was a problem hiding this comment.
Once things are a little more baked we could start quibbling over details but this looks like a solid start and definitely the right direction. Excited to see it evolve!
|
Will add Xpring SDK tutorial. Have resolved conflicts with master. Have added back some Getting Started content intentionally. |
|
ryangyoung
left a comment
There was a problem hiding this comment.
This is looking great. Just a couple of small things that we should change before merging (like removing an internal note) but otherwise, this is a great baseline for the next iterations of the PayID docs!
|
|
||
| ## Create a PayID | ||
|
|
||
| Now that you have a PayID server running, you can create a PayID. If your server was publicly accessible, other people could query your account information from your PayID server. |
There was a problem hiding this comment.
Does this duplicate the following paragraph? The tenses are different in both versions. I'd vote for present tense or whatever's most easily consistent.
| sidebar_label: Set Up NGINX Reverse Proxy and SSL | ||
| --- | ||
|
|
||
| After you set up a PayID server using your preferred [deployment option](intro-deploy.md), you can set up NGINX Reverse Proxy + SSL for load balancing and security. |
| sidebar_label: Overview | ||
| id: welcome-to-payid | ||
| title: Welcome to PayID | ||
| sidebar_label: Welcome to PayID |
There was a problem hiding this comment.
Food for thought: will this page need any revision for the new docs landing page?
|
|
||
| ## PayID standards | ||
|
|
||
| PayID is an open standard. Commentary is welcome. You can open a Github issue to provide feedback. |
There was a problem hiding this comment.
| PayID is an open standard. Commentary is welcome. You can open a Github issue to provide feedback. | |
| PayID is an open standard. Commentary is welcome. You can open a [Github issue](https://github.com/payid-org/payid) to provide feedback. |
ryangyoung
left a comment
There was a problem hiding this comment.
Looks good! Made one tiny suggestion that doesn't preclude the merge!
High Level Overview of Change
Rethink the organization of the docs. Make certain aspects clearer.
Context of Change
The IA should be better.
Type of Change
Before / After
Test Plan
Build and run locally.
Future Tasks
Continue to iterate.