I don't like the docs / project description. Everything is made 'so simple' that important parts are now gone and everything is now pure magic, I guess. > We w

I don't like the docs / project description. Everything is made 'so simple' that important parts are now gone and everything is now pure magic, I guess. > We want to make it more trivial to build OCI compliant images without all the knowledge required to understand how Dockerfiles/Container Filesystem/BuildLayers/etc work As someone who understands how the above mentioned stuff works - I feel like I'm being forcefully excluded from the tool's target audience as I need explanations and the docs are written with such an idea in mind that it is something I shouldn't know. https://nixpacks.com/docs/how-it-works https://nixpacks.com/docs/how-it-works > Nixpacks works in two steps > Plan > Analyze the app source directory and generates a reproducible build plan. This plan can be saved (in JSON format) and re-used at a later date to build the image in the exact same way every time. How about an example of how a simple plan for a few projects would look like? Plus, the tool seems to assume too much: > To create the plan, language providers are matched against the app source directory and suggest Nix packages I don't need no Nix in my images, no thanks.