# Presenting Hyperorg version 0.1.0: The Org to HTML Converter

**URL:** <https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396>\
**Category:** Meta\
**Created:** [March 19, 2024, 9:10am UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396 "2024-03-19T09:10:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![buhtz](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@buhtz](https://org-roam.discourse.group/u/buhtz)\
**Post date:** [March 19, 2024, 9:10am UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/1 "2024-03-19T09:10:18Z")

</div>

I am excited to introduce [Hyperorg 0.1.0](https://codeberg.org/buhtz/hyperorg), designed to efficiently convert files from Emacs Org-mode and Org-roam into clean HTML files. Ideal for Zettelkasten enthusiasts and personal wiki creators, Hyperorg simplifies the conversion process, ensuring your nodes correctly interlinked and accurately transformed into HTML format.

Key Features:

- Converts Emacs Org-mode and Org-roam files to pure HTML5 and CSS.
- Tailored for Zettelkasten and personal wiki use cases.
- Written in Python3.

Visit the project website for clear [installation instructions](https://codeberg.org/buhtz/hyperorg#installation).

Have questions, feature ideas, or encountered any bugs? I appreciate your feed back and do work now on the issues for the next release.

Best regards  
Christian Buhtz

---

<div class="post-metadata">

**Author:** ![WAKA](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/waka/32/668_2.png) [@WAKA](https://org-roam.discourse.group/u/WAKA)\
**Post date:** [March 19, 2024, 11:57am UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/2 "2024-03-19T11:57:27Z")

</div>

> [@buhtz](#):
>
> Christian

Dear Mr. Christian Buhtz,  
Thank you for delivering hyperorg with its wonderful compilation features.  
May I ask you a question?  
Automatically set the name of Org Folder XXX as the destination folder.  
Isn’t there a function to complete with “html-xxx”?  
However, assume that the file path is set to the same location.  
Sincerely, WAKAMATSU(from Japan)

---

<div class="post-metadata">

**Author:** ![buhtz](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@buhtz](https://org-roam.discourse.group/u/buhtz)\
**Post date:** [March 19, 2024, 1:49pm UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/3 "2024-03-19T13:49:44Z")

</div>

Waka-san,  
thank you very much for your feedback and your kind words.

Let me rephrase your suggested feature to be sure that I understand it correct.

You want to specify only the input folder like this?

```
$ hyperorg ~/org-folder

```

And the resulting output should be in `~/html-org-folder` ?

---

<div class="post-metadata">

**Author:** ![WAKA](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/waka/32/668_2.png) [@WAKA](https://org-roam.discourse.group/u/WAKA)\
**Post date:** [March 20, 2024, 1:39am UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/4 "2024-03-20T01:39:38Z")

</div>

Dear buhtz,

Thanks for your e-mail.

Is it possible to complete with a terminal command like this?

The first command input is the org folder I want to convert.

When I write the name and location specification, the folder name of the HTML

which I want to convert will be automatically completed.

The hyperorg command is executed on the completed html folder name

and an html file is created.

I thought that the destination html folder name would be unified.

So I wouldn’t have to worry about the storage location and name.

I believe that the hyperorg you type will be appended

with additional characters for options.

For example, a statement like

$ hyperorg +n ~/org-folder

Yours, WAKAMATSU

---

<div class="post-metadata">

**Author:** ![buhtz](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@buhtz](https://org-roam.discourse.group/u/buhtz)\
**Post date:** [March 20, 2024, 7:15am UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/5 "2024-03-20T07:15:38Z")

</div>

Dear Wakamatsu,  
thanks for your reply.

> I believe that the hyperorg you type will be appended  
> with additional characters for options.  
> For example, a statement like  
> $ hyperorg +n ~/org-folder

I like the idea to make the “outputdir” argument optional.  
But I don’t like the “+n” thing. Here again you will need two arguments. This is kind of unusual behavior not all users are suited on.

I opened a ticket for that feature:  
[#119 - Feat: Optional “outputdir” argument - buhtz/hyperorg - Codeberg.org](https://codeberg.org/buhtz/hyperorg/issues/119)

---

<div class="post-metadata">

**Author:** ![akashp](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/akashp/32/1383_2.png) [@akashp](https://org-roam.discourse.group/u/akashp)\
**Post date:** [March 21, 2024, 8:38am UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/6 "2024-03-21T08:38:30Z")

</div>

Thank you very much for writing this - this tool will be of great use to convert roam files into exported documents. I will try it out in the future; saving it to reference later.

---

<div class="post-metadata">

**Author:** ![buhtz](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@buhtz](https://org-roam.discourse.group/u/buhtz)\
**Post date:** [March 22, 2024, 2:31pm UTC](https://org-roam.discourse.group/t/presenting-hyperorg-version-0-1-0-the-org-to-html-converter/3396/7 "2024-03-22T14:31:05Z")

</div>

After some requests I added a section trying to describe [the benefits of Hyperorg compared to similar tools](https://codeberg.org/buhtz/hyperorg#benefits-compared-to-similar-tools). Feedback and discussion welcome.
