-
Notifications
You must be signed in to change notification settings - Fork 67
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
Displaying theme object inside of PL files #103
Comments
@bradfrost It's not a dumb question at all. Take a look at the commit above on the Anyway, I committed it with obviously poor UX of actually displaying the theme content. Make changes as you see fit, run Feel free to continue working off of this branch if you like. Aside I also see that you are starting work inside |
@bmuenzenmeyer Thanks a ton for this! This all makes sense to me.
Forgive me, I still feel like I'm all thumbs with this process. Can I just work in |
You betcha. |
Cool, thanks @bmuenzenmeyer. I've committed changes here: 1b9b4a0 Any way you could give a quick glance and a thumbs up just to see if I'm not screwing things up? With so many branches and stuff swirling around, I'm still struggling to get my head around where I should be doing work. Sorry for being dumb! |
Awesome thanks! |
Alright, I may have closed this too soon. Next thing I need to do is to get stuff inside the iframe listening to the config. Is that possible/easy? |
as in, individual patterns? |
As in, inside the |
@bmuenzenmeyer @EvanLovely:
This is likely a Very Dumb Question from Brad, but here it goes: I see that the
theme
object is available in the browser (if I open the console and typetheme
it returns the object); how do I get the info withintheme
to display in, say,html/partials/header.html
?I know we are using Hogan to render our templates, but I'm scratching my head why adding
{{ theme.logoImage }}
isn't printing out the path to the logo.Forgive the dumbness of the question, but once I have an idea of how to work with the theme object in this repo, I can get everything wired up!
The text was updated successfully, but these errors were encountered: