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

Question: Live Reloading & Workflow #11

Closed
frankalbenesius opened this issue Nov 13, 2014 · 3 comments
Closed

Question: Live Reloading & Workflow #11

frankalbenesius opened this issue Nov 13, 2014 · 3 comments

Comments

@frankalbenesius
Copy link

Hello! I'm really loving this project. It's making creating a Ghost theme really easy for me. I just have one question though:

What is your typical/ideal workflow for creating a theme using this tool? Currently I'm running 'grunt watch' on this inside the theme folder to compile my stylesheets while also running 'npm start' to watch for theme file changes and update the development ghost environment. This is working fine, but I have to manually refresh the page each time to see changes.

Is there a better workflow for this type of work than running two seperate watchers? Is there a way to have live-reloading available?

@ericterpstra
Copy link
Contributor

Yes, this is generally the normal workflow. I'm usually OK with refreshing the browser after making changes (with Ctrl/Cmd+R), but if you want live reload, there's nothing stopping you from adding something like BrowserSync as an additional Grunt task. Check it out here: http://www.browsersync.io/

There's a nice tutorial on Grunt + Sass + Browsersync at http://www.wearejh.com/development/frontend-automation-with-grunt-sass-browsersync/

@frankalbenesius
Copy link
Author

Great! Thanks.

Would I be adding that task to the Linen Gruntfile or the Ghost Gruntfile? Front what I understand editing the Ghost Gruntfile might not be advised. I guess it doesn't matter what is doing the actual refreshing as long as everything is getting updated simultaneously? I don't have a ton of experience writing my own grunt tasks.

@frankalbenesius
Copy link
Author

closed cause this is crazy old and not open

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

No branches or pull requests

2 participants