9d31f650da
bb15e9804 Update index.md (#1339) ffb2f21d1 Update index.md fc154ac02 Regenerate CLI docs a0a687738 Update index.md d0e35a844 Update index.md 86d0cc042 Update index.md bdaf7e022 Release 0.81.0 b51017445 releaser: Add release notes to /docs for release of 0.81.0 888dd8fcc docs: Regen CLI docs 8c3e8b270 docs: Regen docs helper 79e3e1ebc Merge commit 'acb9109df778fa4a51c0d8b29b3212b12988908f' 31f70af7e modules: Add config option modules.vendorClosest 2631df94e markup/goldmark: Add attributes support for blocks (tables etc.) 19dee04ad Update to Dart Sass Protocol beta6 e507721fe Refactor: Write to stdout by default d204bf160 Refactor: Remove powershell support 91bea48f5 Feat: Add zsh, fish and powershell completion support 9c915ea27 docs: Remove mention of a file size limit for readFile 5acc8b6c7 js: Add Inject config option 45321989e js: Add Shims option git-subtree-dir: docs git-subtree-split: bb15e9804ae56da41f3bdb361adc14f8711fc19d
2.3 KiB
| title | date | description | siteURL | byline |
|---|---|---|---|---|
| Aether | 2020-02-26 | Showcase: "Hugo is not just a static site generator for us, it's the core framework at the heart of our entire web front-end." | https://getaether.net | [Burak Nehbit](https://twitter.com/nehbit), Maintainer, Aether |
To say that this website, our main online presence, needed to do a lot would be an understatement.
Our site is home to both Aether and Aether Pro, our knowledgebase for each product, a server for static assets that we use in our emails, the interactive sign-up flows, payments client, downloads provider, and even a mechanism for delivering auto-update notifications to our native clients. We are using a single Hugo site for all these — it's not a static site generator for us, it's the core framework at the heart of our entire web front-end.
Not only that, this had to work with one developer crunched for time who spends most of his time working on two separate apps across 3 desktop platforms — someone whose main job is very far from building static websites. We only had scraps of time to design and build this Hugo site, make it performant and scalable, and Hugo did a phenomenal job delivering on that promise.
The last piece is, funnily enough, moving our blog to Hugo, which it is not as of now. This was an inherited mistake we are currently rectifying. Soon, our entire web footprint will be living in Hugo.
Structure
Our website is built in such a way that there is a separate Vue.js instance for each of the contexts since we are not using JS-based single-page navigation. We use Hugo for navigation and to build most pages. For the pages we need to make interactive, we use Vue.js to build individual, self-contained single-page Javascript apps. One such example is our sign-up flow at aether.app, an individual Vue app living within a Hugo page, with its own JS-based navigation.
This is a relatively complex setup, and somewhat out of the ordinary. Yet, even with this custom setup, using Hugo was painless.
Tools
CMS: Hugo
Theme: Custom-designed
Hosting: Netlify, pushed to production via git push.
Javascript runtime: Vue.js