Split sections into separate files about stack-on-a-budget HOT 13 CLOSED

you are right, I already thought about it,
I will probably do that in the coming days ;)

from stack-on-a-budget.

@255kb - I can help split them up - the file is not too large at this point. Let me know.

from stack-on-a-budget.

@sangupta wow, I am sorry I just finished splitting the files 1mn ago...

from stack-on-a-budget.

@255kb No worries... it was my bad.

from stack-on-a-budget.

@sangupta still it is sad to see work being trashed, thanks for your understanding 👍

from stack-on-a-budget.

@255kb nah - till things are getting done... no one should mind.

BTW - do you need help in clearing up the conflicts with currently open PRs ?

from stack-on-a-budget.

@sangupta That would be great, I have not a lot of time these days, and christmas is coming, it will be even harder ><
Do you need any authorization?
Also, don't worry not everything has to be merged tonight ;) And I still want to be sure that everything is properly described

from stack-on-a-budget.

@255kb You can mark issues to me and I will raise a PR so that you can run a review.

Or if you wish to grant me write access - I can them tomorrow and then you run review on HEAD.

from stack-on-a-budget.

Actually, I imagined that the service names would stay in the main readme too as links. Good idea? Bad?

from stack-on-a-budget.

not a bad idea
I am using a VS Code plugin that automatically create table of contents, but not accross files, so I did not take time to do this!

from stack-on-a-budget.

created an issue #102

from stack-on-a-budget.

I see. Wouldn't have been that much work given that there already was a ToC assembled

True though, that managing it manually isn't perfect

from stack-on-a-budget.

yeah I will take it back from the previous version ;)

from stack-on-a-budget.