Be nice. Or else.
Miami Founder @ www.creativelist.io, Previously @Pinterest, @YouTube, @Google, @Yahoo! Joined about 1 month ago
For anyone who was doing web development before 2010, this website was a source of inspiration and a place where anyone could find and learn new techniques on how to bend technology to accomplish specific design goals. It's pretty cool to see the site up and running again.
@Marcel: Thanks! Totally agree on the search bar. It definitely feels more blended in the content than in the previous version. I'll continue to tweak it until this looks better. Airbnb has a similar background pattern, but their shadows / colors are darker and their design is a bit more flat. Will have to investigate on that one. Thanks again!
For payment reminders, you can use Stripe. You will have to create a subscription with a plan (at $0).
When the subscription is about to renew (basically when you want to send a payment reminder), stripe will send a webhook (I believe it will be invoice.created). At this time, you can send the email to your customer. When the customer has paid the bill, just cancel the subscription.
You could also get similar results by setting an automated trigger on Customer.io by setting an attribute on your customer (e.g. "invoice_sent"). Other systems like Intercom support this as well. I believe all those emails, to comply with CAN-SPAM Act, are required to provide an unsubscribe at the bottom.
Julie Zhuo is a Product Design VP @ Facebook. Every week she answer a reader's question on The Looking Glass. She will also be talking at the O'Reilly Design Conference in San Francisco.
As the name states: adding a pre-processor means you will add latency into your workflow.
At first it takes milliseconds, but as your application grows, it can take seconds then minutes to complete. Every time you will want to preview a change, the system you are using will have to pre-process the code into something the browser can understand.
Before using a pre-processor, the best is always to assess the issues you are facing. For instance with "classic" CSS:
By assessing the issues you are facing, you will be able to see whether or not to use a specific pre-processor. Now to answer to your question, I use Sass as a CSS preprocessor because the benefits outweigh (syntax is closed to CSS, modularization, shared variables, namespacing, vendor properties, functions). There are others (stylus, less) which provide similar features.
Note: I don't use a HTML pre-processor.
Just listened to the podcast. Loved it!
(disclosure: I was the tech lead working on the YouTube redesign in 2011 and 2012)
YouTube, like any web properties, are often subject to change, and those changes are carefully reviewed, measured, and assessed before a full roll out. It means that if you see some changes, those might never become part of the product - it's just a trial to see how consumers will react and the evolution of their internal metrics.
Minimalist UI, the content is organized in a fung shui fashion - with each part carefully placed. Really love it.
Couple months ago, I launched a platform named CreativeList (www.creativelist.io). It aims to do exactly what you've been asking as it's a search engine specialized for creative professionals (includes designers, and many others). It facilitates how clients find creative talent.
It's short, but I finally wrote an introduction on Medium: https://medium.com/creativelist/introducing-creativelist-7bcf00fbe337#.9lwojas67 to explain this a bit more.