-
-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mention Spin to create new projects #42
base: master
Are you sure you want to change the base?
Conversation
I would indeed move it lower, after the script but before opam, because Dream has a sort of "opt-in" design, where you start with the minimal and know exactly what you're adding every step of the way. However, a hypothetical higher-level framework based on Dream might do it the other way. But that higher-level framework might be just a good template :) |
5880b21
to
a63867d
Compare
If it helps to make it more visible, maybe it can get a section heading. Like "### Starter project" or "### Project template" |
fb17623
to
a3bc25b
Compare
6d89668
to
6169984
Compare
@aantron I improved the Spin template substantially (all of the features are now optional), and the latest Spin release comes with an Opam plugin, so with Opam installed, users can run:
I'm happy with the state of the workflow, so this is ready to review if you want 🙂 |
Thanks! I opened several issues and PRs in the spin-dream repo. |
This PR recommends Spin to create new Dream projects in the Quickstart section.
I've put the mention of Spin higher than the quickstart script, but of course, I'm happy to change that if you feel the middleware example is a better entry point for new users.
I'm creating the PR as draft as there are a few things I'd like to add to the template before it is recommended. Namely, making the setup of TailwindCSS and Turbolink optional, and adding some boilerplate examples with Caqti.