🐍 Ocean Protocol's official documentation https://docs.oceanprotocol.com
Go to file
Matthias Kretschmann e6224e2d0d
add Docker
2018-11-10 14:47:09 +01:00
content many content changes 2018-11-10 00:16:41 +01:00
data handle meta title & descriptions, section color coding, 2018-11-10 02:42:27 +01:00
src handle meta title & descriptions, section color coding, 2018-11-10 02:42:27 +01:00
static more plugins 2018-11-09 22:59:22 +01:00
.editorconfig proof of concept for nav sidebar 2018-11-08 10:44:46 +01:00
.eslintrc drop da base 🍾 2018-11-07 12:33:32 +01:00
.gitignore drop da base 🍾 2018-11-07 12:33:32 +01:00
.prettierrc drop da base 🍾 2018-11-07 12:33:32 +01:00
.travis.yml cache generated images 2018-11-10 00:31:47 +01:00
Dockerfile add Docker 2018-11-10 14:47:09 +01:00
LICENSE Initial commit 2018-11-07 11:01:48 +01:00
README.md add Docker 2018-11-10 14:47:09 +01:00
docker-compose.yml add Docker 2018-11-10 14:47:09 +01:00
gatsby-browser.js switch syntax theme 2018-11-09 22:14:20 +01:00
gatsby-config.js handle meta title & descriptions, section color coding, 2018-11-10 02:42:27 +01:00
gatsby-node.js build fixes 2018-11-09 22:10:35 +01:00
package.json many content changes 2018-11-10 00:16:41 +01:00

README.md

banner

docs

🐍 Ocean Protocol's official documentation.

Build Status js oceanprotocol code style: prettier Greenkeeper badge


These docs are meant to be viewed on docs.oceanprotocol.com. You can still browse them here but links or images might not work in some places.


Content

All content lives in the /content & /data folders utilizing GitHub Flavored Markdown and YAML. Content is organized into the above mentioned categories through subfolders. Those subfolder names, along with the file name, define the final url of a given piece of content.

The final navigational organisation of the content is driven through the sidebar files under /data/sidebars.

Have a look at docs.oceanprotocol.com/test/ to see what content elements can be used in the docs.

Sections

The documentation is split in multiple sections whose content lives in this repo:

  • Core concepts: high-level explanation of concepts, assumptions, and components
  • Setup: getting started for various stakeholders and use cases
  • Tutorials: detailed tutorials

Those sections and their copy are defined in the /data/sections.yml file.

TODO: Additionally, these docs live in their respective repos and are pulled into this site on build time:

  • API reference
  • Component docs

Editing docs

Every article on docs.oceanprotocol.com ends with an Edit this page on GitHub link. Clicking that will put you to the right place in the repository from where you can hit the Edit pencil icon.

GitHub will automatically fork the repository if you are not part of the oceanprotocol organisation on GitHub. Members can simply push to a new branch on the original repo.

The editing workflow is as follows:

  1. Make your changes
  2. Push your changes to a new branch in the repo, or in your fork
  3. Open a pull request against master, automatically asking for review
  4. Wait for review, possibly make request changes
  5. Wait for all checks to pass
  6. Merge!

Adding docs

...

Repositories

The repositories list is currently sourced from the /data/repositories.yml file. The GitHub link is auto generated from the given repository name and will always be added by default.

Development

The site is a React app built with Gatsby, pulling its content from various sources.

As a prerequisite you'll need on your machine:

  • Node.js
  • npm

Clone this repo, install all dependencies, and start the development server:

git clone git@github.com:oceanprotocol/docs.git
cd docs/

npm i
npm start

This will start a hot-reloading local server exposed under localhost:8000.

Use Docker

Alternatively, you can use Docker for which you need to have installed on your machine:

Then use Compose to bring everything up:

docker-compose up

This will expose a hot-reloading server under localhost:8000.

Authors

License

Copyright 2018 Ocean Protocol Foundation Ltd.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.