Skip to content
⚡️ An opinionated, zero-config static site generator.
JavaScript
Branch: master
Clone or download
dependabot-preview and brandonweiss Bump rollup from 1.26.4 to 1.26.5
Bumps [rollup](https://github.com/rollup/rollup) from 1.26.4 to 1.26.5.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v1.26.4...v1.26.5)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Latest commit 13c6e91 Nov 11, 2019

README.md


Charge

Charge

What?

Charge is an opinionated, zero-config static site generator written in JavaScript. It supports a wide variety of common uses and it does it without needing to be configured or customized. It’s fast, it’s simple, and it works the way you probably expect it to. That’s it.

Why?

Yeah, I know, another static site generator. Let me be clear, I really did not want to make a static site generator. It’s really the very last thing I wanted to do.

I went on StaticGen and looked at every JavaScript-based one. I could not find a single one that I thought was simple, well-documented, had the features I needed, was actively maintained, and was designed and worked the way I wanted. So here I am, making a static site generator.

Highlights

  • Zero configuration
  • Templating via JSX and MDX
  • React renders server-side, not client-side
  • Write futuristic JavaScript with Babel
  • Write futuristic CSS with PostCSS
  • Live-reloading development server
  • Rebuilds the minimum files necessary
  • Dynamic pages (coming soon)
  • Stellar documentation

Documentation

You can find the Charge documentation on the website.

How is Charge different from GatsbyJS?

Gatsby is really cool, but it’s very different than Charge, with two particularly large differences.

Gatsby is configuration over convention. It can be used to build complex web applications, but because of that it can be very difficult to understand how to use it. You’ll need to know how to use Webpack, which personally gives me nightmares. It’s likely that you’ll need to spend time learning other tools and then configuring and tweaking Gatsby before you can use it for your site. Charge is convention over configuration. In fact, it has no configuration, it “just works”.

Gatsby renders pages client-side. That means it serves React and some related libraries to the browser along with your components in order to render the pages. Routing also happens client-side. Gatsby can render the initial page load server-side, but there’s no way to not serve hundreds of kilobytes of JavaScript to the browser. Charge uses React to render everything server-side. It generates a truly static site.

More practically, Gatsby is great if you’re building a large, complex website and want lots of control over how you build it. Charge is probably better if you’re building a small website and don’t want to waste time fiddling with configurations and cobbling different tools together.

Real examples

If you’d like to see everything in practice, check out these sites using Charge.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/brandonweiss/charge.

License

The package is available as open source under the terms of the MIT License.

You can’t perform that action at this time.