Possible code to implement as features

[bnb]

If it's okay, I'd like to assemble some scripts/styles/snippets, most will likely be found on GitHub, that we could maybe implement in Oatmail. I'll update this as I come up with more. Note that these are only possible suggestions--just brainstorming here.

For email client:

• Elastisearch - Node.js searching: https://github.com/elasticsearch/elasticsearch-js
• Headroom - For detachable header: https://github.com/WickyNilliams/headroom.js
• Knwl.js - to pull possibly important information out of emails: https://github.com/loadfive/Knwl.js
• favicon.js - for updating favicon with a number when new emails come in: https://github.com/Dlom/favicon.js
• GenieJS - for commands in-app: https://github.com/kentcdodds/genie
• sticky-kit - possible alternative for Headroom (I've been having trouble with Headroom): https://github.com/leafo/sticky-kit
• zoomerang - enlarging images in emails?: https://github.com/yyx990803/zoomerang
• resumable.js - for providing multiple simultaneous, stable, fault-tolerant and resumable/restartable uploads via the HTML5 File API:https://github.com/23/resumable.js
• humane.js - for sent notifications (if necessary): https://github.com/wavded/humane-js
• uniform.js - custom, consistent inputs: https://github.com/pixelmatrix/uniform

For Homepage et. al:

• Skrollr: http://prinzhorn.github.io/skrollr/

General:

• Myth - CSS postprocessor: https://github.com/segmentio/myth

Themes:

• If you want to use bootstrap, any of these are good (with modification, of course):
• * http://bootswatch.com/journal/
• * http://bootswatch.com/simplex/
• * http://bootswatch.com/slate/
• * http://bootswatch.com/united/
• Topcoat - CSS styles to apply to the site: http://topcoat.io/topcoat/topcoat-desktop-light.html

Edit 1: Just re-found Semantic UI, and I have to say I'm really, really loving it. I think it would be the best choice for us for the theming. http://semantic-ui.com/

[pauljohncleary]

Thanks, some of these are great, let's keep this as a working list of resources to pull from.

Big question for now- is which front end MVC JS framework to use? I'm leaning towards AngularJS because it seems to be the most popular.

see here: http://todomvc.com/

[bnb]

For the MVC framework, I wouldn't really care between Angular, Backbone, and Ember, as I think they're on pretty equal footing in several respects, but Angular is definitely the most popular, which would/could probably/possibly increase adoption. Are there any upsides feature-wise to Angular that you like? You probably already know this, but I think it is probably more important to choose the MVC framework that is correct feature-wise rather than popularity-wise. If there is one that provides specific features that would be useful to the project that the others don't have, choose that one.

[bnb]

Added Edit 1 about Semantic UI. I really, really like it. http://semantic-ui.com/

[pauljohncleary]

Ok, let's go with Angular, there's no functional reason, I can't see any unique features that make it a better choice. Just popularity. Expect some updates in the next week or so.

Looks like there's a call to be made between semantic ui, bootstrap or foundation (or some other css framework)

IMO Semantic looks nicer and is more original on the surface. However, Bootstrap has more documentation, examples etc.

But semantic looks fantastic, so I say we go with that?

[bnb]

I agree with you on Semantic, I definitely think we should go with it I wouldn't even really consider Foundation. Bootstrap I would only choose because of popularity, but it is so overused that I'm seeing many, many designers shun sites that use it, going as far as not using them all-together purely because they haven't modified Bootstrap (or a theme) enough. At the stage we're in, I would say it would be hard for us to make Bootstrap completely unique, and doing so removes part of the reason to use a framework.

Again, I definitely think we should go with Semantic.

[bnb]

Two more things. First, I noticed a feature on the Semantic site that is actually super cool, and we might be able to work in as a unique feature. Basically, they have two links in the top navbar--one called "Designer" and one called "Developer". I think it starts out in the Designer view, where everything is explained and demonstrated, with expandable code blocks to see implementation. The Developer view, however, only has code blocks, which are already expanded, with no examples or explanations. I figure we could implement something similar in either the email display page, the email authoring page, or the inbox view page. Thoughts?

Also, I posed the question of what features a perfect webmail app would have to Designer News (question here), and there were a couple of interesting ideas for unique features that we could implement. Thoughts?