Here is a suggested roadmap to make Nulla 1.0 (and Nullstack X:)
Nulla would become a real assistant while Nullstack would be the "magician". Nulla would be a cli containing everything that is helpful but opinionated (for example where to deploy)
When using nulla deploy vercel it should:
Supported hosts at 1.0:
Deploy via ftp/ssh would be nice because of Brazilian shared hosts
I would probably change some messages in Nulla cli, and I am not sure if having Portuguese support is needed, as code is normally made in English and the commands are simple. Removing Portuguese would make the codebase easier to contribute to, and also faster to ship. However is we keep Portuguese we should also translate Nullstack cli
Here is a suggested roadmap to make Nulla 1.0 (and Nullstack X:)
Nulla would become a real assistant while Nullstack would be the "magician". Nulla would be a cli containing everything that is helpful but opinionated (for example where to deploy)
nulla start/build(leave it to Nullstack so it does not duplicate commands)nulla startas a command to run Nullstack in production mode (could start .production/server or server static assets depending on the use case)nulla add(temporarily), plugins will not be part of Nullstack 1.0 but a revamp on them will be one of the first things to be codedWhen using
nulla deploy vercelit should:Supported hosts at 1.0:
Deploy via ftp/ssh would be nice because of Brazilian shared hosts
I would probably change some messages in Nulla cli, and I am not sure if having Portuguese support is needed, as code is normally made in English and the commands are simple. Removing Portuguese would make the codebase easier to contribute to, and also faster to ship. However is we keep Portuguese we should also translate Nullstack cli