Skip to content
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

Brainstorm: How best to show the benefits of TurboGraft #7

Open
qq99 opened this issue Sep 14, 2014 · 16 comments
Open

Brainstorm: How best to show the benefits of TurboGraft #7

qq99 opened this issue Sep 14, 2014 · 16 comments

Comments

@qq99
Copy link
Contributor

qq99 commented Sep 14, 2014

Our example app is a godsend for local testing, but I don't think it will have a broad appeal. We need something pretty!

Perhaps we should make a few simple pretty .html pages calling TurboGraft functions and put it up on a demo site

@qq99
Copy link
Contributor Author

qq99 commented Sep 17, 2014

Probably best is to use gh-pages branch with a main index.html and a few tiny html partials that show the various types of operations

@tylermercier
Copy link
Contributor

It would be ideal if we could just deploy the example app onto heroku and link to a Demo. Then we don't need to maintain two code bases.

@qq99
Copy link
Contributor Author

qq99 commented Oct 29, 2014

$1VPS from atlantic.net? is that cheaper than heroku?

@tylermercier
Copy link
Contributor

heroku would be free, we would only need one dyno. Figuring out the deploy for a nested rails app would be the only cost.

@qq99
Copy link
Contributor Author

qq99 commented Oct 29, 2014

Oh touché

@patrickdonovan
Copy link
Contributor

Doesn't shopify have a herkou account? I think some things like askify are hosted there. But yeah one dyno would probably fine most of the time.

@pushrax
Copy link
Contributor

pushrax commented Oct 29, 2014

Shopify's Heroku account is already too full (we keep hitting the limit). Making another would be better.

@gelkelp
Copy link
Contributor

gelkelp commented Nov 6, 2014

Is there a particular example we'd like to build, or just do a general showcase of the features? I can help out with this so that I can ramp up on the tech before I write about it on the blog.

@qq99
Copy link
Contributor Author

qq99 commented Nov 6, 2014

I was thinking we'd host the example app inside this repo since it's both documentation and example simultaneously

However, that's a good question, maybe there's another minimal app we can build that shows a little bit more how we use it effectively in a more realistic use-case

@tylermercier
Copy link
Contributor

@lkrupphunter setup the project and and run ./server to start the local app. That is what we want to host somewhere.

@gelkelp
Copy link
Contributor

gelkelp commented Nov 7, 2014

I'm going to run with fixing up examples plus some design and branding.

Should we have one main landing page for both of them (Twine + Turbograft) and then have separate examples for both, or should we keep them entirely separate from each other?

@Morganjackson
Copy link

@funionnn Are you still planning to create some examples? TurboGraft looks very interesting and I'm trying to compare it with http://intercoolerjs.org/

@gelkelp
Copy link
Contributor

gelkelp commented Mar 11, 2015

@Morganjackson I added some basic examples to the readme, is there anything else that could be helpful?

@Morganjackson
Copy link

@funionnn No nothing specifically, I was just being lazy! I'll have a play around it with it myself.

@gelkelp
Copy link
Contributor

gelkelp commented Mar 11, 2015

@Morganjackson Cool, if there's anything that's either missing or unclear, feel free to ping me!

@Morganjackson
Copy link

@funionnn cheers, will do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants