This repository has been archived by the owner on Feb 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Integrator documentation #213
Labels
Comments
In my role as Developer Advocate, I would be interested in assisting here. |
@danfowler That would be great! Is there something else important you think we should cover? |
|
Add good examples on goodtables.yml and sources. |
vitorbaptista
added a commit
that referenced
this issue
Dec 6, 2017
It contains: * Quickstart on GitHub * Writing a table schema * Configuring goodtables.io * A (small) goodtables.yml reference It's missing docs for AWS, and the layout is still the default Sphinx theme.
vitorbaptista
added a commit
that referenced
this issue
Dec 6, 2017
It contains: * Quickstart on GitHub * Writing a table schema * Configuring goodtables.io * A (small) goodtables.yml reference It's missing docs for AWS, and the layout is still the default Sphinx theme.
vitorbaptista
added a commit
that referenced
this issue
Dec 10, 2017
vitorbaptista
added a commit
that referenced
this issue
Dec 10, 2017
The docs were generated using the OpenAPI specification. Ideally, the specification file would be generated directly from our API definition, so they're always in sync. We don't do it now, but will in the future.
vitorbaptista
added a commit
that referenced
this issue
Dec 10, 2017
vitorbaptista
added a commit
that referenced
this issue
Dec 10, 2017
The docs were generated using the OpenAPI specification. Ideally, the specification file would be generated directly from our API definition, so they're always in sync. We don't do it now, but will in the future.
vitorbaptista
added a commit
that referenced
this issue
Dec 12, 2017
It contains: * Quickstart on GitHub * Writing a table schema * Configuring goodtables.io * A (small) goodtables.yml reference It's missing docs for AWS, and the layout is still the default Sphinx theme.
vitorbaptista
added a commit
that referenced
this issue
Dec 12, 2017
vitorbaptista
added a commit
that referenced
this issue
Dec 12, 2017
The docs were generated using the OpenAPI specification. Ideally, the specification file would be generated directly from our API definition, so they're always in sync. We don't do it now, but will in the future.
vitorbaptista
added a commit
that referenced
this issue
Dec 13, 2017
vitorbaptista
added a commit
that referenced
this issue
Dec 13, 2017
vitorbaptista
added a commit
that referenced
this issue
Dec 13, 2017
The file size reduced about ~80%
vitorbaptista
added a commit
that referenced
this issue
Dec 15, 2017
vitorbaptista
added a commit
that referenced
this issue
Jan 25, 2018
vitorbaptista
added a commit
that referenced
this issue
Jan 25, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Coupled with big improvements in UX we need to prioritise a clear and comprehensive documentation that guides users on how to make the most of the service. There should be a general introduction to data validation and how the service works.
The critical parts are how to enable / add sources and the
goodtables.yml
syntax. For adding sources we need dedicated page for each backend covering specifics:We also need a page for more advanced topics like the API and authorization. And when they are in place, different plans.
My suggestion is to set up a separate static site on a custom subdomain (help.goodtables.io) that allows us to iterate and improve the docs fast.
Tasks
goodtables.yml
syntaxEstimate
4
The text was updated successfully, but these errors were encountered: