Is your request related to a problem?
Given that most people who use markbind would typically be using git to version control a markbind project, currently it's a tiny bit of a hassle to manually create a .gitignore when generating a new site using markbind init.

Describe the solution you'd like
Would be nice if a sensible .gitignore file is added. In particular, to ignore log files and maybe .env as well as _site.

Describe alternatives you've considered
Minimally, would be nice to provide a suitable example of a .gitignore file, perhaps as part of GitHub .gitignore templates

Additional context
Might also want to consider generating a package.json file that will be able to track the markbind-cli version.

• If package.json is added, the .gitignore file will need to ignore /node_modules

TODO for PRs targeting this issue

• generating a .gitignore when markbind init is called
• either skip or possibly override for the --convert flag (Preferably skip)
• update UG docs on this behavior

This is possibly breaking change