Never used them to be honest, it's one of the lesser important aspects of a website i think. Good structural concept is much more important than icons ;)
I agree with you Anders, that to have icons that visually represent the document type, makes it easier for the client to quickly identify what type a certain node is. If all nodes have the same default icon then it can be hard for a client to understand what a node is just by looking at the tree.
For example I use FamFamFam icons in the popular starter site CWS I created for Umbraco
Wow pictures in a post :) and what a great way of seeing how sites are structured.
I have a habit of splitting content trees into two. A Home node for the site and it's pages, and a Back Office node for data and meta-data (categorisation) type nodes:
Could post your Home node childs as well to see how that is structured?
And what is the pros/cons of splitting in a content and "back office" and not having alle the generic stuff in the website?
If you link to a thing in the back office the user would get a wierd url like sitename/back-ofice/accounts/companies/test-company - how is that for SEO?
Screenshot of your content tree with famfamfam icons
Hi all,
I would like to see what other uses as therir document icons when using famfamfam icons to make the user expirence much more nice :)
If you would like to share some it would be great to see what YOU do. #h5yr all!!
Never used them to be honest, it's one of the lesser important aspects of a website i think. Good structural concept is much more important than icons ;)
I think both a good structure and nice looking icons is for the better of the client. But just my opinion :)
Example? :)
I agree with you Anders, that to have icons that visually represent the document type, makes it easier for the client to quickly identify what type a certain node is.
If all nodes have the same default icon then it can be hard for a client to understand what a node is just by looking at the tree.
For example I use FamFamFam icons in the popular starter site CWS I created for Umbraco
It's personal taste, but I've seen famfamfam too many times now and prefer fugue icons.
This is one of my own sites...
Wow pictures in a post :) and what a great way of seeing how sites are structured.
I have a habit of splitting content trees into two. A Home node for the site and it's pages, and a Back Office node for data and meta-data (categorisation) type nodes:
Nice to see Hendy.
Could post your Home node childs as well to see how that is structured?
And what is the pros/cons of splitting in a content and "back office" and not having alle the generic stuff in the website?
If you link to a thing in the back office the user would get a wierd url like sitename/back-ofice/accounts/companies/test-company - how is that for SEO?
I doubt a backoffice is accessible for anonymous users, so seo wouldn't apply.
generally a backoffice contains data that may be used in other places, but is not shown as is
here is one of my backoffices with the fam fam icons
The produkt pages of http://dk.krenkerupbryggeri.dk/produkterne/1367-premium looks like this in the backend. :-)
@anders is that famfam icons?
think i manually added the beer icon, rest is famfamfam and famfamfam flags (http://www.famfamfam.com/archive/flag-icons-released/) :-)
I think that the icons choosen in the backend is very important to keep a good user experience.
Combined with the right access rights, you can create a very good working enviroment for the users.
We get a lot of good feedback because of well chosen icons, and also we do a bit of work where we merge two or more icons, etc. for folder structure.
Like the "house"-icon to define a website root a lot. The "house-on-page"-icon is used to describe sub-sites.
This example is in danish though
is working on a reply...