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
You could use the TODO functionality in the Projects tab for writing what improvements could be made and what could be fixed. This also serves the purpose of documenting all the progress through the years, that would not be documented if changes were discussed only in the WhatsApp groups.
Adding the TODO in the README is a good start, but a README would serve a better purpose.
The November 2019 version could also be linked to releases instead, as stated in this issue #12
Maybe see this to get started on crafting a good readme.
The text was updated successfully, but these errors were encountered:
Can we convert this repository name to RMI-NITT.github.io?
That'll make debugging and sharing the link within members for corrections easier.
We don't have to create a separate repository every time and make changes in both right?
That's true.
The reason we didn't have this before was that it was easier to maintain just 1 repo, and I remember trying out a gh-pages branch that would deploy the website.
I'm not sure that still works.
And another reason that I didn't do it was that it seemed redundant to have two URLs for the same content.
Once updated, both RMI GitHub and RMI NITT have the same content.
And while updating, one version would differ with another.
But that's fine if you guys are fine with that I guess.
Maybe you could try pointing our rmi-nitt.github.io to automatically point to rmi.nitt.edu
I'm guessing that is possible, but I'm not aware of how it is implemented as of now
You could use the TODO functionality in the Projects tab for writing what improvements could be made and what could be fixed. This also serves the purpose of documenting all the progress through the years, that would not be documented if changes were discussed only in the WhatsApp groups.
Adding the TODO in the README is a good start, but a README would serve a better purpose.
The November 2019 version could also be linked to releases instead, as stated in this issue #12
Maybe see this to get started on crafting a good readme.
The text was updated successfully, but these errors were encountered: