MODX Boilerplate - a HTML5 template framework

Quote from: ThaClown at May 24, 2011, 08:19 AM

- How can I keep using yepnope in the footer and bypass this problem?

This is expected behavior.
You should consider setting display: none; for all images first to avoid this behavior. Slides script should set this to block for sliding images afterwards.

Quote from: ThaClown at May 24, 2011, 08:19 AM

- Is placing JS in the footer really that mutch better?

Yes it is. If you load jquery (~150kb) with additional scripts (~50kb) in header, js-files are loaded and executed just before rendering the body of the page (which contains layout). This blocks entire layout and handling on site until all scripts are loaded correctly. If you load external contents like Facebook-API from their lazy servers this could be very bad.
For now no browsers support HTML5 web-workers and asynchronuous loading 100% what makes need of yepnope.js
And so you have to load all content and then load all javascripts afterwards (so you can already use the page). In modern browsers like Chrome it makes use of asynchronuous loading which means it loads parallel to the pageload and should be much faster than in IE7/8.


Quote from: ThaClown at May 24, 2011, 08:19 AM

It is not the position of the code... placing the yepnope in the header does not fix this problem, Plaing this:

yepnope waits until js-document-ready

Thank you very mutch, works great now!

http://nieuwe-website-ontwerpen.nl/modular/

Quote from: ThaClown at May 24, 2011, 08:57 AM

Thank you very mutch, works great now!

http://nieuwe-website-ontwerpen.nl/modular/

If you’re not using Google analytics or PIWIK analytics, please remove these scripts form js-files.

Thx forgot about those....

The include template snippet is not working in the modx 2.1.0-pl version.
It removes the closing ( ?> ) php tag.

Anyone with the same problem?

Thanks in advance

Quote from: niceoutput at Jun 20, 2011, 06:49 PM

The include template snippet is not working in the modx 2.1.0-pl version.
It removes the closing ( ?> ) php tag.

Anyone with the same problem?

@niceoutput: Sorry, this is not the right topic here for your problem. Please post again in a separate topic with your snippet code.


I currently am working on version 2 of my MODX-Boilerplate and I think it will be great then. Some key features:

• responsive media-queries
• reviewed code (free from old stuff)
• default html5-polyfills
• even more flexible
• inuit.css framework inside
• available as a MODX-package
• more Facebook stuff if needed
• default configurations with several options (and maybe a wizard)
• minified scripts, css etc.
• extended scritp loading with HTML5 features
• sample themes (free and for purchase)
• tutorials, wiki, online-trainings

We’re now on twitter with a separate account: http://twitter.com/modx_bp
And we’re releasing a whole website around v2 when it’s ready.


By the way: We’re searching for another person who is understanding the whole framework (including html5, css3, polyfills, load-techniques, etc.) and want to participate to this project. It’s just because maintaining this project is a lot of time and it would be easier to handle with 2 persons behind it. So if you want to help me out, please write me a message.

I have a question to all my users of the MODX-Boilerplate regarding to usage behavior:

I now have the possibility to change to responsive media-queries for upcoming version2 of MODX-Boilerplate.
This means that all basic styles (css-normalization, default font-styles etc.) would go to smartphone.css (which is the smallest device) and all other css-files would only contain additional styles fitting to their devices.

What do you think about that? Personally I would prefer this.
For you it means you have either change the css-code entirely to your setup if you’re not using media-queries or either you have to use media-queries consequently on your sites.

I like it, makes sense when you think about the 320px and up concept...
Maybe for non-media-queries users there could be a ’regular’ CSS file or version?

Hi, just found and started to try out the boiler plate.

Looking through the header code right at the top it makes reference to fbml. I was curious what this was for and looked it up. Now on the Facebook developers site it says this will be deprecated on 1st Jan 2012 and not supported after 1 June 2012.
http://developers.facebook.com/docs/reference/fbml/

Will this affect the boilerplate templates?

Thanks

Adrian

@Adrian: Sorry, unfortunately I didn't see this post because email notifications do not work. This change was new to me. Luckily this won't break your site, it just won't be recognized.

I'll push an update for that as soon as possible.

It is better to directly submit an issue at github so I will be notified. Thanks for reporting!