Composite C1 - Multiple sites/domains, same design, different main navigation / footer - c1-cms

I have a Composite C1 site with 5 different sites in it (with 5 different domains).
Each site has multiple languages.
Each site has the same basic design (html/css/images) - though is about a slightly different topic with different content.
What is the best way to insert a different navigation menu at the top of each website, and footer at the bottom of each, whilst keeping other layout items the same?
Thanks.

The menus like Composite.Navigation.Distributed or Layout.Navigation.Menu (from the starter site) are subsite-aware etc.
If your subsites share the same layout, you can simply insert the menus like the ones above, they will correctly show the pages that belong to the current website (subsite). you don't need to explicitly "tell" the menu to show pages from a specific site.

Related

Handle no reusable component in React

I'm struggling with following the React philosophy of reusing components.
I have three screens (Screen1, Screen2) that are used as tabs in different pages along my application (Page1, Page2), but these screens are not the same for each page, they differ slightly in the text of labels, buttons, etc that they have. And there is a component, a panel, that is shared among all the screens of a certain page.
Should I create each screen as a different component for each page? Resulting in 4 screen components (two for Page1 and two for Page2)? If yes, should I define them in a different folder than the regular components folder? Because they wouldn't be reusable. Or should I create a reusable component and pass to it the data it should display as json for e.g.?
The question of "Should I extract this as a Component?" is too situational to answer. So it depends on:
How many times will you copy-paste very similar code?
Will they change separately in future? Are their requirements different?
Does the extracted reusable component become extremely long/complex when you combine them?
These are the questions you need to answer.

When should I use Lists vs Menus in Material-UI?

I'm having trouble figuring out the difference between Lists and Menus in Material-UI.
Docs
Lists - https://material-ui-next.com/demos/lists/
Menus - https://material-ui-next.com/demos/menus/
Description
My thinking is that Menus are used for routing and navigation while Lists are used for configuration or static content, but then I saw these quotes:
Menus appear upon interaction with a button, action, or other control. They display a list of choices, with one choice per line.
Reading this, Menus aren't intended to always show, they're designed to be hidden and only shown temporarily.
Menus should not be used as a primary method for navigation within an app.
This makes it seem like a sidebar with a list of navigation elements should be a List. If so, what if I take the same component and want to also use it in a dropdown menu? Do I have to make a separate component using Menu components?
Question
Since the docs are unclear to me, what instances would I want to use Menus vs Lists?
These components follow the Material Design standards, so their intended use would follow the standards.
For Menu:
Menus display a list of choices on a transient sheet of material.
For List:
Lists present multiple line items vertically as a single continuous element.
So while they're similar, I think the key difference is that Menu is intended for a transient selection, presented within something like a Dialog or Modal.

Featured items won't stack in rioght hand columns

My menu item "Home" points to a "featured article" which I have set with layout #leading articles =0, #intro articles=8, #columns =2. Order of presentation on the page is oldest first.
The welcome text on the left is quite long and sits on the left column ok. The next article is short as it has a read more break (like the other articles that follow) and sits on the right hand column fine.
But the next two articles hide down the bottom and across the page. I really want to make them fill up the empty space below the article on the right. There is a lot of space there as the article on the left is quite long. see www.resbona.co.uk
Is what I'm trying to do possible?- I'm using Joomlashack Vintage template with Joomla 3 (latest).
And if so how to do?
Thanks for any help
Derek
This is not possible with basic Joomla Content Component without modifying code. What you can do to archive this is:
Limit featured items count to 1
Add Articles Category module to right column
Set module articles ordering and filtering options to match your front page options
To archive the same using Joomla component only you will have to use Template Override and create your own layout for featured items or override default.

Drupal site sections and end user input

I would like to have sections of a site so the top menu is a menu of sections such as "About Us". Then I want to have a secondary menu of pages within that section in the left sidebar. I know how to lay this out in drupal, but I want to make it easy for my end users to put the page they create into the proper section of the website. Would it be possible for me to create a taxonomy of terms that represent the 5 or 6 sections of the site and then somehow create the path to the page for the section they select in the taxonomy pull down menu?
Download Node Hierarchy, it has exactly that functionality

add main menu item in drupal 7

I have many content type that I have added in drupal 7 and I want them to be available in main menu. For example I have content types:
news
events
and I want the main menu look like
home - news - events
Despite I checked available menu > main menu
it doesn't show up in the main menu. How can I fix this?
Content types refer to the different types of nodes that you can create. Making your news content type available for the main menu means that, when you create news nodes, you can place them in that menu.
If you are trying to create a page that lists news nodes, you need to look into the Views module. It will allow you to create pages or blocks containing lists of content. Then, you can put those pages in the main menu. You can find the Views module here: http://drupal.org/project/views

Resources