You can now tell oranda to build multiple sites at once! By default, this will also generate a separate "root"
page, providing an index into all projects defined within your workspace.
oranda now uses a CSS version that's included in the binary it's shipped with! This means no more HTTP requests to GitHub
to fetch a CSS version over and over. As a bonus, we removed the internal dependency on a Node.js toolchain to build
the CSS in development, which should make hacking on oranda and its themes a lot easier!
In line with workspace support, oranda will now attempt to keep already downloaded versions of its CSS in-memory, which
helps tremendously when you have a lot of workspace members all using a custom CSS version.
This is a simple bug fix. Previously, we accidentally hid the body of a prerelease on its own separate changelog page
(but mysteriously, it showed up on the main changelog page when prereleases were toggled!)
Restrict parsed repo URLs to GitHub only - Plecra/pr553
Right now, we only support GitHub repository URLs to get context from. This fixed an issue where technically, oranda
would attempt to do this with GitLab URLs as well, which would cause unintended behavior.
make artifact autodetect configurable - Gankra/pr527
We now provide a new boolean key, components.artifacts.auto, that lets you explicitly
enable autodetection of artifacts. Previously, we would only enable this if you either
turned on components.artifacts.cargo_dist, or if you provided some package manager entries.
Since oranda does also support gleaning artifacts even without cargo-dist support enabled,
we added this extra switch to let you toggle it without having to mess around with package managers.
This is a breaking change, as enabling cargo-dist support or specifying package managers does
not turn on auto-detection of artifacts anymore. If you were previously relying on auto-detection, your
artifacts will no longer be displayed. To re-enable auto-detection, create a oranda.json file if you don't
already have one, and set the following configuration:
Logos set via the styles.logo option will now be properly centered/aligned in all themes,
and set to a maximum width so that a 1920x1080 logo won't be displayed in its full width and height, thus
pushing all content down below the fold.
Selecting text in the Hacker theme now applies a nice, green, high contrast highlight background
color, instead of being the same color as the text, therefore hiding the content.
Some minor fixes to bring the package manager docs up to speed with how oranda actually processes options.
Maintenance
Refactor into using minijinja templates instead of axohtml - shadows-withal/pr526
A biiig internal refactor moving us away from our previous typed-HTML-in-Rust approach of generating
HTML, towards using a proper template language (Jinja2) instead. This allows for a lot more flexibility
and separation of concerns going forward!
================ public/changelog/v0.2.0/index.html ================
oranda
make artifact autodetect configurable - Gankra/pr527
We now provide a new boolean key, components.artifacts.auto, that lets you explicitly
enable autodetection of artifacts. Previously, we would only enable this if you either
turned on components.artifacts.cargo_dist, or if you provided some package manager entries.
Since oranda does also support gleaning artifacts even without cargo-dist support enabled,
we added this extra switch to let you toggle it without having to mess around with package managers.
This is a breaking change, as enabling cargo-dist support or specifying package managers does
not turn on auto-detection of artifacts anymore. If you were previously relying on auto-detection, your
artifacts will no longer be displayed. To re-enable auto-detection, create a oranda.json file if you don't
already have one, and set the following configuration:
Logos set via the styles.logo option will now be properly centered/aligned in all themes,
and set to a maximum width so that a 1920x1080 logo won't be displayed in its full width and height, thus
pushing all content down below the fold.
Selecting text in the Hacker theme now applies a nice, green, high contrast highlight background
color, instead of being the same color as the text, therefore hiding the content.
Some minor fixes to bring the package manager docs up to speed with how oranda actually processes options.
Maintenance
Refactor into using minijinja templates instead of axohtml - shadows-withal/pr526
A biiig internal refactor moving us away from our previous typed-HTML-in-Rust approach of generating
HTML, towards using a proper template language (Jinja2) instead. This allows for a lot more flexibility
and separation of concerns going forward!
================ public/changelog/v0.3.0-prerelease.5/index.html ================
oranda
You can now tell oranda to build multiple sites at once! By default, this will also generate a separate "root"
page, providing an index into all projects defined within your workspace.
oranda now uses a CSS version that's included in the binary it's shipped with! This means no more HTTP requests to GitHub
to fetch a CSS version over and over. As a bonus, we removed the internal dependency on a Node.js toolchain to build
the CSS in development, which should make hacking on oranda and its themes a lot easier!
In line with workspace support, oranda will now attempt to keep already downloaded versions of its CSS in-memory, which
helps tremendously when you have a lot of workspace members all using a custom CSS version.
This is a simple bug fix. Previously, we accidentally hid the body of a prerelease on its own separate changelog page
(but mysteriously, it showed up on the main changelog page when prereleases were toggled!)
Restrict parsed repo URLs to GitHub only - Plecra/pr553
Right now, we only support GitHub repository URLs to get context from. This fixed an issue where technically, oranda
would attempt to do this with GitLab URLs as well, which would cause unintended behavior.
🎁 generate beautiful landing pages for your projects
oranda is an opinionated static-site generator that is designed for developers
who are publishing projects and would like a website but don't want to build
one from scratch.
oranda uses oranda so you can checkout a live example here!
Installation
To install oranda, please visit the oranda website- which is generated by
oranda!
Quickstart
# build your site
> oranda build
# start a server to checkout a local version of your built site in a browser
> oranda serve
# build your site and start a server that rebuilds on file changes
> oranda dev
Here's an animated demo:
Configuration
If you'd like to configure oranda, place an oranda.json file in the root of
your project and fill it with the configuration you'd like. Check out the docs
to learn more about your configuration options!
Installers: integrating with cargo-dist
oranda is built to work alongside cargo-dist, which is a tool that builds
distributable artifacts for your Rust applications. To tell oranda you are
using cargo-dist you can add this to your oranda.json:
"artifacts": {
"cargo_dist": true
}
This will link oranda and cargo-dist such that oranda can display your
installers and downloadable artifacts on your page.
