arkkimaagi / assemble-website-template Goto Github PK

Now that Google Chrome frame support has been retired, the references to that on the source code are unneeded.

I'm not even sure how to begin, should be fun.

http://andismith.github.io/caniuse-widget/

I'm not entirely sure what's needed for the generation of RSS with assemble, but this should be working since day one of the site release.

The current implementation of the helpers in this template is a mess, mostly because assemble code is in flux. This should be cleared when the new assemble code lands.

Something along the line what was done at SyncronTech back in 2005, along these lines: https://github.com/diagnosticss/diagnosticss but using the methods with generated content and such.

Faster pageloads, better mobile support.

https://github.com/jamesgpearce/confess

Something broke with assemble, the automation section is not updating.

It will be a nice to have a document of all the things considered while building this, I'd imagine it will be a long list.

This should be interesting.

Basicly it needs three things, generating the index from content, searching the index clientside:
http://lunrjs.com/

and adding meta-code for search tools to access it.
https://github.com/h5bp/html5-boilerplate/blob/v4.2.0/doc/extend.md#firefox-and-ie-search-

Maybe templates for different type of pages should be created, so that they have proper meaning and structure.

As a sidenote, this is closely related to ARIA landmarks in #17.

Should be simple, quite same as the fb-metadata

SEO likes better meta descriptions, each page should have unique meta description:
http://www.agent-seo.com/seo/meta-description-optimization-writing-effective-meta-descriptions-for-seo/

Length should be between 175-225 characters spaces.

The meta description should be unique per page.

Pass just the relevant files for bundling. This reduces the amount of data in assemble and makes debugging easier

The current layout structure is a bit messy as there is no support for inheriting layouts in assemble at the moment.

/src/__assemble/layouts/base_html_layout.hbs should be the main html base and default.hbs should inherit it.

I looked at this a while ago, but I've been so busy with stuff lately I decided to check back and you have all kinds of cool stuff in this project. those helpers are awesome. want to maintain a repo/project/boilerplate for assemble or something?

All served javascript should be minimized instead of just concatenated. The last time I worked with grunt-contrib-uglifyjs it had some problems with simple concatenation and I needed that more than minimization.

This time minimization is needed. Should be easy to support both.

Something like prism should be handy:
http://prismjs.com/

http://accessibility.oit.ncsu.edu/blog/2011/06/30/using-aria-landmarks-a-demonstration/

Go trough them..

With the static site, everything should be gzipped to save time and bandwith. This can be done in advance before moving over to the server.

Maybe add something like grunt-contrib-compress into the mix and remember to write proper .htaccess files too.

This needs support from Assemble, I'll have to do a pull request to get it running properly.

The blog generator thing should be planned. There has been some talk with assemble about generated pages, but nothing concrete.