# times Published articles for times. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to automatically add WebP post banners to Jekyll for faster load times DevFeed: [How to automatically add WebP post banners to Jekyll for faster load times]() Original publisher: [Read original article]() Author: Jake Lee Published: 2024-11-30T00:00:00Z Content type: tutorial Language: en Sources: [Jake Lee's Programming Blog]() Topics: [Jekyll](), [Web Development](), [Accessibility](), [browsers](), [CSS]() Tags: [accessibility](), [how-to](), [images](), [jekyll](), [liquid](), [optimisation](), [times]() ### AI overview A tutorial on automating WebP banner generation and delivery in Jekyll. It explains configuring a conversion library, generating WebP files, serving them conditionally with Liquid and picture/source elements, and providing alternative text. The article also notes possible color-rendering issues with the converter. ### Source excerpt Most modern browsers can handle the smaller & speedier WebP versions of images, yet generating them manually can be a pain! Here's how to do it automatically in Jekyll. ## The Nuts and Bolts with Tom Drapeau DevFeed: [The Nuts and Bolts with Tom Drapeau]() Original publisher: [Read original article]() Author: Squarespace Engineering Published: 2021-10-15T16:08:12Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [engineering-culture](), [Job]() Tags: [culture](), [manager](), [q-a](), [team-lead](), [times]() ### AI overview A Q&A with Tom Drapeau about moving from engineering into management, choosing an Engineering Director role at Squarespace, and defining and building engineering culture. ### Source excerpt "The Nuts and Bolts" is a reoccurring Q&A with Squarespace engineers. Questions are compiled by their peers to guarantee we get right to the good stuff. ## Speeding Up Tailwind CSS Builds DevFeed: [Speeding Up Tailwind CSS Builds]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-10-13T12:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Tailwind CSS](), [build times](), [PostCSS](), [Development](), [Web Development]() Tags: [build](), [build-times](), [builds](), [css](), [development](), [frontend](), [how-to](), [insights](), [learn](), [live](), [local](), [magnitude](), [make](), [module](), [optimize](), [orders](), [performance](), [postcss](), [reload](), [replacement](), [tailwind](), [times]() ### AI overview A tutorial on optimizing Tailwind CSS builds in local development. It explains how splitting CSS imports can avoid reprocessing the full Tailwind utilities stylesheet during ordinary CSS changes, improving Hot Module Replacement and Live Reload responsiveness. ### Source excerpt Learn how to optimize your Tailwind CSS PostCSS build times to make local development with Hot Module Replacement or Live Reload orders of magnitude faster! ## Cutting the Cord: Removing Craft CMS 3 Plugins DevFeed: [Cutting the Cord: Removing Craft CMS 3 Plugins]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-03-19T13:56:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System]() Tags: [cms](), [craft](), [don-t](), [fantastic](), [functionality](), [insights](), [let-s](), [need](), [plugins](), [times](), [unplug]() ### AI overview This tutorial explains how to remove unnecessary Craft CMS 3 plugins by using functionality available natively through Twig and Craft CMS services. It focuses on replacing three plugins with built-in capabilities while exploring Craft CMS's broader functionality. ### Source excerpt Plugins are a fantastic way to add functionality to Craft CMS 3. However many times, you don't need them at all. Let's unplug! ## Tips for optimizing CakePHP applications to improve response times and reduce costs DevFeed: [Tips for optimizing CakePHP applications to improve response times and reduce costs]() Original publisher: [Read original article]() Author: Juan Basso (juan.basso@zumba.com) Published: 2012-11-05T00:00:00Z Content type: tutorial Language: en Sources: [Zumba]() Topics: [optimize](), [save]() Tags: [applications](), [better](), [money](), [optimize](), [save](), [times](), [tips]() ### AI overview The article offers tips for optimizing CakePHP applications to improve response times and reduce costs. ### Source excerpt Few tips in how optimize CakePHP applications to get better response times and save money ## Introducing MoqContrib Auto-mocking Container DevFeed: [Introducing MoqContrib Auto-mocking Container]() Original publisher: [Read original article]() Published: 2011-04-06T00:00:00Z Content type: release Language: en Sources: [Tim Kellogg]() Topics: [Mocking](), [IoC (Disambiguation)](), [unit tests]() Tags: [mocking](), [object](), [release](), [service](), [setup](), [tests](), [times](), [unit-tests](), [verify]() ### AI overview The article announces MoqContrib Auto-mocking Container, an inversion-of-control container for Moq Contrib intended for use with unit tests and mocking. An alpha release is planned first for Castle.Windsor, followed by Autofac support. ### Source excerpt The past couple weeks I have been working on an auto-mocking inversion of control container for Moq Contrib. The first results are almost ready to release in the form of an Alpha. The first container to be released will be Castle.Windsor, later we will release an Autofac container.You will be interested in this project if you use an IoC container in conjunction with unit tests and mocking (with Moq). You probably find yourself writing setups like:[SetUp]public void Given(){ _service = Mock(); Container.Register(For().Instance(service.Object));}[Test]public void I_did_something() { var test = new TestThingy(); test.DoSomething(); _service.Verify(x => x.Something(), Times.Once();}When you use an auto-mocking container, the container will create mocks at resolve-time if it doesn't already have a component for it. So in the above example, the setup would drop out completely as there wouldn't be any need to explicitly create and register the mock:[Test]public void I_did_something() { var test = new TestThingy(); test.DoSomething(); _service.Verify(x => x.Something(), Times.Once();}We will release an alpha version of the Castle.Windsor auto-mocking container later this week. Soon after we will add an Autofac container and start working towards a regular release schedule. If you are interested, visit the site at codeplex and give feedback through the discussion groups.Happy Mocking!