Not sure why publishing online necessitates getting to the point. It's long form and follows a very common story telling format. The world has room for different ways to tell a story.
I'm not sure that trying to keep everything in one file is necessarily a great argument. Optimizing for not having to open files doesn't seem like the best thing to optimize for. Even many of the react+inline styles examples include putting variables and other patterns into external files. Language (i18n) strings could be another external dependency. Data model, controllers, and routing are other good examples. (Rarely (if ever) have I seen an MVC framework that doesn't separate things into separate files.)
While you can't modify pseudo elements or pseudo classes, you can replicate them using actual elements and conditional logic. I've seen React examples that do just that.
I wrote a book a couple years ago called Scalable and Modular Architecture for CSS. I self-published in PDF, epub, and mobi formats. I also had the book on Amazon for awhile through the Kindle program and also have it available through pragprog.
I went ebook to start and then added a print version which I print up with a local printer in batches of approximately 500 at a time. I've since had the book translated into French and Japanese.
I've generated approximately $60k in revenue this year alone, not including revenue from Amazon or Pragprog, which were both relatively minimal in comparison.
Specific to your abandoned carts comment, the view is filterable. Type in "Canada", for example, and it'll show all abandoned carts in Canada. We'd love to learn more about what you're looking to accomplish that is difficult to do right now.
We had looked into other names and POS/point-of-sale was the most recognizable and familiar with storeowners. Yes, the acronym is a little unfortunate. :)
Animating transform doesn't affect page scroll, which is a more useful use case (since users need to scroll a page) than being able to use a translate transformation.
Of note, a translate transformation still isn't perfect. It seems to chug and then turn into a smooth animation.
When I first bought my 11" Air, I went with the base model, too. Mostly because I was impatient. But 128GB filled up fast, even with a 1TB external drive. Photos on another drive is one thing but if you have a sizeable music or movie collection, putting it on an external drive is a huge hassle. And then you're travelling with the computer and drive.
Thankfully, I bought the Air the year where you could still upgrade the drive. I bought a 500GB drive to replace the 128 and have been very happy since.
Reminds me a bit of The Superest. In the case of The Superest, two artists take turns creating super heroes/villians that could defeat the previous character. http://thesuperest.com/
If the goal is to spread it as much as possible, it should be free and uploaded to any and every service. The goal is actually to find the optimal balance between distribution and profit. Like madrobby, I've found non-specialized 3rd-party channels aren't very effective and bring in little profit. (Specialized markets like pragprog are better.)
In addition to what everybody else said, there's also trying to find pirated material for niche markets. That is, it's hard to find. I sell an e-book as well, and have foregone any DRM.
More to your point, could people buy the book and give it to their friends for free? Absolutely. And I'm sure some people have. Again, I'm okay with this. I'd rather people bought the book but like print, I can't stop people from sharing and ultimately, I don't want to.
I wouldn't bother. For me, the revenue isn't worth it. Even under $10, not all sales get 70%. Some still only get 35%. Pragprog was definitely more worthwhile. Sales were more substantial and the folks at pragprog are fantastic. Very professional and easy to work with.
It's not even a matter of developing it on non-office hours using non-office equipment. Clauses are usually more broad to stop someone from creating a competing product, even when not on company time. Having built an app designed specifically for company systems, the company would likely have a legal claim against the invention, even if it were developed outside of office hours.
I admittedly have used these services to procure obscure tracks that aren't available via iTunes or other means. That band who did an a cappella cover? No download link on their site or anywhere else? Youtube to mp3.
I think there's a difference between "the customer is always right" and "the customer gets everything that they want."
For example, a customer calls and says, "You overcharged me!" You look at the account and see that, no, the customer wasn't overcharged. The customer is right in the sense that they have through some influence of factors thought that they were overcharged. Was copy misleading? Was something not clear on one page or another?
There are a couple ways to handle this. One is where the customer is wrong: "no sir, you were not overcharged." and then argue with them until they hang up in frustration. Or you can get to the root of the misunderstanding (unclear fees? they forgot about taxes?) and then possibly choose to offer a refund as a thanks to them for helping you prevent other customers from becoming equally unhappy.
The problem I have with most editors is that they try to be like a piece of desktop software. "Install me and get all of these features including themes and plugins." That's not what I want. I want an API. I want a consistent cross-browser approach to wysiwyg html editing that doesn't weigh in at 200+k minified.
What does Aloha come in at? (Web Inspector is telling me 1.6MB!)
I haven't used Aloha but my impression is that it's trying to be like all the other editors like TinyMCE or CKEditor.
wysihtml5 is lightweight, which is nice. It provides a command API so that I can wire up commands to my own toolbar and provides state management. But I don't like that some built-in commands don't offer up enough externalization, like autolinking. Or that I can't cancel an event like beforecommand. beforecommand doesn't even tell me what command is being fired. (or if it does, I couldn't find out how.)