A Selection of Festive Websites to Get You in the Mood for Christmas – Get into the holiday spirit with these fun sites.
10 diagrams to help you think straight about UX Research – Use these diagrams for a simpler approach to UX.
A CSS Venn Diagram – Learn the process behind creating a beautiful Venn diagram.
What We Talk About When We Talk About Design Ethics – A look at the ethical responsibilities of a designer.
What WordPress 5.0 Taught Me About Stress – So much drama. Yet, was it really worth getting so stressed about?
Rallax.js – A vanilla JavaScript plugin for parallax scrolling.
Animation principles for UX and UI designers – Why our approach to animation shouldn’t be an afterthought.
CSS & JavaScript Snippets for Creating Infographics – Going beyond static infographics by adding interactivity and responsiveness.
A Recap of Frontend Development in 2018 – A look at the past year in JavaScript and other notable events.
20 web design trends for 2019 – What will define the web in the next year and beyond.
Rocking the Boat: Examining the Use of Waves in Web Design – Waves are about more than just water. See some stunning examples of how the effect is being used.
A new logo for Unsplash – A look at the incredibly simple, yet very distinctive new logo.
Researching a Property in the CSS Specifications – How to make sense of CSS specs on your own.
An Introduction and Guide to the CSS Object Model (CSSOM) – You’ve used the DOM, but do you know the CSSOM?
The Cheapskate’s Guide to WordPress Plugins – Learn a few tricks that could save you from spending on that commercial plugin.
Universal Text Styler – Text styles that work everywhere – including social media posts!
Remove.bg – Upload a photo and this tool will make the background magically disappear.
Follow Speckyboy on Twitter, Facebook or Google+ for a daily does of web design resources and freebies.
The post Weekly News for Designers № 468 appeared first on Speckyboy Web Design Magazine.
The Laravel News site has posted the latest part of their "Building a Laravel Translation Package" series focusing on a pre-launch checklist of items to get in place before it's finally released.
In the last part of the series, we finished up building the Laravel Translation package. With this completed, we are ready to start thinking about releasing the it to the world. However, before we do, there are few important steps we need to take.
The post covers some of the final non-code items to take care of:
Each item in the list includes a brief summary of what's involved and, for some, links to other resources and tools that can help get it accomplished.
In a recent post to his site Eduards Sizvos shares an opinion that's believed by many in the development world: stop learning frameworks.
We are developers. We need to stay up to date with technology. Every day, we learn programming languages, frameworks, and libraries. The more modern tools we know?—?the better.Keeping up to date with Angular, React, Vue, Riot, Ember, Knockout is fun.
But we are wasting our time.
He goes on to talk about time, how important it is to spend on the right things and offers a story of his own where learning specific technologies didn't help in the long run. He then shares some resources (books) to help you learn good concepts instead of specific tools.
Remember – frameworks, libraries and tools come and go. Time is precious. Invest your golden time in transferable skills. Skills that will always be relevant.
Derick Rethans has shared a post on his site with an experience he had with a mystery of missing breakpoints and some issues he commonly is asked about regarding Xdebug's breakpoint functionality.
Occasionally I see people mentioned that Xdebug does not stop at certain breakpoints. This tends to relate to multi-line if conditions, or if/else conditions without braces ({ and }).f you set a breakpoint at either line 7, 11, or 12, you'll find that these are ignored. But why is that?
To help explain, he uses the vld tool to show the opcode behind the language's processing. In its results you can see that a EXT_STMT code is missing for the lines where the breakpoints were set. Xdebug doesn't see the marker it's expecting so the breakpoint isn't recognized and execution isn't halted as expected. He offers some suggestions you can use of other tools and functions to make sure the location you've selected can actually accommodate a breakpoint.