Development road map
5 February 2018 | 56 views | Tags: Documentation
One of they key goals of Tuskfish is to develop a stable platform that you don't have to update constantly. So, the roadmap, such as it is, is rather modest. Slated improvements are likely to include:
- Moving blocks to a separate database table with its own data entry form, probably as a module.
- Adding events as a new content type (TfEvent).
- Adding a secure machine interface to Tuskfish, for communicating with IOT devices (collecting data from remote sensors, etc).
- Adding a few dynamic block classes, including a list of recent content and a carousel.
- Add a security check to admin.php which will complain if you've left the installation directory on the server, or if your file permissions are wrong.
- Adaptation of some nice free third-party themes to work with Tuskfish, so that people can have more attractive out-of-the-box design options, including multi-column themes (if you can help out let me know).
- Improvement of TfCriteria class to allow nesting and formation of more complex queries.
- Add new TfDatabase method selectIntersect().
- Add language switcher tools.
- Removing HTMLPurifier from the front end; since all HTML content is input validated it's redundant and probably impacts performance.
- Add support for SQRL authentication, when it becomes available.
- Refactoring the structure of the Tuskfish code base to make it cleaner, easier to maintain and more atomic, in line with the principles discussed in Clean Code (yeah I just read it).
Copyright, all rights reserved.