Twindle: Separation of concern and splitting into multiple repos

[johnjacobkenny]

_Originally posted by @arthurbuhl in https://github.com/twindle-co/twindle/pull/336#issuecomment-711247789_

I think we should have separation of concern and keep things simple. So, basically we should have like:

• twindle-co/twindle repo as our core app.
  
  
  
  • _Already implemented_ :heavy_check_mark:
  
  
• twindle-co/twindle-cli repo as our CLI app
  
  
  
  • The CLI app done in this PR :heavy_check_mark:
  
  
• twindle-co/twindle-web repo as our core website.
  
  
  
  • header.html, header.css
  
  
  • home_banner.html, home_banner.css
  
  
  • footer.html, footer.css
  
  
  • team_details.html, team_details.css
  
  
  • All our html files and assets should be here.
  
  

Just wanted to share my opinion. I will leave this up for other contributors for discussion.

[EYRAM565]

I feel we should maintain the process we are used to until we are all (beginners) conversant with the process before any other change.

[tolgaerdonmez]

@johnjacobkenny I totaly agree. I think it would be an ease to everyone if we split it.

[johnjacobkenny]

This will be picked up in some time, may not be done immediately though

[vasudeveloper001]

I think this should be done by this week's end. So that beginners can continue to work here, but those who simply want to go ahead with development can work on other repos directly without much baggage. This will help track the issues and pull requests in a better manner.

[proful]

Agree @vasudeveloper001