Useful tools and resources
7 February 2018 | 14 views | Tags: Documentation
I have found the following tools to be very useful while developing Tuskfish:
- ApiGen: Produces nicely formatted API docs from your code that are well organised and easy on the eye.
- Evernote: Was truly useful in tracking my project development and writing the documentation for it. There's a lot of note taking applications out there, but only Evernote does a good job of syncing across multiple machines and mobile devices.
- phpLiteAdmin: A web-based database management tool, kind of like phpMyAdmin but for SQLite.
- Netbeans: A free IDE that supports PHP.
- Death To The Stock Photo: Send you nice some stock photos each month, which you are allowed to use in your own projects and products. They also have a paid premium service.
- realfavicongenerator.net: A free site that will generate a suite of favicons and supporting code for the main operating systems, from a sample file. Also provides a good explanation and advice on the subject.
I found a few sites particularly useful in understanding some of the nitty-gritty detail of the internet:
- (The only proper) PDO tutorial: Given how important PDO is you'd think it would be well documented, wouldn't you? Nope. This site is essential reading if you want to use PDO. And I do mean essential.
- The Hitchiker's Guide to SQL Injection Prevention: I found this greatly clarifying. Basically, the zillions of byzantine SQL injection attacks we worry about have only one simple root cause: Improperly formatted queries. Now that you know that you can get on with actually fixing it, and detailed instructions are provided.
- What every developer should know about URLs: Everything you instinctively knew and some things didn't, written down in a clear manner.
Copyright, all rights reserved.
This guide will give you an overview of the architecture of Tuskfish CMS, how to write code to perform common operations and how to extend the system to suit yourself. The guide accompanies the Tuskfish API documentation. Keep a copy handy as you read this guide. It is best to review links to the API where provided, as not every detail will be discussed in the text. This is the first version of the guide, so it is still a work in progress.