Refactoring and review

[tbauriedel]

As agreed with @widhalmt in person, we want to review the current state of the collection and refactor some parts of it.

There is no fixed list of issues, bugs, etc. that we want to refactor, but we will find those while reviewing.

We "accept" to implement breaking changes to improve the collection.

Already merged PRs: #394. All following PRs will be reference this issue.

[ivareri]

Will you go through pending pull requests before refactoring? I'm guessing this will change enough to break most of the pending PRs

[tbauriedel]

While some PRs are still in the draft phase or not quite ready yet, there are some PRs that would be nice to have in the first release.
We have reviewed most of the PRs and don't see anything that would completely break things. But yes, changes will be necessary (e.g., documentation, etc.).

We are trying not to change too much (most changes concern variables, etc.). The basic technical functions should remain unchanged. The focus here is on improving usability, comprehensibility, code cleanliness, and better documentation.

Before a release, however, the open PRs will definitely be addressed and try to get them into a 0.1.0 version.