Real Favicon Generator is a handy tool for setting up your website’s favicon properly. It takes care of both the images (formats, resolutions, etc) and the HTML that you’ll need to include. With just a few clicks your website will work properly with browsers, operating systems, and mobile applications.
With so many platforms and icons, it’s hard to know exactly what you should do. What are the dimensions of favicon.ico? How many Touch icons do I need? RealFaviconGenerator did the reseach and testing for you.
If you still prefer to do it yourself and know all there is to generating proper favicon images and markup, have a look at this resource for everything there is to it and more.
- This document originated from a bunch of most commonly used links and learning resources I sent to every new web developer on our full-stack web development team.
- For each problem domain and each technology, I try my best to pick only one or a few links that are most important, typical, common or popular and not outdated, base on the clear trends, public data and empirical observation.
- Prefer fine-grained classifications and deep hierarchies over featureless descriptions and distractive comments.
- Ideally, each line is a unique category. The ” / “ symbol between the links means they are replaceable. The “, “symbol between the links means they are complementary.
- I wish this document could be closer to a kind of knowledge graph or skill tree than a list or a collection.
- It currently contains 2000+ links (projects, tools, plugins, services, articles, books, sites, etc.)
On one hand, this is one of the best single resources on the topic of web development that I’ve seen in a very long time. On the other hand, it re-confirms my belief in “there is no such thing as a full-stack web developer”. There’s just too many levels, and there’s too much depth to each level for a single individual to be an expert at. But you get bonus points for trying.
formapro/pvm is a PHP library for building workflows and business processes. This is a nice addition to alternatives that I’ve looked at in “Getting started with workflows in PHP“. The library is brought to you by Forma Pro, the same guys who are behind the php-enqueue enterprise queuing solution in PHP.
PHP Internals Book provides some insight into how PHP works internally. It currently covers PHP 5, with PHP 7 update coming soon. If you are eager to help, the book is available under Creative Commons on GitHub.
“Async PHP Requests & Reactive Responses with PHP-FPM” is talk by Holger Woltersdorf, in which he shares the approaches he tried for implementing asynchronous requests in PHP, and how he arrived at hollodotme/fast-cgi-client, which is a PHP fast CGI client for sending requests (a)synchronously to PHP-FPM.
Nginx blog (which, if you work with Nginx in any capacity, you should subscribe to) has an excellent guide to rate limiting. The article explains rate limiting from the basics, through bursts, all the way to more advanced examples, with multiple rate limits for the same location.
LINGsCARS.com deserves some kind of title and reward. I’m giving it a website of the day award, as I’m still stunned for words.
On one hand, it serves as a painful reminder of how the web used to be back in the 90’s. It got everything from psychedelic background and auto-played music to animated GIFs and mouse hover effects.
On the other hand, it does stand out from all pastel colored material designed websites of today. Obviously, a lot of work went into building this thing and … somehow … strangely … it works.
Now, please excuse me while I wipe my bloody tears…
P.S.: Yeah it also took me a while to actually prepare that screenshot. Full-page image was too large. Cropping it down significantly brought it down to just under 5 MBytes, after which TinyPNG compressed it to just 1.4 MBytes.
Mocka – simple and elegant content placeholder. Available as a Node.js package.
Making “Push on Green” a Reality is an insider look at how Google handles continuous deployment. Very few teams and companies need to deal with such level of complexity, but the overall principals still probably apply.
Updating production software is a process that may require dozens, if not hundreds, of steps. These include creating and testing new code, building new binaries and packages, associating the packages with a versioned release, updating the jobs in production datacenters, possibly modifying database schemata, and testing and verifying the results. There are boxes to check and approvals to seek, and the more automated the process, the easier it becomes. When releases can be made faster, it is possible to release more often, and, organizationally, one becomes less afraid to “release early, release often”. And that’s what we describe in this article—making rollouts as easy and as automated as possible. When a “green” condition is detected, we can more quickly perform a new rollout. Humans are still needed somewhere in the loop, but we strive to reduce the purely mechanical toil they need to perform.