Draft dev notes

[pepe]

This is more of a features list than an issue. These ideas came to life when I coded a draft, but it was the culmination of longer-term musing about this problem domain.

Raw enumeration of the features:

• interactive
• full git after generation
  • init repo. Already there
  • add everything generated
  • commit with "Initial commit"
  • add origin from repository arg
  • push everything
• entry points in the lifecycle where the user can supplement her code to be executed in the context of the newt
  • through args as a string to be evaluated
  • through file parameter with specific API requirements on included fns, maybe Janet object with methods?
  • examples
  • generate package-specific project structure (joy, osprey, shawn) with the generated file contents
  • transform data sources to code
  • create a Dockerfile, CI, or .github configurations
  • tweet 'bout dat
• load .txt templates
• log what has been done

Some desired constrains:

• must be executable
• must be cross-platform
• must be documented ad nausea

Again I will edit with new ideas.

[pepe]

Our ambition should be to get newt under janet-lang as a standard CLI for generating new Janet projects :).

[yumaikas]

I would like to do that, in the long term. We're still a long ways out from that. That being said, I think we've got a good start with what's where now.

[pepe]

Can you please invite me to this repository?

[yumaikas]

Done.

[yumaikas]

So, I think the next big thing to do with newt is to switch newt to subcommands. This will enable things to be much more intentional, and will allow newt to grow much more, as well as allowing it to be much more specific with the generators