context

I was wondering if anyone had any suggestions as to how I would go about creating a simple context-based menus system using side-by-side sidebars as in this site: walterbernarddesign.com

The intended usage would play out like the example on this page: walterbernarddesign.com/ourwork/newspapers/barrons

I'm sure there must be a relatively straight-forward solution for doing something like this, but so far it escapes me.

** UPDATE: I will be unable to attend DrupalCampNYC 8, but will gladly share my slides and presentation notes if anyone else wishes to present this session. **

** NOTE: This is the same session I did at Drupaldelphia and DrupalCamp Colorado. **

There are ways to organize a page before it gets rendered to the screen. The purpose of this presentation is to show what Drupal does out of the box (blocks/regions) and then show 2 alternatives that provide more flexibility (context & panels). We will identify the strengths and weaknesses of each and provide examples for situations where one is more suited than the other.

Hi, I am working on a site designed to be bilingual and am using OP 1.7. I subthemed the OP theme and being new to Drupal, it took me a while to figure out that the frontpage layout was handled by the frontpage context item. So my aim is to duplicate that frontpage context, let's say to a frontpage_fr and make the same blocks available, but with French content. My problem is that it did not work when i specified the path as "fr".

Translators do not translate pieces of text, they translate meanings of pieces of text. For small projects and long text snippets this does not make much of a difference. A human translator can figure out the meaning and come up with a translation for it. Drupal now uses 190.000 unique strings and some of them are used in many places and by many different modules. While it is nice to reuse already translated strings in different places of the user interface some of them have a different meaning albeit having the same text.

Hello all, and thanks for the great view module, especially to merlinofchaos.

I did some research and did not find a thing even remotely connected to this so I'll try to explain the problem and the few solutions I have in mind, hoping the experts here will be able to guide me toward means to realize them or advice me. Or plug my nose on a "fucking manual 'RTFM' way".
I thought this http://drupaleasy.com/blogs/ryanprice/2008/06/using-views-2-drupal-6-cre... and this thread http://groups.drupal.org/node/37414 could be related but I think my case is more general. Slap me if I am wrong. ;)

The problem :

Let's imagine we have a newspaper-like publication.
You have a top story, on top of the page, and then fixed topics (about cats, dogs, new news, old stories, whatever).
Every story is "tagged" in taxonomy, and can belong to several ones...
Of course, on the front page you want :
- the most recent story in the top story panel
- the most recent story in every topic in the fixed panel dedicated to that topic, but one that is NOT the top story and NOT already a frontage story for another topic (not already the most recent story for a "previously rendered" topic that is not the "top story")

Said more simply : a "story" should appear once and only once on the frontpage being as the top story or the featured story in a topic.

I've noticed that the Author Information is not showing at the bottom of "blog" and "article" content. In OP1.5 it showed. When I looked at the Contexts, I found that Author Information is not there.

Then I tried to add it, but didn't show up on the node. I tested by adding "Who's Online" block at the end of a blog/article, and it works.

Any clue as to why Author Information is not being added? How do I add that? Thanks in advance.

I was wondering if subtheming or overriding CSS is a possibility for the theme provided with OP 1.6?

Hi Folks,

Curious how best to skin this cat. I'm looking to trigger a context based upon the arguments passed to a view. The view is using a page layout. The argument is a taxonomy term. The context condition is set by that taxonomy term.

Desde que conheci o módulo "context", fiquei empolgado com a possibilidade de não depender basicamente da url e papéis dos usuários para contextualizar menus, blocos, etc. Ganhamos em flexibilidade com ele.

"You can think of each context as representing a "section" of your site. For each context, you can choose the conditions that trigger the context to be active and choose different aspects of Drupal that should react to this active context."

Esse link aqui tem uma explicação muito completa sobre o funcionamento dele:

I'm building a website that consist of a main website and three office locations/branches websites. The main website pulls content from all three locations.

Location websites must have a 'home page' with a unique url, as well as the main website ofcourse. Each location must have an allocated admin role that can manage that location content only.