Danielle’s рroject is pretty similar from the beginning steps that we’re taking with Ashley project.
She also will be able (in my opinion to help us with DB improvements(later) for now(think we will prepare some data for her, using the same scripts, that my team created for my project).
Then we will create a backend system for her project, similar to approach, proposed to both Ashley/Arthur projects.
Then I understand that first frontend pages/views should be also similar logic as well.
What is bothering me – Italian language of data. If we just add it and display - no problems here. But it will add an additional level of complexity if we’ll decide to add localization functionality. It can be solved with small steps, by improving my code modules, but it’s definitely a part that I know how to do, but we never started it. Only in my head for the future. It may not a big problem but will take additional time to do.
There a lot of great work was done related to localization software. one of the latest frameworks came from facebook. But again, it requires some time for research. https://github.com/facebookincubator/fbt
Frontend - that will display data and search/filtration functionality.
Ashley – how we can, need to implement search module at your project - but please keep it simple. Because the whole search is another big topic to discuss together later.
Right now I move only one teammate - she will work with DB+backend system. it will be slow from the beginning, but we can extend team, working on that part in the future.
Danielle --> will you be able to export Italian DB into JSON file or CSV file to me? This will save some time for me and for my teammates.
- Ok, your data in the process right now. With my next approach that data will be transferred into the backend, based on graphql server(before uploading data into a database, we will create a scheme that will work with that data should be improved, extended, in order to meet your project requirements)
- We can discuss a few blocks from your schema. But not all of them. Because MVP is our goal. We cannot think about all the aspects.
- We need to split your functionality into small and understandable blocks/modules. They should work independently. It will help to limit our work and start to work on a few modules in parallel and independently.
3.1 If we will do good documentation like as part of our collaboration - it will save a huge amount of time of my team members.
So let’s start to work together closely and have a lot of small chitchats, that can make a picture of your project as clear as possible.
3.2 Think about what will be next and how to explain it to developers. Next steps, assuming that they don’t know a lot about food data theory. So anything should have a detailed explanation.