Styleguide | Task
This is the official Task styleguide for Taskfile.yml files.
Task is a task runner / build tool that aims to be simpler and easier to use than, for example, GNU Make.
Since it's written in Go, Task is just a single binary and has no other dependencies, which means you don't need to mess with any complicated install setups just to use a build tool.
Wails | Build beautiful cross-platform applications using Go
Wails is a project that enables you to write desktop apps using Go and web technologies.
Consider it a lightweight and fast Electron alternative for Go. You can easily build applications with the flexibility and power of Go, combined with a rich, modern frontend.
Also:
https://fyne.io
Naming colors in design systems
Spectrum’s colors are mapped to our design tokens, which are all the values needed to construct and maintain a design system—such as spacing, color, typography, object styles, and animation—represented as data. Our naming decisions for Spectrum leverage industry terminology and commonly known terms whenever possible, so we avoid choosing names for colors that wouldn’t be recognizable beyond the design and development community. We also avoid names that are trendy, subjective, or in languages other than U.S. English.
https://spectrum.adobe.com/page/color-system/
https://spectrum.adobe.com/page/color-palette/
https://uxdesign.cc/how-should-you-name-your-colors-in-a-design-system-3086513476df
Pattern Club | Find Pattern Inspiration
A curated gallery of patterns, textures & visuals by awesome designers & illustrators
mbutterick/pollen: book-publishing system - pollen - Gitea: Git with a cup of tea
pollen - book-publishing system
Camera obscura: the case against AI in classrooms: Matthew Butterick
Research means more than fact-checking
When I first used GitHub Copilot, I said it “essentially tasks you with correcting a 12-year-old’s homework … I have no idea how this is preferable to just doing the homework yourself.” What I meant is that often, the focus of programming is not merely producing code that solves a problem. Rather, the code tends to be the side effect of a deeper process, which is to learn and understand enough about the problem to write the code. The authors of the famous MIT programming textbook Structure and Interpretation of Computer Programs call this virtuous cycle procedural epistemology. We could also call it by its less exotic name: research.
Perceptually uniform color models and their implications / Max Bo | Observable
This notebook was created as a learning exercise to teach myself about color theory. I have interleaved some lightly altered prose from a variety of sources which I found informative, which I have made a best attempt to cite in the References section at the end of the notebook. I would like to extend my thanks to the cited authors for their work. Munsell color system Albert Munsell, an artist and professor of art at the Massachusetts Normal Art School wanted to create a rational way to describe color
Munsell color system
Typography Manual by Mike Mai
A set of rules that will improve your typography 10x.
Use Traditional Point Sizes
Display Double Canon 4.666
Heading 1 Canon 3.999
Heading 2 Double Great Primer 2.999
Heading 3 Double English 2.333
Heading 4 Double Pica 2.000
Heading 5 Paragon 1.666
Heading 6 English 1.166
Body Pica 1.000
Fine Print 1 Small Pica 0.916
Fine Print 2 Bourgeois 0.750
Use Serif for Italic Text
Reduce Heading Spacing
The spacing between a heading and a paragraph should be less than the regular paragraph spacing. If regular paragraph spacing is used instead, the heading would seem too far away from the paragraph.
Use Thin Space
Thin Space might be the most underrated HTML entity. It can be used for a name like J. K. Simmons. Without spacing, the J and K would seem too close together; with a regular space, they seem too far apart. Insert a thin space and it is just perfect.
The HTML code is . You can go even further with Hair Space
Don’t Use Helvetica, Inter, & Roboto
It's time to learn oklch color
I think the biggest bang for your buck is to learn OKLCH (or, “Oklachroma”)
- It’s based on human perception
- It can define any color
- the chroma value is a number between 0 and 0.37
I Restored a 1950's Boston "Champion" Pencil Sharpener - Reddit
Finished! Ready for the next generation of pencil sharpening! I made a full restoration video of the project which can be found at the link below.
https://youtu.be/EZUwunWWCLA
Step Up To Adjustment Layers - Digital Photo
Give your portraits a professional, polished glow in just a few minutes
How To Make Pita Bread at Home
The pitas you make at home are worlds apart from the stuff you buy in stores, and watching them puff to glorious heights in your oven or on your stovetop is culinary magic at its best. Here’s how we do it.
SVG to EMF | CloudConvert
SVG to EMF Converter - CloudConvert is a free & fast online file conversion service.
https://graphicdesign.stackexchange.com/questions/60996/illustrator-emf-export-loses-precision
Before and After Spray Paint Photos That Will Blow You Away
Looking for an easy DIY project? You won't believe these before-and-after spray paint photos!
GitHub - josephdyer/skeleventy: A skeleton boilerplate built with Eleventy.
A skeleton boilerplate built with Eleventy. Contribute to josephdyer/skeleventy development by creating an account on GitHub.
Why do they ignore my awesome design documentation? | Slava Shestopalov | Design Bridges
Why they don’t read it
I’m a bit of a perfectionist. Several years ago, I believed the best documentation should be nicely formatted, concise, well-illustrated, and written in clear language — and this is not wrong. But all these features make little sense if the documentation isn’t regularly used by those for whom it has been created.
If the team doesn’t react to anything you publish, I have bad news: this documentation (specs, reports, guidelines, etc.) might be already “dead.” Here are several typical scenarios of what may have gone wrong:
-
“Approved and forgotten” — design guidelines were created without team involvement and then approved by stakeholders. After the official presentation, someone checked them out, while others didn’t. Since the guidelines were comprehensive, they looked like a huge reading that would take a lot of time.
-
“A perfect monolog” — amazing design knowledge base inspired lots of team ideas and questions, but commenting was either absent in the tool or disabled. As a result, the discussion occurred elsewhere, in Slack or MS Teams, and soon this chat became a more valuable “source of truth” than the knowledge base itself.
-
“Lone warrior” — design system documentation was detailed and well-structured but didn’t include any links to what other team members (engineers, QAs, UX researchers, etc.) were doing. As a result, it remained just the designers’ resource, and designers had to answer the same repeated questions in the chat or team meetings.
Documentation is a digital product no less than the actual product you are designing and being paid for.
How to get started with hand-lettering | by Cat Noone | Medium
Earlier this year, I pushed out a tweet about my desire to be a beginner again, learn something new and took a particular interest in…
5 Steps You Should Take to Prevent Common Running Injuries
All the tips you need to prevent running injuries, including form tips, strength and mobility moves, and more.
FizzBuzz - Rosetta Code
Task Write a program that prints the integers from 1 to 100 (inclusive). But: for multiples of three, print Fizz (instead of the number)...