Skip to content

Commit 890b3e0

Browse files
committed
feat: add projects and cross-link xvowl
1 parent b5c9fe9 commit 890b3e0

File tree

6 files changed

+511
-8
lines changed

6 files changed

+511
-8
lines changed

content/posts/blog-post-1.md

Lines changed: 257 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,257 @@
1+
---
2+
title: "Blog Post 1"
3+
date: 2022-06-18T11:10:36+08:00
4+
draft: false
5+
language: en
6+
featured_image: ../assets/images/featured/featured-img-placeholder.png
7+
summary: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed cursus, odio nec venenatis lacinia, lacus lectus varius nisi, in tristique mi purus ut libero.
8+
description: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed cursus, odio nec venenatis lacinia, lacus lectus varius nisi, in tristique mi purus ut libero. Vestibulum vel convallis felis. Ut finibus lorem vestibulum lobortis rhoncus.
9+
author: TailBliss
10+
authorimage: ../assets/images/global/author.webp
11+
categories: Blog
12+
tags: Blog
13+
---
14+
__Advertisement :smile:__
15+
16+
- __[pica](https://nodeca.github.io/pica/demo/)__ - high quality and fast image
17+
resize in browser.
18+
- __[babelfish](https://github.com/nodeca/babelfish/)__ - developer friendly
19+
i18n with plurals support and easy syntax.
20+
21+
You will like those projects!
22+
23+
---
24+
25+
# h1 Heading :blush:
26+
## h2 Heading
27+
### h3 Heading
28+
#### h4 Heading
29+
##### h5 Heading
30+
###### h6 Heading
31+
32+
33+
## Horizontal Rules
34+
35+
***
36+
37+
---
38+
39+
___
40+
41+
42+
## Typographic replacements
43+
44+
Enable typographer option to see result.
45+
46+
(c) (C) (r) (R) (tm) (TM) (p) (P) +-
47+
48+
test.. test... test..... test?..... test!....
49+
50+
!!!!!! ???? ,, -- ---
51+
52+
"Smartypants, double quotes" and 'single quotes'
53+
54+
55+
## Emphasis
56+
57+
**This is bold text**
58+
59+
__This is bold text__
60+
61+
*This is italic text*
62+
63+
_This is italic text_
64+
65+
~~Strikethrough~~
66+
67+
68+
## Blockquotes
69+
70+
71+
> Blockquotes can also be nested...
72+
>> ...by using additional greater-than signs right next to each other...
73+
> > > ...or with spaces between arrows.
74+
75+
76+
## Lists
77+
78+
Unordered
79+
80+
+ Create a list by starting a line with `+`, `-`, or `*`
81+
+ Sub-lists are made by indenting 2 spaces:
82+
- Marker character change forces new list start:
83+
* Ac tristique libero volutpat at
84+
+ Facilisis in pretium nisl aliquet
85+
- Nulla volutpat aliquam velit
86+
+ Very easy!
87+
88+
Ordered
89+
90+
1. Lorem ipsum dolor sit amet
91+
2. Consectetur adipiscing elit
92+
3. Integer molestie lorem at massa
93+
94+
95+
1. You can use sequential numbers...
96+
1. ...or keep all the numbers as `1.`
97+
98+
Start numbering with offset:
99+
100+
57. foo
101+
1. bar
102+
103+
104+
## Code
105+
106+
Inline `code`
107+
108+
Indented code
109+
110+
// Some comments
111+
line 1 of code
112+
line 2 of code
113+
line 3 of code
114+
115+
116+
Block code "fences"
117+
118+
```
119+
Sample text here...
120+
```
121+
122+
Syntax highlighting
123+
124+
``` js
125+
var foo = function (bar) {
126+
return bar++;
127+
};
128+
129+
console.log(foo(5));
130+
```
131+
132+
## Tables
133+
134+
| Option | Description |
135+
| ------ | ------------------------------------------------------------------------- |
136+
| data | path to data files to supply the data that will be passed into templates. |
137+
| engine | engine to be used for processing templates. Handlebars is the default. |
138+
| ext | extension to be used for dest files. |
139+
140+
Right aligned columns
141+
142+
| Option | Description |
143+
| -----: | ------------------------------------------------------------------------: |
144+
| data | path to data files to supply the data that will be passed into templates. |
145+
| engine | engine to be used for processing templates. Handlebars is the default. |
146+
| ext | extension to be used for dest files. |
147+
148+
149+
## Links
150+
151+
[link text](http://dev.nodeca.com)
152+
153+
[link with title](http://nodeca.github.io/pica/demo/ "title text!")
154+
155+
Autoconverted link https://github.com/nodeca/pica (enable linkify to see)
156+
157+
158+
## Images
159+
160+
![Minion](https://octodex.github.com/images/minion.png)
161+
![Stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat")
162+
163+
Like links, Images also have a footnote style syntax
164+
165+
![Alt text][id]
166+
167+
With a reference later in the document defining the URL location:
168+
169+
[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
170+
171+
172+
## Plugins
173+
174+
The killer feature of `markdown-it` is very effective support of
175+
[syntax plugins](https://www.npmjs.org/browse/keyword/markdown-it-plugin).
176+
177+
178+
### [Emojies](https://github.com/markdown-it/markdown-it-emoji)
179+
180+
> Classic markup: :wink: :crush: :cry: :tear: :laughing: :yum:
181+
>
182+
> Shortcuts (emoticons): :-) :-( 8-) ;)
183+
184+
see [how to change output](https://github.com/markdown-it/markdown-it-emoji#change-output) with twemoji.
185+
186+
187+
### [Subscript](https://github.com/markdown-it/markdown-it-sub) / [Superscript](https://github.com/markdown-it/markdown-it-sup)
188+
189+
- X^2^
190+
- H~2~O
191+
192+
193+
### [\<ins>](https://github.com/markdown-it/markdown-it-ins)
194+
195+
++Inserted text++
196+
197+
198+
### [\<mark>](https://github.com/markdown-it/markdown-it-mark)
199+
200+
==Marked text==
201+
202+
203+
### [Footnotes](https://github.com/markdown-it/markdown-it-footnote)
204+
205+
Footnote 1 link[^first].
206+
207+
Footnote 2 link[^second].
208+
209+
Inline footnote^[Text of inline footnote] definition.
210+
211+
Duplicated footnote reference[^second].
212+
213+
[^first]: Footnote **can have markup**
214+
215+
and multiple paragraphs.
216+
217+
[^second]: Footnote text.
218+
219+
220+
### [Definition lists](https://github.com/markdown-it/markdown-it-deflist)
221+
222+
Term 1
223+
224+
: Definition 1
225+
with lazy continuation.
226+
227+
Term 2 with *inline markup*
228+
229+
: Definition 2
230+
231+
{ some code, part of Definition 2 }
232+
233+
Third paragraph of definition 2.
234+
235+
_Compact style:_
236+
237+
Term 1
238+
~ Definition 1
239+
240+
Term 2
241+
~ Definition 2a
242+
~ Definition 2b
243+
244+
245+
### [Abbreviations](https://github.com/markdown-it/markdown-it-abbr)
246+
247+
This is HTML abbreviation example.
248+
249+
It converts "HTML", but keep intact partial entries like "xxxHTMLyyy" and so on.
250+
251+
*[HTML]: Hyper Text Markup Language
252+
253+
### [Custom containers](https://github.com/markdown-it/markdown-it-container)
254+
255+
::: warning
256+
*here be dragons*
257+
:::

content/projects/configarr.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: "Introducing Configarr: Streamlining Configuration Management for Sonarr and Radarr"
3+
date: 2024-08-01T09:00:00+01:00
4+
draft: false
5+
language: en
6+
featured_image: ../assets/images/featured/configarr-banner.png
7+
page_link: https://github.com/raydak-labs/configarr
8+
summary: Discover Configarr, a powerful tool for synchronizing configurations between Sonarr, Radarr, and TRaSH Guides, simplifying media server management.
9+
description: Learn about Configarr, an open-source project that automates the process of keeping your Sonarr and Radarr configurations in sync with TRaSH Guides and custom settings, enhancing your media server setup.
10+
author: raydak
11+
authorimage: ../assets/images/global/author.webp
12+
tags: [
13+
"configarr",
14+
"sonarr",
15+
"radarr",
16+
]
17+
categories: [
18+
"tools",
19+
"media-management",
20+
]
21+
---
22+
23+
In the world of media server management, keeping your configurations up-to-date and consistent can be a challenging task. Today, we're excited to introduce Configarr, a powerful tool designed to simplify this process for Sonarr and Radarr users.
24+
25+
## What is Configarr?
26+
27+
Configarr is an open-source configuration and synchronization tool specifically created for Sonarr and Radarr, two popular media management applications. It aims to streamline the process of maintaining and updating configurations, custom formats, and quality profiles across your media server setup[8].
28+
29+
## Key Features
30+
31+
Configarr offers a range of features that make it stand out:
32+
33+
1. **TRaSH Guides Integration**: Easily sync custom formats and settings from the popular TRaSH Guides directly into your Sonarr and Radarr instances[8].
34+
35+
2. **Custom Format Support**: In addition to TRaSH Guides, Configarr allows you to include your own defined custom formats, giving you more flexibility in managing your media library[8].
36+
37+
3. **Multiple Configuration Sources**: Configarr supports syncing from TRaSH Guides, local files, and configurations defined directly in the tool's config file[8].
38+
39+
4. **Flexible Deployment Options**: Run Configarr using Docker, docker-compose, or even as a Kubernetes CronJob for regular synchronization[8].
40+
41+
5. **Compatibility**: Currently supports Sonarr v4 and Radarr v4, ensuring you're working with the latest versions of these applications[8].
42+
43+
## Why Use Configarr?
44+
45+
Managing media servers can be time-consuming, especially when it comes to keeping up with best practices and optimal configurations. Configarr addresses this by:
46+
47+
- **Automating Updates**: Stay current with the latest recommended settings from TRaSH Guides without manual intervention.
48+
- **Enhancing Consistency**: Ensure all your instances are configured identically, reducing discrepancies and potential issues.
49+
- **Saving Time**: Spend less time on configuration management and more time enjoying your media library.
50+
51+
## Getting Started
52+
53+
To start using Configarr, you'll need a few things:
54+
55+
1. A `config.yml` file to define your synchronization settings.
56+
2. A `secrets.yml` file for storing sensitive information like API keys.
57+
3. Optionally, custom format definitions in local files or within your config.
58+
59+
For a detailed setup guide and examples, visit the [Configarr GitHub repository](https://github.com/raydak-labs/configarr).
60+
61+
## Community and Contributions
62+
63+
Configarr is an open-source project, and we welcome contributions from the community. Whether you're interested in adding new features, improving documentation, or reporting bugs, your input is valuable in making Configarr even better.
64+
65+
## Conclusion
66+
67+
Configarr represents a significant step forward in simplifying media server management. By bridging the gap between Sonarr, Radarr, and community-driven configuration guides, it offers a streamlined solution for maintaining optimal settings. Give Configarr a try and experience the benefits of automated configuration management for your media server setup.
68+
69+
For more information and to get started with Configarr, visit the [official GitHub repository](https://github.com/raydak-labs/configarr).
70+
71+
Happy media managing!

content/projects/xvowl.md

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
author: "raydak"
3+
title: "xVOWL: Advancing Ontology Visualization"
4+
date: "2024-09-08"
5+
summary: "Exploring xVOWL, an innovative project aimed at enhancing ontology visualization techniques beyond WebVOWL and LDVOWL."
6+
page_link: "https://xvowl.raydak.de"
7+
tags: [
8+
"xvowl",
9+
"ontology",
10+
"visualization"
11+
]
12+
categories: [
13+
"Semantic Web",
14+
"Data Visualization",
15+
"Project Development"
16+
]
17+
series: ["Ontology Visualization Tools"]
18+
featured_image: "../noimage"
19+
---
20+
21+
In the ever-evolving landscape of semantic web technologies, ontology visualization plays a crucial role in making complex data structures more accessible and understandable. Today, we're excited to introduce xVOWL, our cutting-edge project that aims to push the boundaries of ontology visualization beyond the capabilities of existing tools like WebVOWL and LDVOWL.
22+
23+
## What is xVOWL?
24+
25+
xVOWL is an innovative project currently under evaluation and development at [xvowl.raydak.de](https://xvowl.raydak.de). Our goal is to create a more powerful and intuitive visualization tool for ontologies, building upon the foundations laid by its predecessors.
26+
27+
## The Evolution of Ontology Visualization
28+
29+
### WebVOWL
30+
31+
WebVOWL, a web-based visualization of ontologies, has been a significant player in this field. It implements the Visual Notation for OWL Ontologies (VOWL) and is based on open web standards[4]. WebVOWL automatically generates visualizations from JSON files, making it a versatile tool for ontology representation[4].
32+
33+
### LDVOWL
34+
35+
While not as widely known as WebVOWL, LDVOWL has also contributed to the advancement of ontology visualization techniques. It builds upon the concepts introduced by WebVOWL, offering its own unique features and improvements.
36+
37+
## xVOWL: The Next Step
38+
39+
xVOWL aims to address limitations in existing tools and introduce new features that enhance the user experience and functionality of ontology visualization. Some key areas we're focusing on include:
40+
41+
1. **Improved Performance**: Handling larger and more complex ontologies with smoother rendering and interaction.
42+
2. **Enhanced Customization**: Offering more options for users to tailor the visualization to their specific needs.
43+
3. **Advanced Filtering**: Implementing sophisticated filtering mechanisms to focus on relevant parts of the ontology.
44+
4. **Interactive Exploration**: Developing more intuitive ways to navigate and explore ontological relationships.
45+
46+
## Current Status and Future Directions
47+
48+
As xVOWL is still in the evaluation and development phase, we're actively working on refining our concepts and implementing core features. We're drawing inspiration from the success of WebVOWL, which has been widely adopted and even integrated into various applications and frameworks[5].
49+
50+
Our team is committed to creating a tool that not only visualizes ontologies but also aids in their understanding and analysis. We believe that by improving upon existing visualization techniques, xVOWL can become an invaluable asset for semantic web developers, researchers, and enthusiasts alike.
51+
52+
## Get Involved
53+
54+
We invite the community to follow our progress and contribute to the development of xVOWL. Visit our project page at [xvowl.raydak.de](https://xvowl.raydak.de) for the latest updates, documentation, and ways to get involved.
55+
56+
As we continue to develop xVOWL, we're excited about the potential impact it could have on the field of ontology visualization. Stay tuned for more updates as we work towards revolutionizing how we interact with and understand complex ontological structures.
57+
58+

0 commit comments

Comments
 (0)