|Drupal blocks, beans, etc. |
Drupal blocks, beans, etc.
May. 12th, 2014 @ 10:07 am
I need to create "hub pages" (pages with multiple blocks to different areas of a Drupal site) but I have limited access to what I can modify.
Right now the pages that are supposed to be "hub pages" are just simple content pages with a series of divs and inline CSS as blocks, which IMO is a really bad way of coding pages when we can use Drupal to its full potential. And we're also wasting a lot of time tweaking the inline CSS which is being overwritten by the Drupal css...
I think what we should be doing for browser compatibility is to use the "Drupal Blocks" area of the site to create blocks that can easily be added to multiple pages but I don't fully understand how Drupal blocks work.
I'm not really sure what I should be doing and with limited access to most of the block types (the only blocks I can create are "beans"), I need to understand this more before I can get the access I need from the other team who installed the site.
There are several other types of blocks already created so I added some HTML content to it, but I don't know how to add that block to a bean page or if it should be added to a content page?
I'm a Drupal veteran, and I'm here to help :)
YES if you're placing small bits of content that may exist on multiple pages... use blocks!
The concept is really simple. Create a block with whatever content, assign it to a region (a place in a page template) and then setup what paths the block is visible on. Simple stuff really. It's like modules in joomla or "widgets" in wordpress... only 100x more powerful with notably more potential.
Beans are essentially blocks with fields (blocks become fieldable entities if you want to get technical). When working with clients, you can create a block, give it a variety of fields the client should enter, allow block creation, theme the fields... etc etc. Gives you reliable reproducable content, keeps the client from doing something silly with a WYSIWYG... the reasons are endlessly as to why you should do this :)
If you are creating content that only exists in one place ever, blocks/beans is not the way to do it. Some one setup your structure incorrectly and didn't do a good job conceptualizing these hub pages you are talking about.
Explain the "I have limited access to what I can modify" bit...
|Top of Page
||Powered by LiveJournal.com|