Giter VIP home page Giter VIP logo

docs's Introduction

Logo

Osmosis Docs

Osmosis' documentation portal, built with Docusaurus and inspired by Dyte's configuration and template.
Explore the docs »

View Demo · Report Bug · Request Feature

Table of Contents

About The Project

Docusaurus is a static site generator that helps you ship beautiful, accessible docs. For building our documentation portal, we have made certain modifications over the template generated by Docusaurus to be able to properly showcase Osmosis-core, Cosmwasm and Javascript SDKs

Built With

Getting Started

This section describes how you can get our documentation portal up and running on your machine.

Prerequisites

Installation

  1. Clone the repo
git clone https://github.com/osmosis-labs/docs.git
  1. Install NPM packages
npm install
  1. Run the app
npm start

Usage

Writing Documentation

To just edit older documentation, go to the specified versioned folder for a section, for example, you want to edit documentation for React SDK v0.25.x, open up react_versioned_docs/version-0.25.x and edit the required files there.

To create a new version inside a section, for example, flutter. Make your changes in docs/flutter. The ./docs folder consists of the next version, which is unpublished, and is where you add your newer or next version of documentation.

After your changes are done, to create a version, run the following command:

npm run docusaurus docs:version:flutter 1.2.3

This will create a new version 1.2.3 for flutter.

Reference: https://docusaurus.io/docs/versioning

To add new sections

Create a new section in docusaurus by adding a new plugin entry in docusaurus.config.js.

If you're adding a new section, just add new section to SECTIONS[] array with the defineSection() utility easily.

Now, run npm start and you can access your Go docs at http://localhost:3000/go/introduction

Then, you can create versions and edit older versions as mentioned above.

Adding new docs to the Context Switcher

To add a newly created section to the Sections Menu, edit ./src/sections.js.

For example, for a section go, you will add:

import { GoIcon } from '../assets/icons';

const SECTIONS = [
  // ...
  {
    id: 'go',
    name: 'Go',
    icon: GoIcon,
    section: false, // if it shouldn't have a sections menu
  },
]

You'll need to create a GoIcon component too.

That is it!

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated. Sincere thanks to all our contributors. Thank you, contributors!

Support

Contributions, issues, and feature requests are welcome! Give a ⭐️ if you like this project!

License

Distributed under the Apache License, Version 2.0. See LICENSE for more information.

docs's People

Contributors

cordtus avatar cryptoassassin1 avatar czarcas7ic avatar daniel-farina avatar danielfarina avatar deitch avatar faddat avatar gandolfoni avatar george-aj avatar iam-agf avatar ianlapinskii avatar iboss-ptk avatar jayjay-crypto avatar jeremyparish69 avatar jlbit avatar johnnywyles avatar mattverse avatar mikedotexe avatar mikluke avatar muddev avatar niccoloraspa avatar p0mvn avatar sunnya97 avatar tansawit avatar unitychaos avatar valardragon avatar victortokaito avatar xbalbinus avatar yoon-suji avatar zdeadex avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs's Issues

Add any other relevant docs from other repos

A continuation of the old issue that was originally opened in the osmosis repo

We need to hunt down all documentation from other repos, including front-end and add them to the official docs. A follow up will be needed in to then remove these docs from the original source and link them to the official docs.

remove rocksdb.md or add to website

currently https://github.com/osmosis-labs/docs/blob/main/developing/rocksdb.md is an orphan doc, and not referenced anywhere in the website

does it have any value? shall we remove it completely, or add it to https://github.com/osmosis-labs/docs/blob/main/developing/README.md ?

side note: if it has value, it's a bit surprising UX that Osmosis executable does not include rocksdb by default but asks devs to install rocksdb manually separately. What's the rationale behind that decision?

cc @daniel-farina @ValarDragon

Data Folder Structure Explanation

We need to create a page that explains the different folders within the data folder and their respective idiosyncrasies.

  • application.db
  • cs.wal
  • state.db
  • tx_index.db
  • snapshots
  • blockstore.db
  • evidence.db
  • priv_validator_state.json

Scraper Github Action

I realized that the scraper github action runs too quickly after the main branch is updated and therefore doesn't index the changes properly unless it is manually rerun after the pages build and deployment is finished

add a PR template for osmosis docs repo

add a PR template for osmosis docs repo, the PR template will ask requesters to fill in necessary info which will help reviewers to learn the context faster. The template will also force following the same standard going forward

add umbrella section of "Getting Started" to guide newbies on how to contribute to Osmosis

Write a set of starter guidance for new developers to get up to speed quickly. The pain really comes from my experience with onboarding in past weeks that, as someone not so familiar with go/make, I had a super hard time to even build and run tests on osmosis codebase.

cross referencing osmosis-labs/osmosis#891 to here. We can include those suggestions (which is more in-depth than the starter kit) from @ValarDragon as well.

We can break down the effort into smaller one if needed.

broken links in terminology.md

This file:
overview/terminology.md

This text:
Osmosis’ design includes two mechanisms to incentivize long-term liquidity: exit fees and bonded liquidity gauges

