Something that I am planning to implement
How about dependency version constraints for tutorials?
The most common questions/issues people have with my tutorials are:
- What Laravel version is this written for?
- This does not work for Laravel version x
- This used to work with package version x and Laravel version x
I knew that there was going to be an issue with this, so when I started Laravelista I decided to stay on the "bleeding edge".
Each tutorial is written with the latest available version (Laravel/package/...) at that moment. The versions can be seen in the repository on GitHub for each tutorial.
Issues arise when new versions of Laravel are released. Tutorials don't get updated to reflect the changes in the new Laravel version (be it Laravel or a package). Currently I have 44 tutorials. It is really unimaginable to update each tutorial to support the latest version of Laravel. That would demand a lot of work and it would not generate new content, it would only update existing content.
I considered making version constraints on tutorials from the beginning, but soon I realized that that would only limit the audience for that tutorial. What if the reader is working with version
1.2.3, and my tutorial covers version
1.3.1. It is not a big difference probably, but I personally would skip reading that tutorial since the version don't match.
I don't want to update a tutorial with new updated content, and lose old content in the process.
I'm thinking of versioning my content (tutorials) and release updated version on demand.
What do you guys/girls think of that? Is that something that you would like to see?