Skip to content

Commit 9de6d96

Browse files
committed
docs: migrate to vuepress
1 parent 8c06b6d commit 9de6d96

File tree

11 files changed

+2781
-0
lines changed

11 files changed

+2781
-0
lines changed

docs/.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
node_modules
2+
.temp
3+
.cache

docs/docs/.vuepress/config.ts

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
import {defaultTheme, defineUserConfig} from 'vuepress'
2+
import {searchPlugin} from "@vuepress/plugin-search";
3+
4+
export default defineUserConfig({
5+
lang: 'en-US',
6+
title: ' ',
7+
description: 'A Dotfile manager written in Rust',
8+
markdown: {
9+
code: {
10+
lineNumbers: false
11+
}
12+
},
13+
head: [
14+
['link', {rel: 'icon', href: '/favicon.png'}],
15+
['meta', {name: 'theme-color', content: '#f86b6a'}],
16+
['meta', {name: 'apple-mobile-web-app-capable', content: 'yes'}],
17+
['meta', {name: 'apple-mobile-web-app-status-bar-style', content: 'black'}],
18+
['meta', {property: 'og:title', content: 'Toml Bombadil'}],
19+
['meta', {property: 'og:image', content: 'https://toml-bombadil.dev/logo.png'}],
20+
['meta', {property: 'twitter:card', content: 'https://toml-bombadil.dev/logo.png'}],
21+
['meta', {property: 'og:description', content: 'A Dotfile manager written in Rust'}],
22+
['meta', {property: 'og:width', content: '100'}],
23+
],
24+
25+
plugins: [
26+
searchPlugin({
27+
// options
28+
}),
29+
],
30+
31+
theme: defaultTheme({
32+
logo: 'logo.png',
33+
repo: 'https://github.com/cocogitto/cocogitto',
34+
docsRepo: 'https://github.com/cocogitto/website',
35+
navbar: [
36+
{
37+
link: '/quickstart/',
38+
text: 'Quickstart',
39+
},
40+
{
41+
link: '/docs/',
42+
text: 'Documentation',
43+
},
44+
{
45+
link: '/config/',
46+
text: 'Configuration reference',
47+
},
48+
],
49+
sidebar: [
50+
{
51+
link: '/quickstart/',
52+
text: 'User quickstart',
53+
},
54+
{
55+
link: '/docs/',
56+
text: 'Documentation',
57+
},
58+
{
59+
link: '/config/',
60+
text: 'Configuration reference',
61+
},
62+
],
63+
}),
64+
})
3.36 MB
Loading
28.3 KB
Loading

