Fair enough I guess.
That said, I don’t think it’s Particle’s responsibility to provide folks with tutorials on how to program/connect, especially everything non-Particle specific. The Particle system from the outside can be treated as a black-box with a REST interface. No need to know what’s going on behind the scenes, just need to know how to get the data to/from the API. How you then choose to work with that API is entirely up to you.
That’s not to say it wouldn’t be nice if there were more elaborate tutorials, sure, but I can understand it’s not a priority to teach people how to set up a database, code an app or make a website. Those things are separate from the Particle ecosystem, and there are plenty of resources available on how to do most of those things. The best approach then would be to make sure the interactions are as smooth and easy as possible, which a REST API caters nicely to.
What content is missing that is Particle specific, as in, applies only to Particle? Showing folks how to make a connected weather station with a web interface and app is ‘merely’ a combination of stand-alone pieces. That would not be ‘eligible’ for a high-priority tutorial if it were up to me. Showing a complete example of a product with user various methods of user authentication would me more preferred, and is also Particle-specific.
I think it’s a matter of figuring out what’s out there already, though it might not be labeled ‘… Particle…’. A lot of ‘things’ already exist, which, when combined, can create many of the projects people are looking for. The missing pieces are where Particle could/should(?) step in.
I hope that sort of makes sense