A lot of these standalone products have been integrated as features into Google's core product offerings.

Hi Dav, Thanks for sharing 500px. This type of site is exactly what I'm looking for. Why do you say 'until recently'? Anything I should know about when using that site?

I don't think bots are ready to completely replace human agents. I work for enterprise and we've implemented chat bots to complement human agents. The bots take care of the initial intake process, and then pass the user off to a real customer service agent. The bot process is completely transparent, you don't need to pretend its human.

There are several types and levels of design docs. Important questions to know: 1. Who is the intended audience (designers, front-end developers, 3rd party users) 2. What is the purpose of the documentation (to create consistent design implementation across a product, to document how to use CSS, to document how to use and extend UI components) 3. what is the size of the development team?

I agree with you. my response is in context to "don't touch angular,react, or vue js until you learn object oriented programming principles".

designers will get a lot more mileage learning functional concepts first. you need to understand higher order functions, callbacks, pure functions, and closures in order to grasp angular or react. it's what these entire frameworks are built on. never used vue so cant speak about that subject.

you need to learn functional programming, not object oriented programming for javascript.

Do css file sizes REALLY matter in 2017? I'm sure you can be a stats enthusiast and keep bringing that number down. But with high speed internet, a simple minification & gzip process seems to make most file sizes trivial.

For instance, our site's css is over 18,000 lines of mostly non-reusable BEM components. There is very little abstraction of css classes.

post-processed, the css is 50kb. This loads in ~400ms on first load. When its cached, that's 10 ms.

there's no noticeable REAL performance difference in a 20-30% reduction on 400ms load time.

I've looked into atomic CSS before. I still can't wrap my head around a few things.

1) Responsive design. How do you deal with containers that have custom sizes based on screen size? For instance, a div that has flex-basis: 30% for desktop, 50% for tablet, and 100% for mobile?

2) States such as hover. But also, cascading states. Imagine a button inside a div.

CSS: .button { display: none; }

div:hover button { display: initial; }

Both seem pretty crucial in developing rich web apps, no?