Nice, I especially agree with this part: > ..find myself more productive if I can use tools that are well suited to how I think and work. so often I like to bu

Nice, I especially agree with this part: > ..find myself more productive if I can use tools that are well suited to how I think and work. so often I like to build my own tools. To be honest, I'm the same way. Over the years, I've always had a collection of custom libraries for common needs. I often enjoy writing my own library from scratch too, to understand how it works. Routers, databases, template languages, builders.. Sometimes, after developing it to satisfaction, I understand the value of a popular library that does the same thing, better designed or documented than what I built - in that case, I'm fine with transitioning to a better tool. There's definitely something to be said for well-crafted custom tools that work just how you want, intuitively. And you're right that's how popular projects all start out - so, if everyone used only what's available, we would never make progress. :) So what I wrote about using "community standard" libraries, maybe it was a kind of advice to myself.. > I was really about to kind of give up on this whole project when something's not working, I almost chucked it all the way but that sort of "last straw bug" never happened and I just pushed through. Right, I see, this is a kind of record of your journey to solve all the functionality you wanted in such a template project. > mark the moment..that I have achieved this Yes, congratulations on releasing it - that is an achievement worthy of itself. I think many of us can relate to being "scared to look foolish", and we should all feel encouraged to make things public, whether we're experts or beginners. I also agree that, we never know if something can be valuable to other people. Since your code is now open source, anyone can learn from your experience, and use it as a starting ground for their own applications.