Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

cdmedia.github.io

Post reply on HN
Print view View original

91–97 of 97 posts

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#91

Post by [deleted] »

opiotrek wrote: post #47
EvanPlaice wrote: post #10

Cool. I'm actually building something very similar @ http://evanplaice.com . I use Markdown/JSON for all of the content. Markdown files can easily be embedded in a page using the directive I wrote. The source is @ http://github.com/evanplaice/evanplaice.com . I'm planning to eventually extract the good bits, and adapt it to work with Jekyll files. Front-matter support is the last major road block. Google shouldn't ha…

That is truly terrible user experience. Pure example of form over substance.

[deleted]

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#92

Post by EvanPlaice »

jackmoore wrote: post #80
EvanPlaice wrote: post #10

Cool. I'm actually building something very similar @ http://evanplaice.com . I use Markdown/JSON for all of the content. Markdown files can easily be embedded in a page using the directive I wrote. The source is @ http://github.com/evanplaice/evanplaice.com . I'm planning to eventually extract the good bits, and adapt it to work with Jekyll files. Front-matter support is the last major road block. Google shouldn't ha…

I see you are getting some negative feedback, haha. I think the main problem at this point isn't due client-rendering, but the large prerequisite files. Gzipping your JavaScript would trim a MB or more. Putting the static assets on a CDN (or enabling gzip yourself) would cut the render time by 2/3rds. Semantic UI adds 700KBs of CSS, which seems like a lot more than your site should need. Even if this were a static re…

Haha. I figured 'working on' would signal that this isn't 'production ready' yet.

Guess I should choke down my excitement and stay in stealth mode until I'm ready next time.

The entire app is server-less and hosted on a S3 bucket.

Gzipping the content should be an easy addition to the build process.

I'm using approximately 2% of what Semantic-UI is capable of. Fortunately, Semantic-UI provides a set of tools to trim it down to a production-ready bundle.

In addition, Google will likely trim more of the fat from Angular2 in upcoming releases.

The big one I'm concerned about is Rxjs. The size of the lib is massive considering it only provides support for observables and observable extensions.

Trust me, I'm painfully aware of how slow it is right now.

Thanks for the feedback though. I do appreciate it.

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#93

Post by EvanPlaice »

afandian wrote: post #35
EvanPlaice wrote: post #10

Cool. I'm actually building something very similar @ http://evanplaice.com . I use Markdown/JSON for all of the content. Markdown files can easily be embedded in a page using the directive I wrote. The source is @ http://github.com/evanplaice/evanplaice.com . I'm planning to eventually extract the good bits, and adapt it to work with Jekyll files. Front-matter support is the last major road block. Google shouldn't ha…

You should know that your page was blank for about 20 seconds. I nearly closed it.

Try it again.

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#94

Post by EvanPlaice »

kecks wrote: post #45
afandian wrote: post #35

Earlier quoted context omitted.

You should know that your page was blank for about 20 seconds. I nearly closed it.

Took 6 seconds on a Samsung Galaxy S6, Firefox. I definitely would've closed the tab if I hadn't read this.

The combined size of the concatenated js/css files was 1.7mb before compression. Now, both combined are 366KB respectively.

The load time should be much better now.

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#95

Post by EvanPlaice »

jackmoore wrote: post #80
EvanPlaice wrote: post #10

Cool. I'm actually building something very similar @ http://evanplaice.com . I use Markdown/JSON for all of the content. Markdown files can easily be embedded in a page using the directive I wrote. The source is @ http://github.com/evanplaice/evanplaice.com . I'm planning to eventually extract the good bits, and adapt it to work with Jekyll files. Front-matter support is the last major road block. Google shouldn't ha…

I see you are getting some negative feedback, haha. I think the main problem at this point isn't due client-rendering, but the large prerequisite files. Gzipping your JavaScript would trim a MB or more. Putting the static assets on a CDN (or enabling gzip yourself) would cut the render time by 2/3rds. Semantic UI adds 700KBs of CSS, which seems like a lot more than your site should need. Even if this were a static re…

Feel free to try it again. The css and js are now merged and concatenated into one and gzipped. Total size of both is now 366KB

The time to bootstrap the app is about 1.5 seconds. There's room for improvement but I don't expect any massive gains since I can't isomorphically pre-render without a server back-end.

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#96

Post by danielovich »

inflam52 wrote: post #79
danielovich wrote: post #77

Earlier quoted context omitted.

updated that, still cannot get pages or posts to work. bummer...

ohhh I see what's going on here. since you cloned the demo, you need to use postsFolder: 'demo/posts' and pagesFolder: 'demo/pages' since they are located inside the demo folder. The demo is setup slightly different than a standard setup since it's in the subfolder.

You rock! Thank you

Re: Show HN: CMS.js – Fully Client-Side JavaScript Site Generator

#97

Post by afandian »

EvanPlaice wrote: post #93
afandian wrote: post #35

Earlier quoted context omitted.

You should know that your page was blank for about 20 seconds. I nearly closed it.

Try it again.

5 seconds browser loading. Then blank screen for about 5 seconds. Then a spinner for about 3 seconds.

No matter how much optimisation you're doing, you're still destroying the progressive loading of HTML pages and the ability for my browser to tell me how my page is loading.

It may be a fun project, but it's not based on sound technical decisions, in my humble opinion.

Post reply on HN