Introdiction
Confidentiality
If you have not signed an NDA with 10/10, BackBone, Calm Experts or any of its subsidiaries, you are not permitted to have access to this document nor any of its associated documents. If you are an employee or contractor with any of these companies or brands, you are bound by your Employment Agreement, NDA, our Code of Conduct and Development Guidelines. Make sure you have refreshed your memory on all these internal guidelines before reading this document or working on this project.
Welcome to the BackBone development documentation! This resource serves as a comprehensive guide, meticulously crafted for developers actively engaged with BackBone's suite of products. Within these pages, you'll discover essential information encompassing development guidelines, the tools at your disposal, and the established processes designed to foster a seamless and highly efficient development experience.
Given that our products are specifically tailored for developers, it's paramount that we maintain an unwavering commitment to the highest standards in code quality, documentation clarity, and overall user experience.
For details specific to BackBone and its products in line with Calm Experts' standards, guidelines, best practices, and more, we invite you to visit the Calm Experts Docs.
- Intro
- Docs Structure
- Summaries
- Resources
BackBone | Documentation
Getting Started
Description
The goal and purpose of BackBone is to enable developers and companies who employ them to easily build new products and rely on use for BaaS (Backend as a Service) as well as IaaS (Infrastructure as a Service) in simple terms we are the BackBone to any product, should it be cloud serves or Saas.
To Do / tratagy
- Launch media
- Launch Commerce
-
Launch Finance -
Build our own cloud - Build a sales and marketing team
Purpose of Documentation
The purpose of this document, the BackBone | Documentation, is to clearly define all parts of the business, products and establish the scope, means of development, features, definitions, acronyms and all else that is needed to accomplish the success of BackBone, starting with the launch of a media Prototype. This document is intended for developers, UI/UX and graphic designers, investors, marketers and any individual or company participating in the creation of this BackBone. This procurement is not intended to be shared with customers, users or any outside entity.
Scope
This document will cover the users, use cases, means of development and more. What is not included in this document is all and any text, fonts, colors, images, etc. needed for the products itself (that should be created by the marketing team once the app is completed), images, graphics or any materials that are not reliant on a developer. The “Documentation” is not only this document but all the documentation attached; to get a full understanding of BackBone, one should see “Docs site” and follow each link to fully grasp each idea and goal.
Processes
We will explain why this part is important, however to know more about the process, how it works, detailed status updates and more jump to that section.
In this process we have merged the steps and step directions directly into each step documentation, here is a summary.
Included in this Documents
-
Research
-
UX Documentation
-
Development Documentation
Processes
If you would like to contribute and improve any of the processes in this document or the document itself, please see the “Documentations details”.
— move to docs site
Document Support
Document Structure
Intro To Doc Structure
When creating a good product or feature, there are only two things to figure out. 1. What is the problem, and 2. What is the solution? However, before you can even think about building a solution you must have a solid foundation to build that solution on, that is your business, how will you operate, how will you make money and so on. This document is divided into those three parts of success.
The Problem
For the problem, we first need to know that a one exists, that is why we (step #1) Initiate, this lets us *the rest of the company) know of the problem and provides the appropriate teams (often dev or product) with the necessary information to get started. Ready to initiate a task or problem? See the Initiate docs.
In this phase, (step #2) We Discover, we focus on learning as much as possible about the problem and those who have it.
Finally, we (step #3) we Analyze all the information gathered thus far and come to a conclusion, create a document stating opinions and assumptions about the problem and prepare all necessary materials to refer back to when focusing on the solution.
While each part of the process is linked, we recommend starting at the beginning of The Problem document.
For each task or problem you identify, create a jew document, either as a tab or a standalone doc.
The Foundation (AKA Business)
Before we get started, in order to create a product you will need to have a foundation to handle expenses, sales and other admin tasks, this is your business or non-profit. Some of this will be redundant but let’s start with the foundation.
BackBone consists of multiple foundations as we are venturing into various industries, within the Foundation document, one can find each document separated into divisions or subsidiaries.
Profiles
Products
The Solution (AKA Product)
First, (step #4) we Plan. In order to execute a successful UX we must be prepared. We might think of many great solutions but they don’t help the user unless we challenge our assumptions.
That's why we have (step #5) Design.
We must (step #6) Validate that our design works in the real world.
(step #7) Implement our work with the dev team.
Finally, (step #8) Review the work by the dev team before it is handed off to QA and continue the review process with them.
Summaries
Description
The Summaries & Processes section is designed to guide all teams (research, UX, development, marketing and anyone working with them or in connection to BackBone to understand the timeframe, requirements, and expectations related to completing a successful product and related task.
Details & Status
| Assigned To | Due | Requirements | Time Frame | Documents | Status | Tasks |
|---|---|---|---|---|---|---|
| Person | Date | 2 Weeks | File | New |
Results
Problem Summaries
Simply, you will find brief information about the stage, tasks and status.
Foundation Summaries
Company Profile Summary
Market Research Summary
Marketing Summary
Finance Summary
Goals & Objectives
Summary
Hudi is a live streaming auction app, focused on garage sales and rare items
Goals
-
Complete app development
-
Launch
-
Reach 500,000 users
-
Have at least 10 auctions at all times
-
Make at least 20K per month
-
Switch to commerce
-
Develop costume backend functions along with commerce
-
Be popular in at least 10 countries
-
Reach 5m users
-
Make $1m
5Ws
Solution Summaries
Full Documentation List
These documents are listed in order of importance or roughly in the order of how you should consume them.
These documents are still in the early stages, be sure to come back and update yourself over time.
Before you start
Sign the Hudi | Non-Disclosure Agreement with Template | Pending
- Make a copy
- Replace “Template” with your legal name
- Review the details with your hiring manager
- Sign the document and send to hiring manager
Sign your Hudi | Employment Agreement with Template | In progress
- Repeat the same process as the NDA
Read the Hudi | Code Of Conduct | Pending
Read the BackBone Practises & Guidelines | Pending
Complete this document Hudi | Documentation | In progress
Read the Development Documentation | In progress
Documentation by Department
Hudi Departments | Pending
HR
Hudi | HR | Pending
Employee Handbook
Hudi | Employee Handbook | Pending
BackBone benefits | Pending
Hudi | Employment Agreement with Template | In progress
BackBone | Practises & Guidelines | In progress
Hudi | Non-Disclosure Agreement with Template | Pending
BackBone | Code Of Conduct | In progress
Development
Legal
Sales
Marketing
Documentation by Divisions
Hudi Devisions | Pending
BackBone Everything
Hudi | Problem | In progress
Hudi | Foundation | In progress
Hudi | Solution | In progress
Entertainment
Problem | In progress
Foundation | In progress
Solution | In progress
Commerce
Problem | Pending
Foundation
Solution
Advertising
Problem
Foundation
Solution
JS&C
Problem
Foundation
Solution
Products
Everything
API Documentation | Pending
Hudi | Solution | In progress