Accommodate for a growing number of template functions

[simenandre]

Hello! 🎉

Thank you again for this awesome tool! Considering the growth this repository has had, I thought I could throw myself into trying to "organize it for growth" (feels very corporate thing to say). Anyway, what I did was move all Go files into internal, since, as of now there are no exported functions, and probably will not, right? Secondly, I added cmd/main.go.

I am but a novice Golang-programmer, so feedback would be magnificent. I'll improve as you see fit!

But, why not keep it as is?

Mostly because if files are kept being added, the repository tree will be very long and people hate scrolling to the README 😅.

Before	After
. ├── Dockerfile ├── LICENSE ├── README.md ├── gists.go ├── go.mod ├── go.sum ├── humanize.go ├── main.go ├── repos.go ├── rss.go ├── sponsors.go ├── templates │ └── github-profile.tpl ├── types.go └── users.go	. ├── Dockerfile ├── LICENSE ├── README.md ├── cmd │ └── main.go ├── go.mod ├── go.sum ├── internal │ ├── gists.go │ ├── humanize.go │ ├── main.go │ ├── repos.go │ ├── rss.go │ ├── sponsors.go │ ├── types.go │ └── users.go └── templates └── github-profile.tpl

[muesli]

@cobraz Apologies for not responding earlier, this one completely went under the radar and I just noticed there's an open PR left here 😟

I agree, there's definitely room to better organize the project. I think we should rather move the GitHub & GoodReads API (that now exists) into their own sub-packages in this repo. There's no need to hide them away. Something like humanize.go probably fits in either internal or a utils package (even though I typically despise them a bit).

If you're still interested in moving this forward, I'm happy to merge such a PR!

Sorry again!