11–20 of 35 posts
I did something similar with a resume template [1] where instead of mustache I use angular. The problem with a purely client side solution is that it doesn't sit well with search engines. You would still need to figure out a way send html from your server at least to the search engines if you want to be indexed. [1] https://github.com/dhawalhshah/modern-resume
I did something similar with a resume template [1] where instead of mustache I use angular. The problem with a purely client side solution is that it doesn't sit well with search engines. You would still need to figure out a way send html from your server at least to the search engines if you want to be indexed. [1] https://github.com/dhawalhshah/modern-resume
What do you mean? Why? What problem do search engines have indexing static content? I've never heard of anything like this before.
Watching the screencast, you can see how a static .html file is generated.
I find it odd that he talks about client side rendering so much on the site and then presents a screencast that doesn't really portray Punch as rendering things in that way. I would like to see a demo video showing how Punch can offer me interesting ways to use client side rendering to make my site better.
Rather confusing, but interesting nonetheless.
Earlier quoted context omitted.
What do you mean? Why? What problem do search engines have indexing static content? I've never heard of anything like this before.
I think he means for the dynamically rendered parts, like "GitHub Watchers".
Others have raised the issue of client side rendering causing issues with search engines. By putting it so prominently on the website, it does make it seem as though it is the intended use. Watching the screencast, you can see how a static .html file is generated. I find it odd that he talks about client side rendering so much on the site and then presents a screencast that doesn't really portray Punch as rendering t…
Screencast was created to quickly highlight the main use case of Punch, which is generating static HTML pages. However, if you read the post further you will find how Punch can be used for client-side rendering.
Also if used correctly, client-side rendering should not cause any issues with search engine indexing. Maybe, I will come up with a separate blog post on how to use client-side rendering with Punch to enhance UX of a site without affecting search engine indexing.
Others have raised the issue of client side rendering causing issues with search engines. By putting it so prominently on the website, it does make it seem as though it is the intended use. Watching the screencast, you can see how a static .html file is generated. I find it odd that he talks about client side rendering so much on the site and then presents a screencast that doesn't really portray Punch as rendering t…
Earlier quoted context omitted.
I think he means for the dynamically rendered parts, like "GitHub Watchers".
Oh, right. I read some comments below and figured that it takes JSON and dynamically renders the template client-side, which seems very unnecessary. Why not just generate HTML? Does Jekyll work that way too?
Earlier quoted context omitted.
Oh, right. I read some comments below and figured that it takes JSON and dynamically renders the template client-side, which seems very unnecessary. Why not just generate HTML? Does Jekyll work that way too?
Punch generates static HTML pages using Mustache and JSON, which can be served from a server. Apart from that Punch's renderer can also be used on client-side to render dynamic content. This is elaborated with an example, in the blog post.