hodgesmr / empress Goto Github PK

Dynamic JS content is hard for Google to crawl. Look in to options to make Empress content crawlable.

https://developers.google.com/webmasters/ajax-crawling/

First, this is an awesome project. I've worked with Jekyll or a while, but got sick of it. I'll probably switch to this.

One of my first thoughts was that there are a lot of http requests here, but the whole thing otherwise feels really nimble.

Would you be open to a pull request that concatenates and minifies CSS & JS as part of the build, or do you think that's unnecessary and something that would be better to do on my own fork? I'm just thinking of the vendor JS scripts and 3 CSS files. This could be even faster by cutting down on those.

Right now, the App.Posts loop just loops the links to each post. Wouldn't it be more interesting if it had excerpts? Perhaps there could be a method to just grab the first paragraph, or first 100 words or something with a "Read more…" link?

This also raises issues of pagination. With or without excerpts, a blog with 100 posts would just scroll forever. Are there any plans to handle that?

If the screen is small enough to generate the nav dropdow, it doesn't close if you select the page you're already on. Example: select 'Home' while at home.

Iterating over that posts array is slow, especially as the number of posts grow. Either change json structure or find a smarter way to pull a post from the list.