| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
- Put banners in center of container
- Set minimum size of page and elements to make room for banners
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Ideally I would like to have the sidebars expand to show all their
contents, but I have not found a way to make this look nice. They should
also expand their container, so that the footer comes below the
sidebars. For now this seems like an acceptable solution.
|
| | |
|
| |
|
|
|
| |
- Module headings now go all the way out.
- Side body content is included like a module only if not empty.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also fixes DOM id of sidebar modules with spaces in their title.
|
| |
|
|
| |
Also strip out modules with empty bodies.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was some problems with the approach in the previous commits.
- render_collection (render @sidebar_modules in our case) requires
that all objects return the same partial path. Ours may not do that,
so we wrote our own `render_sidebar_modules`-helper.
- The way render_partial finds the correct path to the partial is
to append what's returned by to_partial_path with whatever root
the parent view is in. That would require duplication of the partials
under all the different engines namespaces. Our `render_sidebar_modules`
does it differently, and just looks up the partial according to the
root namespace. This means the sidebar_module code can move back under
the root application so we don't mess up the refinery namespaces.
- Finally found the proper way to link to a blog_post so that it
works from all namespaces. The correct way is:
refinery.blog_post_path(post)
This works in views (and presumably helpers,) but not in controllers
which is why we struggled with it before.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rewrite the _sidebar_module partial to render only one module,
and to not make any assumptions about the contents of a module.
(Except that it has a title and a body.)
Move the actual module logic into model classes, and use the
ActiveModel magic to have it find it's own partial. Now we
have the view logic for each module in it's own partial that
in turn renders as part of the _sidebar_module partial.
Only implementation this far is the blog-category module
listing the latest blog entries within each category.
|
| |
|
|
|
|
| |
I would like to just render the refinery/blog/index template for
this, but I did not find a way to do it, so I copied it instead. May
need to revisit this if upgrading to a new refinery or blog engine.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Note to self, use model decorators to massage model data, but leave
the markup to the views where it belong.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Also did some code cleanup in
PagesControllerDecorator::populate_sidebars.
The controller will now populate left and right sidebars (only
left for now,) while the SidebarPostDecorator will provide the
markup for each post that is to be shown in a sidebar.
The plan is to further expand the system with other Sidebar-
Decorators, so each item can be rendered using the same in the
partial.
|
| |
|
|
|
| |
List blog categories and 10 most resent posts in each category in
the left sidebar.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Enable all the standard engines:
- blog
- inquiries
- search
- page-images
- videos
|
| |
|
