Introduction
BackBone Vitals are the core functios for any project, talored for Infrestructure, Build, Launch and maintain, these categories help Clients take thier project through the full development lifecycle and we cover every srucal step.
Task Chat Launch- Infretructure
- Build
- Launch
- Maintaine
Ideas
- Earnings
- Billing
- Database (SQL / noSQL)
- Hosting (Site, App, Function)
- Storage
- Securaty
- Logs A system that keep a record of all events that take place on the database, function/backend and frontend
- Extentions (Prebuilt functions)
- Help Center
- User Guild
- Token sustem
- Desogn systems
- Icon packadges
- frontend libraraies (in flutter, react, kotlen, etc)
- Tests
- Analytics
- Status & Details
- Research
- User Stories, Flows & Personas
- Features & Functions
- Data
Description
Add a detailed description
Status
These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.
| Owner | Lead | Doc Status | Product Status | Last Update | Version | Release | Phase |
|---|---|---|---|---|---|---|---|
| Mendy | Esti | In Progress | Up Next | 04.03.2024 | 0.01 | Internal | Alpha |
Reminders
- Keep code lean and clear
- follow the outlined arcetecture
- write commetes in your code
- update the staus in the docs and in GitHub
- try not to recreate functions we alredy have, rather update exsiting functions to support your needs
- Be sure to follow the release guidelines
- Update Documentation
- keep API docs up to date each time you update or add endpoints
Links & Resources
Research
Features
Below is a list of features that will be utilized in order to deliver the best account features and functionalities. The details bellow are not comprehensive feature details but rather, describe how the features will be utilized within the account, for further details, please see the individual feature documentation.
-
[Permissions]
permissions are a a spesifict fuunction like users, projects, etc. esencaliy every action that can be taken has a related permission.
-
[Levels]
each permission has a permission level (e.g. view, comment, edit, admin, owner)
-
-
Access
Access give the user or client a set of permitions
-
Groups
A group
-
Teams
should the client have created a team with multiple clients, permissions or access can be set for the full team at once.
You can find the Data Structure.
On the document we want to keep all the important data, the first fetch and fast to access.
- who (user/client id)
- what (object id e.g. project, aseet, etc)
Access
If the account type is not "indiviual" the account will not have an auth method and thefore will reqesre access. This will be a sub-collection within the account document that will hold the account, group, etc IDs of anyone who has access to this account.
- access
- - account 1
- - - account id
- - - level
- - - inhrited (id)
- - - expries