Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How to create CSS based skins with YAML (best CSS-Framework) - free base skin and tutorial availableHow to create CSS based skins with YAML (best CSS-Framework) - free base skin and tutorial available
Previous
 
Next
New Post
6/18/2009 8:31 AM
 

Blueprint is by Google (http://code.google.com/p/blueprintcss/), not Blurprint.

Yes, YAML doesn't dictate that your website has to be a grid layout (because YAML is not a prefab layout, the five rules) — but you easily can build grids with subtemplates in seconds. And this makes the difference, because you're much more flexible and although very fast. However the design should look like, you can do it with YAML. Most designers don't understand CSS, that's why it's important you have the full control about your layout.

 
New Post
6/18/2009 10:04 AM
 

yaml wrote
 

Blueprint is by Google (http://code.google.com/p/blueprintcss/), not Blurprint.

Yes, YAML doesn't dictate that your website has to be a grid layout (because YAML is not a prefab layout, the five rules) — but you easily can build grids with subtemplates in seconds. And this makes the difference, because you're much more flexible and although very fast. However the design should look like, you can do it with YAML. Most designers don't understand CSS, that's why it's important you have the full control about your layout.

Just read an article about Blueprint CSS. It's not developed by Google but at least hosted.

Regards, Silvio

 
New Post
6/19/2009 6:03 AM
 

Question/scenario:  most css-div based layouts claim to be flexible, elastic, and more elegant than table-based layouts.  However, I have not yet found one that is any where near elegant or worth using when you consider the true elasticity of a table.  YAML for DNN looks promising.

As a designer, you also have to consider that you are designing a one-size-fits-all template.  Most div/css layouts cannot achieve that at all.  Generally, if you have a column set to 250px wide and the end user inserts a photo 400px wide, instead of stretching the column and wrapping around this photo, it merely places the photo in column 1 while overlapping the content of column 2.  Less than gracefully, too, and your skin/layout is suddenly broken and looks extremely unprofessional.

Yet, a simple table takes care of that problem because a table is truly 100% "elastic".  Can the YAML layout function exactly like a table in regards to this issue?  The only reason I have refused to design without tables is because, in this respect, div's are just more of a step backwards than they are forwards.  Perfect examples are right here at this site in this forum.  I see a lot of posts where the text actually gets written over the right side border that is supposed to be the edge of the content.  In a professional looking design, regardless of whether it's table or div based, that right hand border had better be able to expand gracefully to wrap around the content placed inside it.  I have just not seen any div based layout that can do that.  That is, unless your group has discovered the fix?  As soon as div/css based layouts actually prove to be more elegant and can truly be elastic, I'll switch over and leave table based design behind, and I'd love it if your template would allow me to do so with a good conscience that I really am providing a client with a DNN skin they will love.


JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

New Post
6/19/2009 6:05 PM
 

Ok, so I've finally gotten around to following the tutorial, and for the most part it works, but I am encountering some typical CSS issues and I have a feeling some may be cropping up from the 'liberties' I've taken with instructions provided... First I'm attempting this on a DNN 5.0.1 installation, second for the navigation I have just dropped in the standard DNN Nav token (still evaluating menu systems, Xmenu from MarkItModules.com is looking very promising). Beyond that I have followed the directions on the tutorial.  However, when I get the ASCX modified and copy in the CSS files, it looks right but the panes overlap the drop-down menus. I attempted to give COL1 and 3 a lower Z-index than the #nav and .main_dnnmenu_bar assets but no luck.

Any thoughts?


Wells Doty Jr
Online Content Development
 
New Post
6/19/2009 7:01 PM
 

Wells Doty wrote
 

I attempted to give COL1 and 3 a lower Z-index than the #nav and .main_dnnmenu_bar assets but no luck.

You have to set the z-index on the submenu class settings.  I ran into this problem with DNN Nav and flash before.  You have to make sure you assign the z-index: 1000 to the submenu's td class.  Meaning if the submenu class is Main_Submenu, then the z-index is applied to "Main_Submenu td".  That may or may not work, if not, then it may be an issue with YAML.  They are working on an unordered list rendering of the DNN Nav menu for DNN 5, but as far as I know, it is still very buggy and not ready for production use yet, hopefully it will eliminate the desire or need for third party menu modules.

Rick


JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How to create CSS based skins with YAML (best CSS-Framework) - free base skin and tutorial availableHow to create CSS based skins with YAML (best CSS-Framework) - free base skin and tutorial available


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out