Be nice. Or else.
building Voyager Joined about 4 years ago via an invitation from Allan G. Taurean has invited alec s, Nicole Francesca Pagliaro, Eric Boyer, Dominik Martin, Josh Green and 5 others, Liang Shi, Bjoern Zinssmeister, Day Jimenez, Timothy L., James Bruno
This is really good when you want to create a class that overrides most specificity. I use it to apply a blanket screen-reader-only class.
CSS still treats this as having an ID even though you're technically saying it doesn't have an ID, so it will override any class declaration regardless of its placement in your CSS document. The only thing that could override it would be another ID or an inline style.
I know it's petty but I can't seem to read this as anything other than "En Oh" = "NO".
This is really great to see. ★★★★★
I don't know, I think some Kickstarter projects do a good job of using design and crowdfunding to make previously unaccessible things accessible. The Misen Knife is a good example. My problem with this is the baked in elitism and self-congratulation that comes with selling something like this. It feels so out of touch.
In the (hopefully unlikely) event of the Kickstarter not meeting its goal, will you still pursue building this app through some other means? Subform hits almost every single pain point I have.
This is so unnecessary. So much effort and rhetoric to take a product that sells for $3 and make one slightly nicer for $20.
Maybe this is obvious to others but it'd be awesome to hear some insight in how you'd use this in your workflow with Sketch. (Even a similar gif to the one you have for illustrator would be super helpful)
Pro tip: you can save this as a template in sketch. Once Greyprint is open, just go to
file > save as template…. After that, you can always start with Greyprint as a foundation via
File > New From Template > Greyprint.
Really where I see this shining is when multiple designers are working in various parts of a larger project. Eg. I may be working on a checkout process while someone else is designing an on boarding flow, two things that are entirely separate but dependent on the same base components. Versioning and managing conflicts has been really my only issue when using Sketch.
Historically I've always done everything from the ground up but recently I started working on my own framework/set of tools based on the types of things I find myself rewriting the most often. Its mostly stuff in SCSS (mixins/functions/variables) so it doesn't add that much bloat to the project.