In my previous article we discussed reasons why you could benefit from using a static site generator. To recap:
- A static site is a collection of pages contained in basic HTML files. You could hand-write these in a text editor but managing assets and repeated elements such as navigation can become problematic.
- A Content Management System stores page content in a database and provides facilities to edit and apply themes. Management becomes easier at the expense of flexibility, performance, server requirements, security and back-ups.
- A Static Site Generator is a compromise between using a hand-coded static site and a full CMS. You generate an HTML-only website using raw data (such as markdown files) and templates. The resulting build is transferred to your live server.
Popular static site generators include Jekyll, Pelican, Hugo and Metalsmith -- see StaticGen for many more options.
An SSG appears to offer the benefits of both CMS and static worlds but they will not be suitable to every project…
Continue reading %7 Reasons NOT to Use a Static Site Generator%
by Craig Buckler via SitePoint
No comments:
Post a Comment