- Switched PicoCMS assets to use Composer
- Updated insecure jQuery version
- Protocol relative URLs (HTTP / HTTPS)
- Diagram redesigns
- Anchor links in Howto
- Unused assets purged
- PicoCMS backend
- Rewrite of CSS theme to Bootstrap 4
- Responsive theme for small screens / mobile devices
- Yarn to keep site dependances up-to-date
- Simplified JS code
- Security fix: the http referrer for all visitors is stored in a plaintext .dat file. Malicious PHP code could be injected if the webserver is set to interprete all file extensions for PHP code (non-standard setup)
- Minor changes to content by Cory
- Relicensed under the MIT License
- Source Code / git repo uploaded to GitHub
- Added events widget that shows the current show/event the company is at or selects the nearest one with a friendly 10 day countdown.
- Code to prevent FOUC on the jQuery sliders
- New theme based off of Frooition theme for ChannelAdvisor webstore
- CMS is a rehaul of the txtbuch beta engine
- Pages coverted to markdown and images optimized
- Bugfixes for Internet Explorer div widths
- background images reduced in size and tiled via CSS
- changed fixed width to fluid width
- header contact info image replaced with actual text for SEO
- newsletter page and signup form
- contact information in footer of webpage
- store hours JavaScript that identifies today's hours and any special holiday hours
- Switched from SQLite database to serialized arrays stored in .dat files
- Simple visitor logger with currently online support
- PSR-3 compatible logger
- txtbuch core live, running first ecommerce website
- engine seperated from website content so changes can be tracked easier from a git repo, using softlinks to include engine into website
- Javascript init system lazy loads needed libraries and CSS based on each page's content. Site theme can also lazy load additional components as needed.
- Simple theme engine using {{ var }}. Special variables for calling a function {{ func_$name }} and including a file {{ inc_$name }}
- Redesigned old txtbuch engine to be more modular. Somewhat MVC; site content is located in a seperate content folder.
- Reusable code organized into file libraries based on what they do (ie: func_arr.php has functions that operate on arrays)