I removed avatar.png as it is no longer being used and has been replaced with logo.svg.
If an admin uploads a custom logo, this will take the place of avatar.png and will be used as the new logo.
As part of the new logo (https://github.com/JulianPrieber/littlelink-custom/milestone/1) I'm now using the new 'logo.svg' vector logo.
For this, I added an if-else statement in most cases, which first check for a custom logo uploaded by the admin or the avatar of an individual user. If the image doesn't exist, the default logo (logo.svg) is used.
Added automatic dark mode detection to littlelink.blade.php via a cookie with js.cookie.min.js (see previous commit).
Detecting the dark mode setting is done with JavaScript. The script detects the preferred dark mode setting in the client's browser and saves it with a cookie. If the script detects a change in this setting, it corrects the cookie.
Loading the appropriate skeleton.css is done via PHP with an if-else statement. If the cookie (saved by the previous script) color scheme equals 'dark' it will load skeleton-dark.css (found in /littlelink/css).
If dark mode is not detected OR nothing is detected/cookie is getting blocked, the statement defaults to skeleton-light.css (also found in /littlelink/css).
You could change what the if-else statement defaults to (i.e. which color scheme is loaded if the cookie fails to detect) by switching 'skeleton-dark.css' and 'skeleton-light.css' around (see comment in if statement).
Everything added is commented and marked with begin/end.
Credit to 'user1575941' on Stack Overflow who's commented code REALLY helped getting behind all this.
Added automatic dark mode detection to home.blade.php via a cookie with js.cookie.min.js (see previous commit).
Detecting the dark mode setting is done with JavaScript. The script detects the preferred dark mode setting in the client's browser and saves it with a cookie. If the script detects a change in this setting, it corrects the cookie.
Loading the appropriate skeleton.css is done via PHP with an if-else statement. If the cookie (saved by the previous script) color scheme equals 'dark' it will load skeleton-dark.css (found in /littlelink/css).
If dark mode is not detected OR nothing is detected/cookie is getting blocked, the statement defaults to skeleton-light.css (also found in /littlelink/css).
You could change what the if-else statement defaults to (i.e. which color scheme is loaded if the cookie fails to detect) by switching 'skeleton-dark.css' and 'skeleton-light.css' around (see comment in if statement).
Everything added is commented and marked with begin/end.
Credit to 'user1575941' on Stack Overflow who's commented code REALLY helped getting behind all this.
Added automatic dark mode detection to home.blade.php via a cookie with js.cookie.min.js (see previous commit).
Detecting the dark mode setting is done with JavaScript. The script detects the preferred dark mode setting in the client's browser and saves it with a cookie. If the script detects a change in this setting, it corrects the cookie.
Loading the appropriate skeleton.css is done via PHP with an if-else statement. If the cookie (saved by the previous script) color scheme equals 'dark' it will load skeleton-dark.css (found in /littlelink/css).
If dark mode is not detected OR nothing is detected/cookie is getting blocked, the statement defaults to skeleton-light.css (also found in /littlelink/css).
You could change what the if-else statement defaults to (i.e. which color scheme is loaded if the cookie fails to detect) by switching 'skeleton-dark.css' 'skeleton-light.css around' (see comment in if statement).
Everything added is commented and marked with begin/end.
Credit to 'user1575941' on Stack Overflow who's commented code REALLY helped getting behind all this.
Live demo: https://julianprieber.github.io/littlelink-admin-demo/button-entrance.html
Added an entrance animation for buttons on home.blade.php. This animation was made by the Animate.css project (https://github.com/animate-css/animate.css).
Each button entrance animation lasts 100ms. Every button after the first adds 100ms to the value of the previous button i.e. button 1 loads after 100ms, button 2 loads after 200ms, button 3 after 300ms and so on...
Timings for the buttons can be changed in /littlelink/css/animate.css
I put every button in a separate <div> Tag, so the animation wouldn't in interfere with the existing hover animation.
Live demo: https://julianprieber.github.io/littlelink-admin-demo/button-entrance.html
Added an entrance animation for buttons on littlelink.blade.php. This animation was made by the Animate.css project (https://github.com/animate-css/animate.css).
Each button entrance animation lasts 100ms. Every button after the first adds 100ms to the value of the previous button i.e. button 1 loads after 100ms, button 2 loads after 200ms, button 3 after 300ms and so on...
Timings for the buttons can be changed in /littlelink/css/animate.css
I put every button in a separate <div> Tag, so the animation wouldn't in interfere with the existing hover animation.
Likewise, I removed all <br> Tags.
This is the last major public path edit. For simplified usability, I am integrating the public Laravel directory into the root directory.
All files in /public have been moved into the root directory. This directory is no longer necessary and therefore has been removed.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
hover-min.css has been moved!
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
Added hover-min.css (button animations)
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
Changed path /public to root directory.
!!!NEEDS TO BE TESTED!!!
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
Changed path /public to root directory.
!!!NEEDS TO BE TESTED!!!
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
This edit is part of moving everything from root/public to root.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
Fixed path (removed '/..' ). Index.php will be moved to into the root directory.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
This is one of multiple public path edits. For simplified usability, I am integrating the public Laravel directory into the root directory.
For this, I am changing every instance of 'public_path' to 'base_path' and will use this format in future changes as well.
JulianPrieber
