Publish Websites Like a BOSS B]
A static site is a website with no moving parts: no dependencies, no database, no code execution, no admin panel. This is different from a "web application" which requires many layers of software.
Publish anywhere by "compiling" your website and hosting the contents on nearly any web-host on the planet. Ruhoh also supports automatic hosting so you don't have to worry about finding or setting up a web-host.
|Git||for file management.|
|Full-Control||Multiple self-hosting options.|
|Code||No programming necessary.|
|Friendly||Accessible for beginners & experts.|
|Open Source||MIT license.|
Why a static site?
In terms of publishing textual content and images, a static site is much faster, more secure, costs less, and is highly scalable -- it won't slow to a crawl or crash due to increased traffic.
There comes a time in your life when as a creator you must create! Your technical curiousity compels you to return to the joy and freedom of using your own tools and owning your content.
You fire up your text-editor and create a masterpiece. A quick switch over to the terminal allows you to execute "publish" like some hipster techno-wizard -- lines of output race down your black terminal screen until finally you see "completed!"
You verify your website is updated, bring up Facebook, twitter, gchat, and snapchat(?), CTRL+V your domain into the appropriate boxes and you pause for three triumphant seconds before finally proclaiming...
"I made that!"
Focus on content not programming. Ruhoh is language-agnostic, it's not strictly tied to any one language so you don't need to know ruby or do any programming if you don't want to. However, it turns out to be a good way to learn.
Focus on Web Publishing and nothing else. Ruhoh prioritizes web-publishing specific optimizations like SEO-optimized permalink structures, cononical redirects, microformats, RSS/ATOM feed generation, robust internationalization, textual search, comments, and so on.
Onions Ruhoh should be immediately usable and effective for beginners and experts alike. All functionality should be intuitive and simple to uncover and learn. As your experience grows and you dive deeper into customizations, the layers of power, functionality, and extensibility should elegantly peel away from ruhoh like an onion. You don't have to use them, but they will be there.
Who should use ruhoh?
Ruhoh is built for users looking to publish content online. Publishing content is not the same as creating web apps so ruhoh is not an application framework and you don't have to be a programmer.
- Are technically curious.
- Value owning your own content.
- May be jaded by hosted solutions like Wordpress and Tumblr.
- Are probably not cool with NSA surveillance.
Knowledge of ruby is not required, but since ruby can be a pain to install, it's best if you are capable of setting up a 1.9+ ruby environment locally.
Ruhoh is pretty technical, but the goal is to be accessible and intuitive for beginners.
Beginners are welcomed and encouragd to grow with ruhoh's functionality as experience and curiousity dictates. Experts can immediately take full advantage of ruhoh's modular architecture and straightforward APIs. Nearly all features are powered by standalone "service libraries" that can be overloaded or swapped.
- Prioritize Web Publishing. Work will focus on delivering the best publishing experience and utilizing the web's latest standards for maintaining published content on the Internet.
- Language-agnostic. A language-specific workflow places focus on the tool rather than the content. Therefore ruhoh's core design and interface should be completely free from language-dependent knowledge or paradigms.
- Freely Customizable. Ruhoh provides many core features such as URL formatting, markdown rendering, tags, automatic summarization, etc. These functions should expose themselves merely as "services" that the user can override, extend, replace, or re-implement without worry.
- Obsessive Separation of Concerns
Ruhoh is designed around three principle layers of functionality which are obsessively kept separated as much as possible.
- Content Layer Text, data, and media based content; all your great writings and thoughts.
- View Layer
The programming logic that processes and connects your content to the presentation layer.
This layer is enabled by Mustache which heavily encapsulates programming logic.