I am very new using drupal which you would know from my questions. Yes, I will seperate navigation from the content of the 60 plus pages. I understand this.
Some one suggested to use panels for all these inside pages. I can use 2 column layout. Left for content and right for navigation. Question is in my understanding of this concept. This means should we create 60 such panel pages with 2 column layout? some content on left column is static and some comes from the views. OR should ww use 2 column theme and create 60 plus basic pages? I believe if we use pannels then I don't need a theme for inside pages. I have pge.tpl.php for the home page.
On Thu, Nov 21, 2013 at 9:51 AM, themes-request@drupal.org wrote:
Send themes mailing list submissions to themes@drupal.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/mailman/listinfo/themes or, via email, send a message with subject or body 'help' to themes-request@drupal.org
You can reach the person managing the list at themes-owner@drupal.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of themes digest..."
Today's Topics:
- Re: themes Digest, Vol 72, Issue 5 (David Metzler)
Message: 1 Date: Thu, 21 Nov 2013 06:51:07 -0800 From: David Metzler metzler.dl@gmail.com Subject: Re: [themes] themes Digest, Vol 72, Issue 5 To: A list for theme developers themes@drupal.org Message-ID: A7B18255-04F9-4F19-A48D-F7A1C06EF7D5@gmail.com Content-Type: text/plain; charset="iso-8859-1"
Typically this is done in drupal with the navigation being separated from the content of the 60 plus pages and using the navigation as drupal blocks inside a "sidebar" region in a theme. Is there something about this approach that doesn't work for your use case?
Just trying to figure out how new you might be to the drupal way of doing things.
On Nov 20, 2013, at 6:33 AM, vibanu vibanu@gmail.com wrote:
Chris, I will get the book. Thanks for your suggestion.
I have page.tpl.php theme copied and modified from Zen. In Drupal, for
the home page, I enabled system noode_view and created a variant for the HOME page with a selection creteria for front page and 3 column layout panel. This is now overwriting the templates content area.
Our other inside pages of the static website have 2 column layout.There
are over 60 such pages with left side being content and the right side is the navigation.
I am trying to understand if I need another template for these inside
pages on Drupal and the relationship of panels with the inside template for over 60 pages? What is the best way acheive this functionality?
On Wed, Nov 20, 2013 at 7:00 AM, themes-request@drupal.org wrote: Send themes mailing list submissions to themes@drupal.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/mailman/listinfo/themes or, via email, send a message with subject or body 'help' to themes-request@drupal.org
You can reach the person managing the list at themes-owner@drupal.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of themes digest..."
Today's Topics:
- Re: themes Digest, Vol 72, Issue 3 : migrating static HTML page with TABS to DRUPAL (Chris McAndrew)
Message: 1 Date: Tue, 19 Nov 2013 18:51:47 -0500 From: Chris McAndrew chris@csmcreative.com Subject: Re: [themes] themes Digest, Vol 72, Issue 3 : migrating static HTML page with TABS to DRUPAL To: themes@drupal.org Message-ID: <CAFV3ugkDuoNr+YD=
YiYNrJkiEbD_8Of7wy64OjQhwnF69fHYWQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Drupal definitely isn't something you will get up to speed with in a
short
period of time. I think you really have to work with it every single day and make it your focus. If it has to be in Drupal for whatever reason
than
you have no choice but if it's just for tabs, I don't get it. Maybe WordPress or something would be easier and quicker.
Drupal kicks butt though and I will never touch WP again. The best book
for
me that I reference daily is the Pro Drupal Development book. It's a big yellow and black book and covers everything you need or might want to learn.
Good luck and you definitely have plenty of help here so always ask.
Chris McAndrew??
*[image: http://csmcreative.com] http://csmcreative.com Chr**is
McAndrew*
*Interactive Designer & Developer Mobile*: 1.603.498.3864
- Email*: chris@csmcreative.comchris@csmcreative.com<
chris@csmcreative.com?subject=Question+via+email+contact+link>
- Web*: http://csmcreative.com
*Twitter*: @chris_mcandrew https://twitter.com/chris_mcandrew *LinkedIn*: chrismcandrew http://linkedin.com/in/chrismcandrew
On Mon, Nov 18, 2013 at 1:38 PM, themes-request@drupal.org wrote:
Send themes mailing list submissions to themes@drupal.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/mailman/listinfo/themes or, via email, send a message with subject or body 'help' to themes-request@drupal.org
You can reach the person managing the list at themes-owner@drupal.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of themes digest..."
Today's Topics:
- migrating static HTML page with TABS to DRUPAL (mullick)
- [#JMB-402-45965]: migrating static HTML page with TABS to DRUPAL (RebirthRO)
- Re: migrating static HTML page with TABS to DRUPAL (Carl Wiedemann)
- [#GFX-836-29289]: Re: migrating static HTML page with TABS to DRUPAL (RebirthRO)
- Re: migrating static HTML page with TABS to DRUPAL (Sushanta Banerjee)
- [#IGY-236-37981]: Re: migrating static HTML page with TABS to DRUPAL (RebirthRO)
- Re: migrating static HTML page with TABS to DRUPAL (David Landry)
Message: 1 Date: Mon, 18 Nov 2013 10:33:03 -0500 From: mullick vibanu@gmail.com Subject: [themes] migrating static HTML page with TABS to DRUPAL To: themes@drupal.org Message-ID: < CAMVtPvjvrqenR2usobBwzj8tYB+pOV5a5z+QyHT+E7XVzCqGKg@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1"
Hi, I have to move our static HTML site to DRUPAL. I am one week young
user
of drupal and I am reading and learning from others experiences. I will appreciate if you can give me your suggestions on the best way to restructure the following similar page (with tabs) to DRUPAL? http://www.cs.sunysb.edu/people/faculty.html Thanks in advanace!
On 11/22/2013 03:28 AM, vibanu wrote:
I am very new using drupal which you would know from my questions. Yes, I will seperate navigation from the content of the 60 plus pages. I understand this. Some one suggested to use panels for all these inside pages. I can use 2 column layout. Left for content and right for navigation. Question is in my understanding of this concept. This means should we create 60 such panel pages with 2 column layout? some content on left column is static and some comes from the views. OR should ww use 2 column theme and create 60 plus basic pages? I believe if we use pannels then I don't need a theme for inside pages. I have pge.tpl.php for the home page.
Not at all.
I do not understand separating navigation from content, Navigation is a menu structure, content is filler for the page and can be displayed anywhere on the page. I have not found a reason for 60 plus pages in any of my dev work, our largest site has 15 pages but this is because of users, roles, permissions and specific data entry that is required in that particular system.
You may need a few pages but Panels can render content onto a page, then with the click of a mouse render different content to that page and even change the page layout for each render. All on the one page or small set of pages.
Johan Falk, NodeOne, Scandinavia has done a fantastic set of 13 tutorials on using panels, they are an inspiration in how to rethink the way we use Drupal and Panels. I learned much and am in the processof redesigning our system accordingly and the best part, for me is that Panels uses our existing data and views and we can use the minimal Zen theme and we do not have to do any theming, Panels does that. A minimalist Zen works a treat for us.
But you can use any theme and switch off all of it's attributes so it's a blank page. I found this to be quite messy.
Regards Roger
Yes, I think many of us are saying the same thing here. Many people new to drupal are also new to database driven CMS's. It's best to stop thinking about 60 pages of content plus navigation and think about the different types of content you have, then see if you can create panels that override the node(page) views of the content, and/or or add menus / features as blocks to the sidebars of the theme.
It's hard to advise, because how you organize the content depends on how the navigation relates to the content… whether its a hierarchy (in which case taxonomies or books might be more appropriate… or wether it's a list of related popular content…. how much repetition there is in the navigation elements and how they relate to the content. Ultimately you should not end up creating 60 panels… that would not be sustainable, but rather create potentially a panel variant for each type of content, or panel(s) that house views of content or other features.
I don't know if this helps but definitely check out the tutorials mentioned.
On Nov 21, 2013, at 2:32 PM, Roger arelem@bigpond.com wrote:
On 11/22/2013 03:28 AM, vibanu wrote:
I am very new using drupal which you would know from my questions. Yes, I will seperate navigation from the content of the 60 plus pages. I understand this. Some one suggested to use panels for all these inside pages. I can use 2 column layout. Left for content and right for navigation. Question is in my understanding of this concept. This means should we create 60 such panel pages with 2 column layout? some content on left column is static and some comes from the views. OR should ww use 2 column theme and create 60 plus basic pages? I believe if we use pannels then I don't need a theme for inside pages. I have pge.tpl.php for the home page.
Not at all.
I do not understand separating navigation from content, Navigation is a menu structure, content is filler for the page and can be displayed anywhere on the page. I have not found a reason for 60 plus pages in any of my dev work, our largest site has 15 pages but this is because of users, roles, permissions and specific data entry that is required in that particular system.
You may need a few pages but Panels can render content onto a page, then with the click of a mouse render different content to that page and even change the page layout for each render. All on the one page or small set of pages.
Johan Falk, NodeOne, Scandinavia has done a fantastic set of 13 tutorials on using panels, they are an inspiration in how to rethink the way we use Drupal and Panels. I learned much and am in the processof redesigning our system accordingly and the best part, for me is that Panels uses our existing data and views and we can use the minimal Zen theme and we do not have to do any theming, Panels does that. A minimalist Zen works a treat for us.
But you can use any theme and switch off all of it's attributes so it's a blank page. I found this to be quite messy.
Regards Roger
themes mailing list themes@drupal.org http://lists.drupal.org/mailman/listinfo/themes
Well said David. The problem with coming from standard web site design is that it does not relate to CMS design. The trick is to realise that Drupal is, and provides, content management -- through the creation of content types, each of which handles a different part/sort/type of content be it form data, blocks of text, images, menus, etc.
All variations of that content, no mater what it is, can be displayed anywhere on one or two pages just by telling the cms what and where to display, to whom and when. Panels or Blocks can do that equally well but I find Panels much easier.
Maybe, instead of Navigation, use the term Menu. You can have as many different menus for navigating the content which in turn relate to the display of different content on the same small page set.
I have found that in Drupal, the term Navigation refers to quite a specific and predefined type of menu and I never use it. It like all menus and blocks can be switched on or off.
You have 60 pages. These will all contain similarities that you need to consider. Header,text, images, footer, dates, videos, etc. Have a read up on creating content types in Drupal.
I would strongly suggest not trying to create a finished cms as a beginner but have a sandbox development install that you can experiment with, add and remove modules and themes, learn panels and blocks and simply delete and reinstall if it all goes wrong. We all learned this way or some variation thereof. I have used Drupal for many years yet use a sandbox install for experimenting, sometimes I have a sandbox, a test setup and the soon to be live site. But that is still not the actual live site on another server.
Cheers Roger
Yes, I think many of us are saying the same thing here. Many people new to drupal are also new to database driven CMS's. It's best to stop thinking about 60 pages of content plus navigation and think about the different types of content you have, then see if you can create panels that override the node(page) views of the content, and/or or add menus / features as blocks to the sidebars of the theme.
It's hard to advise, because how you organize the content depends on how the navigation relates to the content… whether its a hierarchy (in which case taxonomies or books might be more appropriate… or wether it's a list of related popular content…. how much repetition there is in the navigation elements and how they relate to the content. Ultimately you should not end up creating 60 panels… that would not be sustainable, but rather create potentially a panel variant for each type of content, or panel(s) that house views of content or other features.
I don't know if this helps but definitely check out the tutorials mentioned.
On Nov 21, 2013, at 2:32 PM, Roger arelem@bigpond.com wrote:
On 11/22/2013 03:28 AM, vibanu wrote:
I am very new using drupal which you would know from my questions. Yes, I will seperate navigation from the content of the 60 plus pages. I understand this. Some one suggested to use panels for all these inside pages. I can use 2 column layout. Left for content and right for navigation. Question is in my understanding of this concept. This means should we create 60 such panel pages with 2 column layout? some content on left column is static and some comes from the views. OR should ww use 2 column theme and create 60 plus basic pages? I believe if we use pannels then I don't need a theme for inside pages. I have pge.tpl.php for the home page.
Not at all.
I do not understand separating navigation from content, Navigation is a menu structure, content is filler for the page and can be displayed anywhere on the page. I have not found a reason for 60 plus pages in any of my dev work, our largest site has 15 pages but this is because of users, roles, permissions and specific data entry that is required in that particular system.
You may need a few pages but Panels can render content onto a page, then with the click of a mouse render different content to that page and even change the page layout for each render. All on the one page or small set of pages.
Johan Falk, NodeOne, Scandinavia has done a fantastic set of 13 tutorials on using panels, they are an inspiration in how to rethink the way we use Drupal and Panels. I learned much and am in the processof redesigning our system accordingly and the best part, for me is that Panels uses our existing data and views and we can use the minimal Zen theme and we do not have to do any theming, Panels does that. A minimalist Zen works a treat for us.
But you can use any theme and switch off all of it's attributes so it's a blank page. I found this to be quite messy.
Regards Roger
themes mailing list themes@drupal.org http://lists.drupal.org/mailman/listinfo/themes
themes mailing list themes@drupal.org http://lists.drupal.org/mailman/listinfo/themes
-
David Metzler -
Roger -
vibanu