Weekly Update 115: Spotlight on CSS
This is a copy of our weekly newsletter for developers which you can subscribe to here.
Over the next few weeks, I'd like to share some of the progress we've been making on the programming mission, including new and improved Instant Answers and the impact they're having. This week, let's turn the spotlight on CSS.
It's exactly two months since Zaahir (@moollaza) did some initial analysis and discovered that 18% of CSS-related queries show an Instant Answer. The ultimate goal is for 100% coverage, meaning that any CSS search will show an Instant Answer and developers can get the information they need in the shortest possible time.
So how are we doing? Thanks to great community efforts, we now have 35% coverage for CSS! This is the result of both new Instant Answers and improvements to existing ones. Try some of them out:
Pretty cool, huh? Particular thanks go to hchienjo, ManrajGrover, rasikapohankar, sahildua2305, samskeller and VeerpalBrar for their great work. Of course, there's still a lot of room for improvement so if you'd like to help us help CSS developers, check out the todo list in the CSS Overview forum post.
And here are some specific issues we're currently looking for help with...
- Color Codes: Reduce the over-triggering
This triggers on any query ending in "color [name]"
- Find CSS coverage opportunities
We have a list of unanswered queries. We'd like help looking through their results and proposing new Instant Answers or updates to existing ones (see the "To Do" section in the linked post).
- CSS Colors: Lacking "rebeccapurple"
This was added to the CSS spec a couple of years ago as a tribute to Eric Meyer's daughter.
- Microsoft PowerShell Cheat Sheet: Fix typo
A nice easy one — "CaseSentitive" should be "CaseSensitive"
IAs for Adoption
The following Instant Answers are looking for a maintainer — someone to moderate suggested changes from the community as well as address any issues that pop up in the future. If you'd like to step forward, please create an issue on GitHub using the button at the bottom of each IA page.
We all love keyboard shortcuts, right? And we all use the command line, right? So what better than telling you all the keyboard shortcuts available for the command line!
This is super easy — just type this command:
You'll then see a long list of all the keyboard shortcuts set up for your terminal. It may look confusing at first but
\C means the Control key and
\e means the escape key. Shortcuts with a hyphen mean you should hold down the keys simultaneously, and with no hyphen it means press the keys consecutively.
A simple tip, but you may find a shortcut that could save you lots of time. Note that this may not work on Windows unless you use something like MinGW/msys.
And with that, enjoy your weekend!
- The DuckDuckGo Staff