Yes, I’ve already started to build my plans around that so thanks.
In part, your contribution is the reason for my post - you have extended the ecosystem to try and cover a missing part of the offering, but to use your work I’m having to first still understand the ecosystem.
I can give a simple example, by just following the docs from the Installation page under Setup & Deployment section.
-
The page gives me 2 options of CLI or Docker, but the Docker option is noted as creating a customer Docker container from a local project and as I do not yet have a local project it is not a valid option. So CLI is my only choice even if 2 were provided.
-
After some basic notes I reach a section titled “Creating a Strapi project” which talks about cli switches, but I need to go to another page to find out about the actual cli command. Normally documentation starts with the command and then details the switches.
-
The new page seems designed to test to see if I read everything on a page as you have to read the provided note to find out that the examples provided need to be prefixed with the correct npm/yarn command (that’s nice, now remember I know nothing about the JS ecosystem so that info does not really help).
-
Well I managed to create a valid ecosystem, shame that the ubuntu/debian universe seems to have spent at least 5 years arguing with the yarn team, so all I need to do now is just run “npm run strapi new project” to get a basic setup as that is what the page indicates… Even I can tell that that’s not going to work as strapi is unlikely to be part of the core js ecosystem I have managed to deploy and guess what it does not.
-
So back to the install page and onto the next section. Well, I have no idea what npx is but the whole line has the look of a package installer. So lets run it with some general values and yes it does an install. Now, let’s run it with some different options as getting dropped into a different shell of some type, while a browser is opened up is not that helpful.
-
I now have a directory, which I can now execute “npm run strapi new project” in and I would guess your project.
It was at this point I decided to write my post as it was clear that JS/JT experts have basically created and documented a whole project that is aimed at JS/JT experts and that by accident (or design) excluding everyone else is not the best of ideas. Tomorrow I will continue this game of discovery.