-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"New Stack" |> Elixir, Phoenix, Elm & Tachyons? #37
Comments
Not sure if you want to take advantage of it, but you can call this stack 'PETE'. (Phoenix, Elixir, Tachyons, Elm). It sounds pretty catchy. Might even be worth it to dedicate a new repo describing the PETE stack and why/how to use it, maybe even with some installation scripts/guides to start with the barebones Pete stack. Perhaps even something like http://mean.io/ for this stack. (pete.io)? |
@nelsonic do dwly have any projects that have tried out this (awesome) new stack |
…ir, Erlang & Elm #NewStack dwyl/technology-stack#37
Ok, it's dawned on me that having our "Tech Stack" doc saying one thing and using "New Stack" in projects is sending mixed messages ... so I'm prioritising communicating this better for today! 👍 |
https://github.com/search?q=oops&type=Commits We all make "mistakes" ... |
@jruts I really like the succinctness of "PETE" as a name ...
also we are using:
and optionally:
|
What about "TEPPE" (which is sadly not a gender-neutral person's name which would be amaze!) |
I kinda like it... Especially with the Magic Carpet reference. |
Swap out Tachyons for https://github.com/mdgriffith/style-elements |
@pdavidow we've added Style Elements to our "to learn" list: dwyl/learn-elm#96 Our reasoning for using Tachyons is that several of our apps are still Server-Side Rendered. |
The New Stack for 2017 is:
see: #27
The text was updated successfully, but these errors were encountered: