I am pretty excited for this release. I worked a bit with ZURB Foundation for Email 1 (Ink) and you still had to deal with this terrible table structure that reminds me of 1990's HTML. I think there are some really good ideas here, most importantly an abstraction that allows you to quickly develop branded and responsive HTML emails using some simple html structure that masks a lot of having to deal with those tables, TDs, etc.
Awesome job on the ZURB Foundation 6 launch. Great graphics, sci-fi theme, some awesome new features for the framework. The flexbox grid, yeti launch and the new menu component are worth looking at.
There are services such as snipcart and foxycart that you can trigger via html and javascript. Like most non-locally hosted ecommerce solutions they send you to a subdomain for the final checkout. I have tested both on a static site and both work very well. Snipcart is easier to implement but lacks customization. If you are looking for heavy customization (like custom products beyond just sizes, colors and options) without having to build out your own system, check out foxycart.
Very interesting project and direction for Foundation. Now uses angular directives instead of jQuery "PlugIns" has YAML defined routes and animation through ui-router, flexbox based grid. If you have been using Foundation for a while and are interested or using Angular you should definitely take a look at this project.
The angular-bootstrap and angular-foundation projects have existed for quite some time. Is there some sort of ember equivalent?
In these projects they are rewriting much of the javascript / jquery components as angular directives. The CSS/Sass/Less is unchanged. I assume much of the same could be done in an ember based project.
I think this is a pretty interesting article about doing a revised product, 2nd product launch. From what I gather, it is quite similar to a 2nd or subsequent edition of a non-fiction book. I can't remember where I read it, but someone said that you can often make more money off of a 2nd edition, and often it takes a lot less work than the 1st edition as you are just revising the content.
I'm curious as to why Zepto support was removed. Zurb was pretty big on it for Foundation 3. Smaller size than jQuery, faster load time on mobile, etc. Any ideas why this was scratched?
This is a great article and you can read countless examples the importance of sales and marketing for tech focused startups or small web based businesses. I agree 100% with most of what is being said. Also very cool to create a bootcamp focused on the other end of the business.
The irony of the title, Don't Learn to Code is realized in CTA of tradecrafted.com. Under Business & Social, point 3 is "Basic Programming"
Maybe this should be renamed to: Don't Learn to Code, [much, yet, etc.]
I just point this out because there are varying degrees of what people mean by learning to code. I don't believe that learning to code is bad for anyone, just as I don't believe that math, reading, writing, literature and the arts are either.
Are there any self directed guides to traction or learning this stuff outside of attending a bootcamp?
I am super excited about this. I love the fun visuals, extensive documentation, transparency and honesty about issues with email clients. I think there is huge potential here and I can't wait to see where they go with it. A huge use case that no one is talking about is transactional emails from your web or mobile app. Now you can have great looking emails that increase engagement that look great on mobile email and look (both in design and the underlying code) much like foundation based rails apps.
I agree about both points. I guess I was in the position where I use my own computer or one I can change to dvorak about 99% of the time. The keyboard shortcuts are not great though. Especially for things that are meant for left hand keyboard and right hand mouse simultaneous movement, like in photoshop or most games. I usually just switch to qwerty in a pinch.
vim, is also especially awkward in its movement commands. ST IMO doesn't have this same level of awkwardness.
There are other variants for other languages. There is Bépo for French.
The Dvorak layout is ideally suited to typing in english where you have a constant switching of vowels to constants. All the vowels are on the left hand so the idea is that you alternate and it is unlikely that you will type much more than 2 or 3 in succession and often only 1.
Author here, would really like to get some feedback about how I can make this better for the zurb foundation / ruby community. If you have any resources about creating Rake build scripts for static site resources (outside of Asset Pipeline / Sprockets) I would love to hear about them.
At first I thought this article was how to use processing and racket together (headline) but it seems that it advocates for the use of racket and possibly for it to have richer documentation.
I have been using processing for many years and there are many different ways people get into the language: 1) through artists and their works, think Casey Reas, Aaron Koblin and the tutorials by Daniel Shiffman. 2) through specific use cases like, I want to hook up my kinect and do x. 3) it is taught in may experimental arts and datavis classes / tutorials. and 4) lore, I have heard from many people "processing seems like a good fit for x" 5) an so on.
I think where processing excels or has exceled in the past is being able to quickly pick up more experimental bits of code and libraries in Java / C++ and put a simpler syntax in front of them. People often say, processing is really just java. And to be specfic, it is just a preprocessor and an api/library (core.jar) for Java. The processing IDE is okay for beginners but most people that get serious with it move to an external text editor or IDE like Eclipse.
In my opinion it is not the simplified Java syntax that makes it great to work with it is the philosophy that drives the api. It is very easy to start drawing shapes in just one line of code. They create duplicate methods so you can pass in ints, floats or another datatype without resorting to casting.
There are also a bunch of offshoots, processing.js, ruby processing, etc. which are pretty exciting. Often the way the api is ported is not the best fit for the new host language. I have played with a bunch of these and they are fun but they seem to not get the kind of traction the main processing project does.
I think if you are wanting to advocate racket more effectively you should look at the historical linage of processing (design by numbers, data visualization by ben fry, etc.) and you will see why so many of the learning/documentation focuses on things that interest designers and artists. If you want to do the same for Racket, get some artists to do some awesome work. Then have them document it, break it apart and share it. I think this is how such a large community has sprung up around processing and why so many projects continue to use it today.
The other project that works really well with processing/js is toxiclibs/js. You should consider porting it if you want to draw in some of the newer crowd.
I know this has been done in Sacramento for years. Yellow Lights at large higher speed (40mph) intersections (like Fair Oaks and Howe) have the yellow light set at the CalTrans minimum safe approach speed, which is often 25 mph. This is on a double lane left turn with traffic at or above the posted speed limit.
Good luck fighting that ticket, well within the California State law.
Too bad they don't have to set the yellow light timing consistantly. That probally wouldn't give you the 2x increase in citations.
I think the work done here is fansastic and presents a great alternative to the zurb joyride / jquery or zepto combination. I agree with some of the other comments about the usability on an ipad and mobile device as well as scrolling the screen to the focused element. I think larger targets would really help with this.
At this point in its development, if you are able to use jQuery or Zepto I think that Joyride 2 offers a much better UI / UX especially if you are planning to use Foundation 3/4.