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
Given that more people are coming to the project we should start writing a bit more documentation and putting it all in one place.
I was think that maybe we could try to use GitHub Pages to write all the documentation and gather the useful link so that then I could ask Mr. RIP to crate a short link that could be easy to remember.
The text was updated successfully, but these errors were encountered:
UPDATE: since yesterday https://rip-comm.github.io/sossoldi/ is working and we can use it as a landing page for our project 🎉
Moving forward there are certainly lots of things that we can improve, as discussed on Discord here are a few task pages that would be really useful:
Coding styles: for all the rules or best practices of our project
DB Structure
Setup + How to contribute and open a PR (this is partially implemented but we might want to improve it, for example we should make sure that we are all using the same version of Flutter)
Roadmap/Mission: we could add a page with what this project is about and why we are working on it
Reusable widget list: so that everyone knows what's already there and doesn't have to write everything from scratch
Folder Structure
How to contribute to the Documentation
As always if anyone would like to work on some of them you can comment here and then open a PR when you are ready.
If you don't know how GitHub Pages work don't worry it's pretty simple, you can just use .md files and link them as you would do normally, once those changes are merged in the main branch then the page will update automatically in a few seconds. To test the page inside your fork you need to activate them inside your fork (here is a guide) and then you will have your personalised link (ex. https://theperu.github.io/sossoldi/)
Given that more people are coming to the project we should start writing a bit more documentation and putting it all in one place.
I was think that maybe we could try to use GitHub Pages to write all the documentation and gather the useful link so that then I could ask Mr. RIP to crate a short link that could be easy to remember.
The text was updated successfully, but these errors were encountered: