Title: Project Title Author: First Last Email: [email protected] Address: 1234 Street, City, State 12345 Phone: (XXX)XXX-XXXX Affiliation: www.LaCroixDesign.net Copyright: 2015 Company Name Keywords: Proposal, Web Design Date: March 13, 2015
/* | |
This document has been created with Marked.app <http://markedapp.com>, Copyright 2011 Brett Terpstra | |
Please leave this notice in place, along with any additional credits below. | |
--------------------------------------------------------------- | |
Title: LaCroix Design Co. Proposal | |
Author: James LaCroix — www.LaCroixDesign.net | |
Description: Styles for outputting proposals to PDF using Marked. | |
*/ | |
body { |
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important
or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.
Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma
I hereby claim:
- I am plainspace on github.
- I am jaredvolpe (https://keybase.io/jaredvolpe) on keybase.
- I have a public key whose fingerprint is 65A6 9B8F DBD3 A385 17A9 F3EA 5A11 ABF7 89A3 D49D
To claim this, I am signing this object:
Somebody asked me how to become a Product Manager. Here's what I wrote them. | |
--------------------------------------------------------------------------- | |
Hi Jon, | |
Those are a lot of questions. Let me try to simplify it. | |
I think a Product Manager is a person who is responsible for determining | |
what a product should be and how it should evolve. This is a design role |
I'm learning how to finger paint Leap Motion style.
A Pen by Jared Volpe on CodePen.
A Pen by Jared Volpe on CodePen.
- Personalized features. Currency, language, country specific deals, taxes, or delivery options are changed based on user's location.
- Registering provides value to users. For example a "Free Trial" button communicates a clear benefit, but a "Register" button doesn't. Unnecessary registration is avoided.
- Transparent pricing. Prices are clearly displayed. There are no hidden costs or surprises in the terms.
- Pages don't refresh automatically. Users can get confused if new content is uploaded suddenly, for example on news websites.
- Sample content. For example there is a sample newsletter next to a newsletter sign up form.