I think we should maintain changelog to the separate md file and add link of this file to readme doc. It will make clean to our readme file.

After updating from v3.0.0.beta1 to komposable/komponent@d1ae3df to make komponent work after a Rails 6 update, the komponent components themselves are showing up in the styleguide sidebar:

I'm seeing something like this in my current styleguide:
![Bildschirmfoto 2020-03-10 um 13 45 07](https://user-images.githubusercontent.com/3320662

this is valid ruby, should not be flagged

Please help to figure out how to change path to documentation so that I won't need to place it under 'public/swagger_docs/v1/swagger.json'?
I'm used to use https://github.com/brennovich/ruby-swagger and with Rails update 'swagger_engine' is not working anymore (of course).
I could write task for copying .json file everytime it's generated, but that's not nice.

If one does not use the default postgress username and password in their local postgres installation, it would be nice if they are able to change the database username and password in a .env file which is not tracked by git. For a person using the default username and password, the workflow should remain as is currently.

Expected Output

Developers can change their database credentials in th