docs/docs/README.md

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
home: true
3+
heroImage: logo.png
4+
tagline: A Dotfile manager written in Rust
5+
actionText: Getting Started →
6+
actionLink: /quickstart/
7+
features:
8+
- title: Dotfiles Template️
9+
details: Inject variables in your dotfiles to manage your dotfile state in one place.
10+
- title: GPG encryption
11+
details: Encrypt your SSH keys, passwords, corporate configs via GPG and safely commit them to your public dotfile repository.
12+
- title: Themes and profiles
13+
details: Organize your dotfiles, switch themes and working environment on the fly.
14+
- title: Installation hooks.
15+
details: Live reload your window manager components with pre and post installation hooks.
16+
footer: MIT Licensed | Copyright © 2020 Paul Delafosse
17+
---
18+
19+
### What are dotfiles anyway?
20+
21+
If you don't know what dotfiles are, you probably want to read this.
22+
23+
24+
## Why Another dotfile manager
25+
26+
I wrote Toml Bombadil because I kept changing my desktop environment : switching from i3 to sway,
27+
from sway to xfce, from xfce to gnome and back to sway. When you keep changing your working
28+
environment like this you end up with several problems :
29+
30+
- Some symlinks will end up orphans.
31+
- Not every program you use support Xresources and you will most probably have to manually edit some themes/config.
32+
- When starting a fresh installation you will very likely need to adapt your existing dotfiles to your new machine.
33+
- It is a mess!
34+
35+
Toml Bombadil try to solve this with a simple addition to the symlink method used by other tools:
36+
instead of creating a symlink from a dotfile to the actual config path of a program, it will create
37+
a copy of it and symlink the copy. This additional step allow to use your original dotfile as a
38+
template and inject variables in the copy. You can have multiple value files in the same dotfile
39+
repository and change color scheme, or any value on the fly.
40+
While Toml Bombadil has all those features available you could start using it only to generate
41+
symlinks and templatize your dot file progressively.
42+
43+
## Installation
44+
45+
[![Packaging status](https://repology.org/badge/vertical-allrepos/toml-bombadil.svg)](https://repology.org/project/toml-bombadil/versions)
46+
47+
### Archlinux
48+
49+
```shell
50+
pacman -S toml-bombadil
51+
```
52+
53+
### Cargo
54+
55+
```shell
56+
cargo install toml-bombadil
57+
```
58+
59+
60+
## Alternatives
61+
62+
The awesome-dotfiles repo maintain a list of dotfile managers.
63+
Before writing Toml Bombadil, I was using [dotbot](https://github.com/anishathalye/dotbot), it's easy to configure and simple to use.
64+
I wanted something a bit more configurable but [chezmoi](https://www.chezmoi.io/) felt way too complicated.
65+
If you want the heavy artillery, chezmoi is probably what you are looking for.
66+
67+
68+
69+
## Contributing
70+
71+
Find out how to contribute to Toml Bombadil [-> Contributing](../contributing.md)
72+

docs/docs/config/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
TODO

docs/docs/contributing.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
## How can I help
2+
3+
Toml-bombadil is a small project but there is always something to be done, if you wish to contribute there are
4+
several ways you can help us :
5+
6+
### Finding bugs
7+
8+
Found a bug in Toml Bombadil ? Let us know by [opening an issue](https://github.com/oknozor/toml-bombadil/issues/new?assignees=oknozor&labels=bug&template=bug_report.md&title=%5BBUG%5D%5B).
9+
10+
### Writing blogposts
11+
12+
You just migrated your dotfiles to Toml Bombadil and want to share the experience ? Let us know, so we can reference your article.
13+
14+
### Working on existing issues
15+
16+
Toml Bombadil new features are grouped in a milestone for the [next version](https://github.com/oknozor/toml-bombadil/milestones).
17+
You might want to look at this first to get a grasp of want is currently going on.
18+
If you want to work on an issue, let us know by tagging [@oknozor](https://github.com/oknozor) on the comment section.
19+
We will be happy to provide guidance and respond to your questions.
20+
You might want to pick a tagged [good first issue](https://github.com/oknozor/toml-bombadil/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
21+
22+
### Write bats tests
23+
If you have spotted a bug, a great way to help us improve toml bombadil is to write a
24+
[bats](https://bats-core.readthedocs.io/en/latest/) test to reproduce it, see [HOWTO](https://github.com/oknozor/toml-bombadil/blob/main/bats-tests/HOWTO.md) for more info.
25+
26+
### Suggesting new features
27+
28+
You have an idea for a new feature ? You are welcome to open a [feature request](https://github.com/oknozor/toml-bombadil/issues/new?assignees=oknozor&labels=enhancement&template=feature_request.md&title=%5BFEATURE%5D)
29+
on the issue board.
30+
31+
### Submit a pull request
32+
33+
Toml bombadil respect the following coding standard for any code addition to the main branch :
34+
- We use [clippy](https://github.com/rust-lang/rust-clippy) to spot lints.
35+
- We enforce code formatting with [rustfmt](https://github.com/rust-lang/rustfmt).
36+
- We write test (Code coverage must never decrease when merging to the main branch).
37+
- Commit shall respect the [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) specification
38+
39+
You have picked an issue and started to work on your fork. Time to make a pull request !
40+
If your issue is referenced in the next version milestone, you are expected to submit a pull request to the corresponding
41+
version branch (following semver format and prefixed by "v", ex : "v2.0.0-rc").
42+
If your issue is a bug fix you can submit your PR to main directly and increase the minor version.
43+
44+

0 commit comments

Comments
 (0)