The "exit fees" and "bonded liquidity gauges" links are not working.

Other than that, the glossary is well written and helpful. Keep up the good work.

osmosisd service creation

right now docs only show instructions for setting up cosmovisor service, need to make a tab to choose between cosmovisor and osmosisd

[Epic] [Build] on Osmosis Docs

Building dApps on Osmosis

  • Start Building
    • #81
    • In depth guide
  • Tools
  • Join a network
    • Local Osmosis
    • Join the testnet
    • Join the main net
  • Osmosis daemon

Building Osmosis Core

  • Getting Started
    • Build and test
    • IDE Setup
  • Performance & Profiling
  • Join a network
    • Local Osmosis
    • Edge Testnet (Staging environment, stage branch)
      • Push latest version to stage before main
    • Join the testnet
    • Join the main net
  • Modules
    • List of all modules

The following pages I’m not 100% sure where to put them under yet.

  • Key management
  • Assets
  • Relaying

Also, I think we need to create a new page for:

[Build] RPC and LCD endpoints

Document RPC and LCD endpoints. Please share any information available on this ticket and then @daniel-farina can add it to the docs.

  • Understand what endpoints developers actually need to build their apps. (Are lcd actually needed? Should them be replaced with gRPC ? )
  • Show people how to replicate the infra setup as we might have to introduce some rate limiting for non authenticated users in ours

Create documentation/guidelines for the release process

Background

We don't have any documentation/guidelines for releasing our projects. As a result, it takes a lot of time to onboard on that. We should have the sequence of steps and rules documented so that everyone is consistent and new contributors can understand the process quickly.

Relevant discussion on Slack: https://osmosis-network.slack.com/archives/C027ELA290B/p1643991656792299

Acceptance Criteria

  • compile a document recommending a release process
  • gather the team's feedback by asking for review and suggestions on Slack
  • update the document

Expand integration documentation

From JeremyParish, he suggested the following list of articles to add to our documentation under the integration section.

I was thinking of having a page or section for many different things projects tend to ask questions about or need help with:

  • How to transfer CW20 tokens between zones
  • How to validate IBC token transfers
  • How to integrate onto Mintscan
  • How to integrate onto Coin Gecko
  • How to add a pool onto the Trade page
  • How to add a token onto the Assets page
  • How to register onto Assetlists
  • How to register onto Cosmos Chain Registry
  • How to create a pool on Osmosis
  • How to add External Incentive Gauges onto Pools page
  • How to add External Incentives to a pool
  • How to propose onboarding onto the External Incentive Matching program
  • How to propose onboarding a pool for Osmosis Liquidity Mining Rewards
  • How to sponsor a Twitter Contest
  • Request Social Media promotion
    etc.
    I know that some of these, like, adding gauges or creating pools, is already documented elsewhere (under Develop, I believe), but I have it again as it seems to be part of the natural flow for integration.

Create Documentation for Each Module

This is a continuation of the issue that was originally created on the osmosis repo

Modules Documentation breakdown & pendting items

Modules not TODO:

  • txfees (queries and tx are odd I'm circling back)
  • claim (not top priority since airdrop is over right?)
  • simulation (not enough info on this)

Unsorted:

  • auth
  • bank
  • distribution
  • evidence
  • slashing
  • staking
  • upgrade

remove developing/cli/README.md

https://github.com/osmosis-labs/docs/blob/main/developing/cli/README.md seems to be yet another orphan file that is not referenced anywhere. Also missing a few hyperlinks for bullets like "create a wallet"

AFAIU, README in this repo is used more as a group page where it may have multiple sub pages, like https://github.com/osmosis-labs/docs/blob/main/developing/modules/README.md, but this one in cli folder is not serving that purpose and thus seems to be good to remove.

Thoughts? @daniel-farina @ValarDragon

Relayer Setup

Document basic guide on how to set up and maintain a relayer

[Build] Quick guide

This guide is meant to get dApps developers up and running quickly.

@xiangan
As discussed earlier. I have put together an outline for the first quick guide on building dApps in Osmosis. As you become familiar with the tooling we will iterate and improve the guides.

Repo: docs
Branch: stage
Page to publish guide: https://stage-docs.osmosis.zone/developing/dapps/get_started/quick-guide.html

Tasks

  • Membrane initial setup
  • Use Membrane with the testnet
  • Create your first dApp
    • Scaffold your dApp
    • Configure the testnet
    • Deploy
    • Interact with the deployed contract
    • Front-end scaffolding
  • Use Membrane with LocalOsmosis
    • Install and run LocalOsmosis
    • Scaffold your dApp
    • Configure the testnet
    • Deploy
    • Interact with the deployed contract
    • Front-end scaffolding

Please add more to this guide as we become familiar with the tooling.

Help developers build on top of Osmosis

This is an epic to capture the different components needed to help developers build with Osmosis.

Infrastructure

  • osmosis-labs/osmosis-infra#6

Front end

  • Get started with Telescope

Documentation

  • Expand the docs here

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.