Partyfists

It's just odd for an MVC framework to not have a 'C'. Generally, your view would just generate HTML, the controller listens for events and responds to them by updating the view and model. Here, your view is taking over that responsibility.

For how small the library is, this is pretty fantastic though. Significantly smaller than Backbone for similar syntax.

This is really interesting. I guess the part that confuses me is using the "View" to do traditional controller-esque things. At least in the example, that is how it looked. Would you be able to explain that choice?

There are a few things in play here that you may not be considering. First this minimum wage increase would probably happen over 5 years like San Francisco and Seattle are doing. So businesses would have time to prepare and it would not go from $9 -> $15. Second, these companies have many costs outside of labor. If labor were to double for just employees making less than $15/hr, the price of everything would not just double. It would have to go up, of course, but it would not double. The final thing to consider is that if every one in the USA is making more money, they will also have more money to spend. This means they are more likely to spend money at these types of businesses thus increasing daily sales for the company.

The argument you are making is an extremely common argument from before the minimum wage was instituted decades ago where minimum wage was also (relatively, of course) significantly higher than it is right now. It turns out that people do like to spend money and when they have more of it, they spend more of it.

Also, you can append a last modified query parameter to automagically clear the cache for static assets.

Of course, feel free to reach out with any questions you have. I'm on twitter @partyfists let me know!

Best of luck to you guys.

We use JIRA at my office, and I really do not like it for project management. JIRA gets too big and unmanageable way too quickly.

I have not, however, tried JIRA agile, which might be better.

For straight user stories, I love Sprint.ly. However, its feature set is just that: User Stories. It works extremely well, makes sense and is a pleasure to read.

For me the things I can do to stay motivated are like this:

1. Work with people you really enjoy being around. 2. Do something you love doing 3. Find a type of music which is not distracting. Preferably, no lyrics or loud noises. 4. Find what is making you procrastinate (video games for me) and moderate it. 5. Be goal oriented. Be more agile and celebrate the small victories.

I hope that helps!

To answer your first question, yes that is exactly where you should put your super-specific styles. You want to put your communal styles in your placeholder, styles that all types have but are different in the mixin (background color, etc) and the rest on the class itself.

The best way to get better at Sass is to follow people who are active in the community (which unfortunately is not me). Start with Chris Coyier and Hampton Catlin and work your way from there.

If you don't mind me plugging my own talks, I have a few that are really good at learning Sass:

https://speakerdeck.com/liamdanger/why-your-sass-is-bad-and-...

https://speakerdeck.com/liamdanger/what-if-css-was-object-or...

https://speakerdeck.com/benbayard/how-to-raise-a-code-puppy

Hey Id,

I'd say learn how CSS works first and really understand what it's doing. However, Sass can help you write very maintainable efficient styled code.

I will always recommend using Sass, but only if you know what CSS you're making and know that it matters what CSS is being output.

Of course! The idea behind using preprocessors is helping you write CSS more easily. The goal is not to write obfuscated CSS, but rather to write CSS well! What it really enables (imo) is to think of styling in an Object Oriented way. Whenever you're about to write a block of Sass think "What is this thing?". The answer is almost never a "green button" but rather "getting started button". Or something like that. It also helps you to think in terms of inheritance:

The "getting started button" and "buy button" are both interaction buttons. (Similar buttons, but one is green and the other is yellow).

In Sass you represent that this way: 1. Placeholder %interaction-button class where you outline the fact that it has a border radius, color, and any other shared styling. 2. A button maker mixin where you put the colors that need to be changed, and any other flags (like has_sub_text: true for the unbold text) and then @extend's the placeholder above. 3. The classes ".buy-button {}" which include the mixin you made.

Hey! I just want to say, this is awesome and I wish you the best of luck.

I am a Developer and I noticed a few really concerning things in your CSS:

1. I believe you're committing the greatest CSS Sin: Emulating the DOM structure using nesting. Here is one example: "#site-header.newheader nav>ul>li>a.buttonGreen"

That CSS Selector should not exist like that. You shouldn't be using ids (first) and second this should be be: .buttonGreen {}

It looks like bad Sass or LESS is being used and nesting is being abused. If you'd like more advice on how to fix this I have written many talks.

The reason these selectors are a problem is because of the extremely long paint time. Right now your site takes around 30ms to paint. It should be closer to 10ms.

2. The CSS classes used are meaningless. Above there's a "buttonGreen" class. However, what if you redesign and that button is now blue? Do you just edit the CSS (like should have to be done) Or do you change your HTML and CSS to reflect a basic styling change? This only hurts you and maintaining your site.

3. You're loading 2.4 MB of data on your home page. 1 MB of that is images, which is fine, but that means you have 1.3 MB of data loading. The good news is that on mobile almost 100% of what you are loading are images, however, that number is still 2 megabytes. I'd see if there is a way to lower that number.

4. It is extremely busy. I was really confused when I got to the site. I am not a good designer so I cannot give specific advice, but I'd think "calming" the site would help a lot.

5. On Chrome Mobile I cannot click the hamburger button. It does nothing.

6. You need to simplify your creation flow. You have 4 pages right now, it should only be 1.

7. Your select boxes need a dropdown arrow.

8. USE NATIVE SELECTS and restyle them using CSS. Use a fallback for IE and IE only!

9. Mobile functionality is not the same as desktop functionality, this is a big one that needs to be fixed. You should be able to do the EXACT same things on mobile that you can on desktop.

10. The goal of the site should not be browsing, I don't think. I think it should be about: Creating lists and sharing lists. Browsing should certainly be an option, but make creation and sharing more prominent than browsing.

You can click the button and it's John McCain saying "Hell No" from his Party of Hell No speech. There was a bit on the Daily Show about it and I thought making it in to a button would be funny.

It is not a technical masterpiece, and it was built in about an hour. But I am proud of it.

This was inspired by an episode of the daily show. It consists of an incredibly basic Go fileserver, HTML5 and CSS3. Nothing advanced or cool, but I like.

It looks like this scrapes, as opposed go being real time.

Someone above posted a link to http://m.news.ycombinator.com.moovapp.com

I think after being improved a little bit it could do exactly what you're looking for.