Content menu compartmentalisation - bolt-cms

I'm working on a Bolt driven website which has quite a few contenttypes. Some of which are related to one another. It would be nice to break down the content menu in the admin section to make it easier to see related content.
So for example the list currently is something like this:
one
two
three
four
five
six
etc
I was thinking just a divider line similar to what appears in the settings menu would be enough to help the admin user's eye.
one
two
three
four
----------------
five
six
----------------
etc
Is there a way I could achieve this?

At the moment this is not possible.
You can however add fontawesome icons to your contenttypes for extra visual accessibility in the menu
icon_many: "fa:trophy"
icon_one: "fa:trophy"
Just replace trophy for any of the names in http://fortawesome.github.io/Font-Awesome/icons/
And you can move some less used contenttypes to a submenu with the following option:
show_in_menu: false

Related

How to make an on click collapsible list using html and CSS

when i click on the arrow or the name the list drops down
this is how the expanded list looks like
how do I get this type of collapsible list using html and CSS
I tried it with details and summary tags but it puts the list further away from the other normal lists is there any other way to achieve it.
The question is already answered on stackoverflow and on the internet. Make sure to do some research before asking.
Here are some links: 1. Link 1
2. Link 2
You can take some ideas from these two and make your own custom dropdown.

What do we call the `bottom bar` of an HTML image slider?

English is my second language and I don't know how to call the bottom bar #3 in below snapshot - bottom navigator I guess?
Well there are two few options:
Carousel Controls (this is used in bootstrap as a class name)
Indicators - either Carousel Indicators or Slideshow Indicators (this is used in W3.CSS)
I would think both are just as good in explaining what you mean and they are both used equally as much when talking about those small dots.
You can also use:
Pagination - though this is not as popular, and is mostly used to describe pages and not slideshows
Carousel Dots - which sort of explains it visually
When you need to know a specific term of a thing from a website, you can check the source code (right click → inspect element) as the term is sometimes revealed as a class name or something similar. As far as I can tell they don’t have one definitive name, as each site and each carousel library has their own name for them.
These are some acceptable names:
Carousel indicators
Carousel controls
Carousel dots (Owl Carousel)
Dot navigation
Carousel bullets (on shouldiuseacarousel.com)

How to edit Wordpress menu to make a two-line menu?

I am trying to edit my wordpress page to make every menu item at the top of the page two lines long with the top line being a single word (ie: Home, About, etc.) and another line in a different font underneath each item (ie: "Read about us" underneath "About").
Here is an example of what I mean:
http://images.sixrevisions.com/2009/04/13-26_css_block_menu.png
I am aware that this is achieved in some way by using the 'Description' box on the Wordpress menu screen, and I have checked the 'show descriptions' box, but I'm unable to get it to display correctly.
Any help is greatly appreciated!
You do this by creating a custom walker which extends the Walker_Nav_Menu class - here's a good tutorial on it;
http://www.kriesi.at/archives/improve-your-wordpress-navigation-menu-output

Dynamically Populate Content Within Un-Orthodox Grid

I'm currently developing out a blog page with a 3 X 3 grid layout for content to fall into the different boxes (see attached example).
http://imageshack.us/photo/my-images/337/cssex.jpg/
The content blocks in the lighter gray are meant to be stationary, so any updated, recently added, etc. content will not affect these boxes, only the black ones. I'm trying to figure out the best approach with keeping the gray boxes stationary, but allowing the black boxes to be populated dynamically (WordPress blog entries) and floating naturally through the layout.
As of now, I'm thinking that each individual black box will query the recent post that aligns to it. So, the first black box would query the most recent post, the second black box would query the second recent post and so on.
A big order!
Here is the general idea to help get you going:
You need to make those blocks a <div> or <section> with an ID tag like this:
<section id=brief1>
(BTW, you can also use a "table" & merge cells to get that layout, just ensure you use an ID)
Then you need find a script to update the innerHTML using straight JavaScript, or a JS library like jQuery, MooTools, etc. This will allow you to inject text &/or an image inside those boxes. Example search: http://duckduckgo.com/?q=javascript+update+innerHTML+div
Once you have 1 spot updated with text, it is time to edit that script. Make an array of our ID tags, then loop though all of them to insert new content one at a time.
Good luck! If I see something pre-rolled on my travels, I'll update this thread.

When shall I use list-element in HTML

I have never used list before. I have created a website with over 30 000 LOC and never use a single list-element. But when I look at the source code of other say Twitter they use list all the time. What is the advantage of using list-elements? Most of the time I can achieve the same result with div-elements in terms of lay-out
Semantics. Items in a list are typically related by their meaning, not just their layout.
Chances are if you're using a table with one column you are using the table for layout, this is a good candidate to replace with a list
You should use lists when they are semantically the best choice. When you're creating some HTML, ask yourself the following question:
Am I making a list of things?
If your answer is yes, you want to use the list element, or if it's a list with two or more columns of related information, a table.
By comparison, a list of items created using divs has no meaning. Take the following example of a list:
Sausages
Bacon
Pork
Gammon
That is a list of pig meat products, and normally, your HTML should look like this:
<ol>
<li>Sausages</li>
<li>Bacon</li>
<li>Pork</li>
<li>Gammon</li>
</ol>
This tells us and the browser that all the items in that list are related. They all have a common attribute (in this case, that they are pig meats). If however you were to use this code:
<div>Sausages</div>
<div>Bacon</div>
<div>Pork</div>
<div>Gammon</div>
That tells us (and the browser) nothing about the content, only that they exist on the page. From a styling point of view (i.e. CSS), it doesn't make much difference, and may even make life easier, but it's (a) an abuse of the div element (see: Divitis), and (b) bad for accessibility, since screen readers and other similar software will not be aware that the data is related. Your search engine optimisation can also suffer (in theory).
Do bear in mind that it doesn't have to just be a list of text data, like above. A list of navigation links is still a list, and you should mark it up as such. For example:
<ul class="site-navigation">
<li>Home</li>
<li>About Us</li>
<li>Log in</li>
</ul>
It used mostly for creating menus, but the same results can be easily achieved with div elements.
It is more easy to control your menu if it's a simple list, and I think search engines also prefer them
I'm with Giles on this one, but wanted to expand a bit. A list of items holds semantic value. Anything you list in a page most likely belongs in a list. Examples are:
Products
Navigational menu items
Share links (e.g. Facebook, Twitter, LinkdIn, reddit, etc)
This list itself belongs in a list :)
Also, imagine a scenario in which styles are not applied or are applied differently (very common on mobile browsers, especially those not on newest/advanced smartphones), or if someone using Firefox goes into View -> Page Style and selects No Style to. You still want your page to make sense. If you're listing items on a page, you still want them to appear as some sort of list, not just a bunch of DIVs. DIVs have no semantic meaning except to organize things in separate containers and layout control.