πŸ‘Contribute to the Documentation

It explains our documentation participation.

Comprehensive documentation plays a vital role in the adoption and development of any growing technology, especially one that's evolving as quickly as Flashback. Whether you're an experienced developer or a newcomer, your contributions to our documentation, tutorials, and how-to guides can help us to build a stronger, more accessible platform. Plus, it's a great way to expand your own expertise and support the entire community!


Why Contribute?

  1. Enhance Your Skills: Writing and refining documentation deepens your understanding of Flashback’s concepts. Become an expert in Flashback, and you'll have the chance to become an ambassador or ecosystem mentor to newcomers.

  2. Grow the Community: Clear, high-quality resources attract more developers and users, fostering a stronger blockchain community. By sharing knowledge, you, as a community member, play a key role in Flashback and its emergence as a next-generation cloud solution.

  3. Boost Your Portfolio: Being an active contributor showcases your expertise and commitment, which can set you apart in the blockchain industry from a professional development perspective.


Types of Contributions

  1. Documentation: Improve existing docs or create new content. This could include tutorials, an introductory video about a feature, architectural explanations, or an overview of the technology.

  2. Tutorials: Write step-by-step guides to help others learn how to use Flashback tools and services. The easier we make it to learn, the more users and builders will join us.

  3. How-to Guides: Develop detailed instructions on tasks like deploying a blockchain node or creating a smart contract.


⭐ Getting Started

Step 1: Understand the Contribution Guidelines

Read contribution guidelines. Look for a CONTRIBUTING.md file in the repository. This document will provide information on:

  • How to fork and clone the repository

  • Branch naming conventions

  • Pull request (PR) procedures

  • Coding standards

Step 2: Set Up Your Environment

Ensure you have the necessary tools and dependencies installed. Common tools include:

  • Git: For version control

  • Markdown editors: For writing documentation (e.g. Visual Studio Code, Typora)

  • Blockchain-specific tools: Flashback currently leverages ecosystems like Starknet and Stellar. You can participate in these environments.

  • Software and Cloud tools: Flashback is doing storage (and computing in the future). Contribute to Flashback’s open-source codes related to data storage integrations.

Step 3: Identify Areas for Improvement

Start by reviewing our existing documentation to identify gaps or areas for improvement. Look for:

  • Outdated information (the blockchain world moves fast... help us to keep Flashback at the cutting edge of new technologies)

  • Missing tutorials (Flashback has endless possibilities; your how-to guide might be just what others need)

  • Ambiguous instructions (clear explanations encourage broader adoption)


πŸ§ͺ Making Your Contribution

1. Fork and Clone the Repository

Fork the repository to your GitHub account and clone it to your local machine:

git clone https://github.com/flashbacknetwork/flashback-docs
cd flashback-docs

2. Create a New Branch

Create a new branch for your contribution:

git checkout -b documentation-update-gitusername

3. Write or Update Documentation

  • Use Clear and Concise Language: Ensure your writing is easy to understand.

  • Include Examples: Code snippets and screenshots can help illustrate your points.

  • Follow the Project's Style Guide: Stay consistent with the style of existing documentation.

4. Commit Your Changes

Commit your changes with a meaningful message:

git add .
git commit -m "Updated documentation for feature X"

5. Push to Your Fork

Push your changes to your forked repository:

git push origin documentation-update-gitusername

6. Create a Pull Request

Navigate to the original repository's page and create a pull request. Provide a clear and detailed description of your changes and reference any related issues.

7. Address Feedback

Project maintainers may request changes. Please address their feedback as soon as possible to get your contribution merged. We recommend you open a ticket in our Discord for follow-ups and to learn about potential rewards.


⏭️ Writing Tutorials and How-to Guides

Structure Your Content

  1. Introduction: Briefly explain what the tutorial or guide will cover.

  2. Prerequisites: List the tools or knowledge needed.

  3. Step-by-Step Instructions: Break down the process into clear, actionable steps.

  4. Conclusion: Summarize what was covered and provide next steps or additional resources.

Example Template

# Title of the Tutorial

## Introduction
Provide an overview of what the tutorial covers.

## Prerequisites
- List of required tools or knowledge.

## The Steps of the Guide

### Step 1: Name of the Step
- Detailed instructions for the first step.

### Step 2: Name of the Step
- Detailed instructions for the second step.

## Additional Information (optional)
Provide additional information to udnerstand the tutorial and the technology.

## Conclusion (Optional)
Summarize what was covered and suggest further reading or next steps.

## Frequently Asked Questions (Optional)
List the questions you receive by doing your tutorial. 

## Author Contact (Optional)
Provide the contact information as an author. 
It is welcome and will help to improve your tutotial and yur contribution.

Best Practices

  • Keep it Simple: Avoid jargon and overly technical language.

  • Be Thorough: Don’t skip steps; assume readers are new to the topic.

  • Update Regularly: Technology evolves, and so should your content.

  • Engage with the Community: Participate in forums, Discord channels, and discussions to understand common pain points and what people need.


Contributing to Flashback documentation, tutorials, and how-to guides is a rewarding way to enhance your skills, support the community, and promote the adoption of blockchain technology. By following these guidelines, you'll create meaningful resources that benefit both newcomers and experienced developers. We look forward to seeing your contributions!

Happy contributing!

Last updated

Was this helpful?