Actually, take some weekends for HTML and CSS basics, but do not bother for too long as it is not really necessary for your situation. Just need to know what classes affect what :D and then start to learn JS fundamentals like following some links of this collection: http://jstherightway.org/

or this of the all new and very good "looking" page ( I did not complete it yet ): https://www.javascript.com/resources

and then you can look into this user-curated list of framer-relevant resources: https://docs.google.com/document/d/1ddjYyM6JVWzHW2ngU-0R1UhzzXNgHcklXRCDYHfQGGY/edit

Though, this is just my adviced order of things. You could also simply opt to go directly into the resource list and start with coffee script for beginners and framer and stuff. ^{^}

As an early member in the fb group, I guess it simply is the combination of the industry participants, e.g. designers and front-end designers and the open context of a fb group.

There is no magic juice in gathering the right people in an personal environment that is facebook.

I have a simple question: Do you consider remote working roles or are there already existing positions open for this matter?

Oh, I can't hold back and must answer that.

I am an interface designer and front-end developer with recent full-stack experience, that turned to something someone might call UX engineer. Thus I know exactly what those devs are about in #1

I am no fan of coffee either and I recurringly also point out that I do not like designers to learne coffee without knowing any basics or foundation work of what JS is about and how to code properly in the facebook group. Coffee script touts itself of being a simplified version of JS, but in fact it does quite the opposite in my terms. It takes out the logical segmentation the JS syntax provides you in favor of "less letters in your view". This is also evident in the facebook group, where maybe 3 out of 5 questions are simple debugging questions of designers who have no clue about code and make basic mistakes over and over again.

If you want to learn to code, then learn to code. Using framer and coffee will not make you to learn how to code, it simply will allow you to copy&paste some basic patterns out of your mind without understanding the structure behind it.

That's why developers shuckle if someone wants to start with coffee... which is frankly not learning how to code.

Though, if you are in an environment that requires rapid prototyping, now, than framer is not your choice and you should opt for a different tool. If you really want to learn to code, you should do that and learn HTML and CSS and then JS with real JS books and NO "LEARN to make App X in 30 days" courses, because there you don't learn how to write code, you simply learn how to copy methods that end up being an App.

Learning to code IS NOT EASY and nothing you can do and accomplish fast. HTML and CSS, is easy done, but including logic with JS is not easy in contrary to today's media message of "learn to code fast" and such. It takes at least a year to come up with basic logic that is not totally broken and unoptimized.

And that is also the reason why your #2 exists. Of course, you can't understand what is written there, it is an API docu for using JS logic. It must be really hard, it is even hard for me to get some connections from time to time...

To #3: This actually is all included in framer as it uses js and thus you can inject CSS at will.

Pixate had a very unique approach between node- and code-based prototyping. Though, the recently added Actions module is not comparable to what framer does or generally is.

To explain that a little better, framer has "no" fixed set of what you called "all that framer is capable of", because framer basically is a JS framework and thus can do everything you can accomplish with JS. (Framer Studio is a specialised editor for framer).

However, the community already has set a gallery page, where already existing modules are available to use for other designers, opening the framework to designers who don't want to code nor can.

A UI for say sliding and rotation and something... don't know, actually does not fit the spirit and approach of framer.

Framer.js actually is code. It's not comparable to Quartz or other visual tools, it's coffeescript or js code, which is why an animation from framer is easy to translate into code, but it takes way more time than Quartz or comparable.

Keynote, Flinto, Invision: - Made to rapidly create a user-flow, to show interaction paths and give an overall feeling

QC, Framerjs: - Made to create intricate animations, which details/numbers can easily be translated into the Apps source code

QC vs Framerjs: QC basically reminds me of those camera animation and scripting panels from 3D SW. It's simple and just needs some time to fiddle around with the boxes and numbers to learn, yet it will always be faster than writing pure code.

But, as many already mentioned, in the end it depends on your liking. With some practice in framerjs, you may come up with the same output, but it'll take more time.

Latter is always the most persuasive argument for me as well.

Having learned multiple languages, at some point you realize, the fastest way to learn best-practice models and common methods of doing x is simply learning from code, from stuff others have done.

This necessarily requires a huge community just as jQuery.

However, I disagree with AngularJS being more flexible, but Angular just offers so many resources to have an answer ready for every question you may come up with.