# making Published articles for making. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Making of a Logo DevFeed: [The Making of a Logo]() Original publisher: [Read original article]() Author: Paul Lewis Published: 2025-01-15T00:00:00Z Content type: opinion Language: en Sources: [Paul Lewis]() Topics: [Website](), [blender](), [3D](), [stl](), [SVG](), [export](), [render](), [Sketch]() Tags: [3d](), [3d-printed](), [blender](), [cameras](), [export](), [file](), [logo](), [making](), [render](), [stl](), [svg](), [update](), [website]() ### AI overview The author describes creating a new Aerotwist logo, starting with sketches on a reMarkable 2 tablet, refining it as a vector and SVG, and preparing it for 3D printing by exporting an STL from Blender. ### Source excerpt A new website, and a 3D printed logo! ## Six Strategies for Making Data Visualizations Accessible, Scalable, and Helpful DevFeed: [Six Strategies for Making Data Visualizations Accessible, Scalable, and Helpful]() Original publisher: [Read original article]() Published: 2022-11-08T13:00:00Z Content type: tutorial Language: en Sources: [Material.io - Material Design]() Topics: [Data visualization](), [Accessibility]() Tags: [accessibility](), [accessible](), [data](), [data-visualization](), [making](), [strategies](), [tips](), [visualization]() ### AI overview The article presents six strategies for making data visualizations accessible, scalable, and helpful. ### Source excerpt Six strategies for making your data visualization accessible, scalable, and helpful ## Supply chain integrity with GoReleaser using Go mod proxy DevFeed: [Supply chain integrity with GoReleaser using Go mod proxy]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-08-23T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [integrity](), [Go Language](), [proxy](), [builds](), [hash](), [opensource]() Tags: [builds](), [go](), [hash](), [making](), [opensource](), [proxy](), [supply-chain-integrity]() ### AI overview This tutorial explains how to verify Go binaries built with GoReleaser by using the Go module proxy and comparing module hashes. It also discusses signing, reproducible builds, and limitations involving dependencies and non-open-source GoReleaser Pro. ### Source excerpt Since the infamous SolarWinds attack, supply chain integrity is something a lot of people are discussing and working on. ## An Annotated Docker Config for Frontend Web Development DevFeed: [An Annotated Docker Config for Frontend Web Development]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-03-22T16:12:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Docker](), [Web Development](), [DevOps](), [Development](), [Docker Compose](), [Dockerfile]() Tags: [allows](), [apple-silicon](), [config](), [development](), [devops](), [docker](), [docker-compose](), [environment](), [frictionless](), [frontend](), [insights](), [local](), [making](), [multi-arch](), [needs](), [onboarding](), [project](), [shrink-wrap](), [web-development]() ### AI overview This tutorial explains how to use Docker as a local development environment for frontend web projects. It presents a reusable configuration approach that packages each application with the environment and service versions it needs, making environments reproducible, disposable, and easier to share. Examples reference Craft CMS, Laravel, NodeJS, and Rails, with multi-architecture base images available for Apple Silicon. ### Source excerpt A local development environment with Docker allows you to shrink-wrap the devops your project needs as config, making onboarding frictionless ## Some brief notes on making ethernet cables DevFeed: [Some brief notes on making ethernet cables]() Original publisher: [Read original article]() Published: 2017-09-30T18:07:40Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [Ethernet](), [Tool]() Tags: [cat6](), [connectors](), [equipment](), [ethernet](), [guide](), [making]() ### AI overview A practical guide to making and routing Ethernet cables. It cautions that crimping is difficult, recommends buying ready-made cables when possible, and discusses suitable tools, connectors, cable types, and pulling cable through conduits. ### Source excerpt Some brief notes on making ethernet cables With thanks to the most excellent NLNOG for a lot of mostly correct advice! Friends will tell you "crimping" ethernet cables is easy. Most of your friends either have overly rosy memories, or have practiced on 200 cables before telling you it is now easy. It is not easy. This page is for if you have a few extra euros/dollars/coins to spare, and don't want to spend rare hours of concentrated effort to crimp an ethernet cable using unfamiliar equipment and supplies. ## Making Websites Better through Accessibility DevFeed: [Making Websites Better through Accessibility]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-07-23T22:42:00Z Content type: article Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Accessibility](), [Website](), [Development](), [User interface design]() Tags: [accessibility](), [accessible](), [away](), [compliance](), [customers](), [development](), [insights](), [isn-t](), [just](), [legal](), [making](), [means](), [turning](), [ux](), [wants](), [website]() ### AI overview The article explains that website accessibility helps organizations reach more people, avoid excluding customers, and support inclusive products and services. It discusses legal requirements under the Americans with Disabilities Act in the United States and recommends integrating accessibility into design and development workflows. ### Source excerpt Making your website accessible isn't just about legal compliance, it also means not turning away customers. Because who wants to do that? ## Making Customer Support Requests Visible in Real Time to Measure End-User Quality DevFeed: [Making Customer Support Requests Visible in Real Time to Measure End-User Quality]() Original publisher: [Read original article]() Author: espen Published: 2011-07-04T06:50:39Z Content type: article Language: en Sources: [Finn.no]() Topics: [Support](), [Logging](), [real-time](), [HTML](), [App]() Tags: [customer-service](), [html](), [logging](), [making](), [persistence](), [real-time]() ### AI overview The article describes an effort to make customer support requests visible in real time across an organization so teams could better understand the quality of their work. Because existing ticketing and call-center statistics lacked detail, the team observed the support process, introduced paper-based logging, and created an HTML prototype based on that workflow. ### Source excerpt In the post Putting a face on quality we talked about how we wanted to bring our end users closer to our developers by visualizing tweets about our service. This was only one of many tasks we performed in order to get a better feel on how our work effects our users. In this post we'll show you what we did in order to put numbers on end user quality by working with out customer service team. Up until now our customer service team had a hard time visualizing the effect our code had on end users. They where publishing numbers on number of incoming requests, but these numbers where on a weekly basis at best. Research in the wild Therefor we set out with the goal of making all support requests visible in real time for the entire organization. Out hypothesis was that this would provide everyone on our teams from developers, product owners and sales staff with a clear view on what kind of quality they deliver. In order to figure out what our application should look like we set out to see what the reality was and sat with our customer service team to see how they worked. But they had no system in place for logging requests and what area of our service it was about. All we had was the statistics from our support ticket system and call center. These systems did not provide enough detailed information, therefor our Lean task force team encouraged them to start logging requests on paper then put it all into a set of Excel spread sheets. Needless to say this required quite a bit of effort from the people one the customer service team and it was not a solution for the long term. When deciding how to approach creating a application for logging requests we looked at how the analog logging process was performed. Realizing that a request could be for more than one problem area and effect multiple teams we realized that the paper layout was in fact ideal. We created a quick prototype in HTML and had the users test it. This prototype had no persistence and did only show how the process