Please note: Instructions for use of this application are available on the login page.
The purpose of this site is to serve as a portal for Mako drivers in Colorado. It has 3 functions:
- To serve as a single launchpad for filing reports with one click.
- To notify drivers of who is currently in the office if they need to contact a LTCF staff member directly (zero count, traffic accident, other concerns…)
- To provide current notices and updates for drivers so they are all armed with the latest information.
The design principals of the site are as follows:
The Site Should Be Easy To Maintain & Operate Without Any Previous Experience
Upon login, users will be greeted with a tutorial for adding/removing LTCF in the office and their phone numbers, toggling them “on” and “off” in relation to their office presence, and adding new notices. Maintaining the framework is handled automatically in the background and that framework is based on the most widely used components, meaning development will be continuous and hands-free.
Excess Time Should Not Be Wasted On Development
This one is more about me. This site has been built as quickly and “down and dirty” as possible. We do not care about SEO or a lot of other considerations that go into development, and take time away from more important Mako duties. This site is just a simple tool, and effort should not be wasted on making it anything more.
Anyone Should Be Able To Administrate The Site With No Previous Experience
The operation of the site (adding/removing users, moderation of content, extending capabilities) should not require any special skills.
Our Company Process Should Not Require Modification
Everything here should be based on existing systems, processes, and methodologies. This site functions based on our process, and should not require us to change the way we do anything.
Where This Site Stands Now:
Development has been suspended. Further development would require additional time and the result may not be needed or desired. Future potential developments could include a way for each driver to log into their own page to view and confirm their routes, and give us a cleaner path for route additions and skips. This would be tied into existing sheets so that the route deployment method is more automated. We have other ideas too… but at present this site has already met the original design objectives, and unless instructed otherwise, we are not planning to develop it further.
