You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, we have a clear idea of how to write an extension and all the steps needed for it. So, first thing is to study a new structure for this project before implement the new UI made by @nexturhe4rt.
TBP Consumer API
This API needs to be a 10% write/90% read focused, since the only goal is to serve the chatter information for the extension users. It's suppose to be simple, but at the same time it's supposed to be FAST! That's why the initial design is using ScyllaDB and Rust and we're gonna keep it.
TBP Platform
This will carry our landing page and a simple admin/user panel with FilamentPHP. Besides that, when you do any change at the extension, you will be communicating with the Platform and it will ensures to persist at the Consumer API.
In general, every feature will be developed in PHP and the only change at the Consumer API will be adding a new key to the settings table.
How to organize it?
We're gonna open issues only at the main repository (here). For each new feature, we have to elaborate the effort around the projects and PROPER LABEL IT!
Also, for every release, all repositories must be tagged with a new release but this still can be turn into a discussion.
Next Steps (in short)
Refactor the Extension and code the new UI
Prepare the new Feature Requests
Establish a Release routine.
Thanks everyone for the work so far and let's make it work even better!
The text was updated successfully, but these errors were encountered:
We're on Beta and the goal is the 1.0.0!
Since we're growing all projects at the same, I decided to split it into single repositories for each application. So, now the structure looks like:
New Repository Responsibilities
TBP Extension
Now, we have a clear idea of how to write an extension and all the steps needed for it. So, first thing is to study a new structure for this project before implement the new UI made by @nexturhe4rt.
TBP Consumer API
This API needs to be a 10% write/90% read focused, since the only goal is to serve the chatter information for the extension users. It's suppose to be simple, but at the same time it's supposed to be FAST! That's why the initial design is using ScyllaDB and Rust and we're gonna keep it.
TBP Platform
This will carry our landing page and a simple admin/user panel with FilamentPHP. Besides that, when you do any change at the extension, you will be communicating with the Platform and it will ensures to persist at the Consumer API.
In general, every feature will be developed in PHP and the only change at the Consumer API will be adding a new key to the
settings
table.How to organize it?
We're gonna open issues only at the main repository (here). For each new feature, we have to elaborate the effort around the projects and PROPER LABEL IT!
Also, for every release, all repositories must be tagged with a new release but this still can be turn into a discussion.
Next Steps (in short)
Thanks everyone for the work so far and let's make it work even better!
The text was updated successfully, but these errors were encountered: