I recently switched to SiteGround for hosting my sites, including this one. I lay out my rationale, along with the steps taken to make the move happen. I also reflect on the benefits of the move and how I found the process.
Agreed. It shouldn’t be necessary to remove content unless it is problematic, outdated, or just unneeded. .NET Magazine moved some of its online content to Creative Bloq, but left out much of the existing content. I know I’ve bookmarked a number of articles from the former’s website, so will have to look for those and update them if possible. Fortunately I’ve for some time used Evernote to clip and archive useful web content for later reference, just in case. This may well not be the case for the larger web however, though the Web Archive may be of some help.
This whimsically-titled page is in fact a concise resource for web developers. It covers numerous ways to optimize webpages for weight and speed, and is broken down into the following subtopics:
Optimization can seem like a dry subject, but this resource really simplifies the subject, pointing out the simple ways to make gains on page size and speed. Low-hanging fruit perhaps, but even those can add up!
A splendid roundup of articles and posts on how to maximize webpage and application performance. The entries are divided into multiple categories, including the basics, images, security, scripting, and tooling. There’s much good reading to be had here.
A community-driven effort to make web accessibility easier.
Has a checklist for common issues within accessibility, including colour contrast, form element usability, and ARIA roles. Also features a listing of related resources. Finally, periodic postings of additional considerations.
A Smashing Magazine article by Heydon Pickering on the nature of the HTML5 sectioning algorithm. Heydon covers how it works, the challenges in implementation, and some techniques for how to make it work. This article is an effective counter against some of the recent anti-sectioning treatises.
A really interesting look at how Wildbit converted a large existing stylesheet into multiple component SASS files. Shows how to leverage some of the strengths of SASS to reduce redundant CSS. Also ends with a summary of performance gains following the refactoring.