GithubHelp home page GithubHelp logo

docs's Introduction

Introduction

Documentation contribution flow

Priorities can be found here in Pinned issues section. Please follow it.

When changes are made to Components, UI, general interaction flows, etc. They should be described in Blynk Documentation repository

Plus we have continuos existing documentation transfer case. To proceed with it:

  • find a file you know/created
  • check it's contents to be up-to-date with Blynk 2.0
  • put it to the corresponding directory or article of the new documentation
  • create pull request (let's keep main branch safe)

Documentation structure.

Keep to tree structure and mind that every entity should be described.

struc

There are Sections, Directories and Articles.

While we see Directories and Articles are displayed commonly in UI we have to keep in mind that in the terms of repository structure there's a difference:

We have Sign Up and Restore Password in Welcome Screen directory. Sign Up has two articles containing so it's directory while Restore Password is an end-point and it's article.

code-struc

While articles contents are stored inside *.md files description to directories should be put inside README.md inside the corresponding directory.

Article or Directory description formatting style

  • When writing an article explain each object giving maximum information shortly.
  • Use headers, paragraphs and lists to make it easier to read. Example
  • Provide the pictures in cases it can ease user's search of some specific buttons (such as Action, Tags or Map View buttons) or to give explanation to separate screen sections (such as Main Tabs switches, Devices List, Device View)

Link new Article or Directory to main structure

Once the Article or Directory description is written/added it should be linked inside SUMMARY.md so it can be uploaded and viewed om the Web.

To retrieve your *.md or directory path:

  • open it

  • click Action button

  • copy Path

    copy path

Edit SUMMARY.md by adding the relative link you got by following prevous steps to the file you've created following the markdown you'll see there.

docs's People

Contributors

blynkkk avatar earlold avatar gitbook-bot avatar mark-pan avatar thanxx avatar vshymanskyy avatar

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.