Rail Course and Asset strategy
Added 2019-01-13 09:50:49 +0000 UTCAfter being sick for quite a while I came back to the railsystem. Taking back a step from a project is sometimes a very good thing.
In this case I decided to change my approach in regard to the assets I am using. In my initial creation process I started creating the polyshifter for tasks that I would need more than once.
But at the same time I want to keep developing that asset unrelated to the railsystem which will make it a hassle to keep it organized.
So just in the right moment to continue the rail course And just when I first applied using the multiple asset approach - this is what I am going to change.
All functionality that feeded the initial polyshifter setup will be added as a tool to the rail asset itself. That way developement on several assets is unrelated to each other AND going into the course you can follow the creation of ONE asset with all the tools needed.
This also makes the railsystem one package which could be open to non-patreons while keeping the polyshifter exclusive to Patreon.
Cheers
David
