-
Notifications
You must be signed in to change notification settings - Fork 17
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
aside #27
aside #27
Conversation
Solution #1: Hack up hobo_bootstrap and the aside definition
This works, but it's damn ugly, and breaks pseudo-parameters like after-content. (which is used in one of our integration tests). |
Solution #2: modify the hobo generators to use the content-body & aside parameters instead, and require all themes to define them. I'm leaning towards this solution ATM. Thoughts? |
+1 from me. |
I like solution 2 too :). |
The code looks good, but I'm unsure whether you have finished your work. Should I test and merge this pull request? |
Please test it. I'm going to add a version bump to both pull requests so because old hobo_bootstrap won't work with new hobo and vice versa. Then we just have to make sure that we merge the pull requests into both hobo & hobo_bootstrap simultaneously. |
I tested both branches (hobo_bootstrap#aside and hobo#issue_11) and they work very nicely :). Please merge when you want and I'll push the gem. By the way, I took a screenshot of the aside and found a bug in the process: #30 |
Merged. Don't push the gem yet. People using hobo from github should be Bryan On Mon, Nov 12, 2012 at 2:07 PM, Ignacio Huerta [email protected]:
|
Ok :) |
hobo_clean defines content like this:
hobo_bootstrap defines it like this:
the hobo generators use the above like this:
Notice that the generated code does not use the aside param from hobo_bootstrap. So the aside ends up being a section at the bottom of the page.