Thread

But you mention separate channels for resorts and transport.

So currently it stands as the below. However this only shows the advice channel entries underneath the advice section, I also want it to show transport and resort links in there that link to /adive/resorts. I guess I can just manually write the links in there which might be easier?

<div class=“nav”>
      <ul class=“sf-menu sf-navbar”>
          <li>HOLIDAYS</li>     
          <li {if '{embed:my_location}’==“advice”} class=“current”{/if}>
      {exp:channel:info channel="advice" style="nested"}
      {channel_title}
      {/exp:channel:info}
          <ul>
              {exp:channel:entries dynamic="no" channel="advice" limit="8" }
              <li>{title}</li>
              {/exp:channel:entries}
          </ul>
      </li>
          <li {if '{embed:my_location}’==“groups”} class=“current”{/if}>
      {exp:channel:info channel="groups" style="nested"}
      {channel_title}
      {/exp:channel:info}
          <ul>
              {exp:channel:entries dynamic="no" channel="groups"}
              <li >{title}</li>
              {/exp:channel:entries}
          </ul>
      </li>
          <li {if '{embed:my_location}’==“events”} class=“current”{/if}>
      {exp:channel:info channel="events" style="nested"}
      {channel_title}
      {/exp:channel:info}
          <ul>
              {exp:channel:entries dynamic="no" channel="events"}
              <li >{title}</li>
              {/exp:channel:entries}
          </ul>
      </li>
      </ul>
      </div>

So currently it stands as the below. However this only shows the advice channel entries underneath the advice section, I also want it to show transport and resort links in there that link to /advice/resorts. I guess I can just manually write the links in there which might be easier?

<div class="nav">
        <ul class="sf-menu sf-navbar">
                <li><a href="http://otherdomain.com" target="_blank" rel="noopener">HOLIDAYS</a></li>        
                <li {if '{embed:my_location}'=="advice"} class="current"{/if}>
        {exp:channel:info channel="advice" style="nested"}
        <a href="http://{channel_url}">{channel_title}</a>
        {/exp:channel:info}
                <ul>
                    {exp:channel:entries dynamic="no" channel="advice" limit="8" }
                    <li><a href="http://{url_title_path=advice}">{title}</a></li>
                    {/exp:channel:entries}
                </ul>
        </li>
                <li {if '{embed:my_location}'=="groups"} class="current"{/if}>
        {exp:channel:info channel="groups" style="nested"}
        <a href="http://{channel_url}">{channel_title}</a>
        {/exp:channel:info}
                <ul>
                    {exp:channel:entries dynamic="no" channel="groups"}
                    <li ><a href="http://{path=groups/{url_title}}">{title}</a></li>
                    {/exp:channel:entries}
                </ul>
        </li>
                <li {if '{embed:my_location}'=="events"} class="current"{/if}>
        {exp:channel:info channel="events" style="nested"}
        <a href="http://{channel_url}">{channel_title}</a>
        {/exp:channel:info}
                <ul>
                    {exp:channel:entries dynamic="no" channel="events"}
                    <li ><a href="http://{path=events/{url_title}}">{title}</a></li>
                    {/exp:channel:entries}
                </ul>
        </li>
        </ul>
        </div>

How often is main nav going to change?  I don’t even use the channel:info tags - no sense making EE run queries to build links dynamically that never change.

Just add channel:entries tag pairs in the Advice section as needed to pull resorts and transport links.

I’d suggest working through this most basic tutorial.

You don’t assign entries to templates per se’.

Rather, you code EE tags in a template to pull the entries that you want that template to display.  Or there are EE tags in a template that dynamically pull entries depending on what URL the template is loaded with.

You can create one template that serves as multi-entry viewer, category-entry viewer, and single-entry viewer, all by how you link to that template.  Usually in a production site this isn’t the case, but it does demonstrate how EE works with templates pulling content.

EE isn’t a “page-centric” CMS, but rather a “post (or entry) centric” CMS.

Thanks , it helps .

I suggest buying and reading Boyink!‘s book @ http://www.train-ee.com/courseware/news/item/new-expressionengine-2-book/. It helped me get up to speed with the general workings of EE very quickly.

I found myself delving into the nether-regions of EE much faster due to his explanations instead of trying to sort out the User Guide for the simple stuff.

Thats my 0.02.

(I really should “preview post” before I submit)

Thanks for the recommendation Ken, I really appreciate it.