A plugin to export pages in Logseq to Hugo.

In Logseq:

Exported md:

Illustration of Logseq's implemented task states:

- [Discoed Link](https://discord.com/channels/725182569297215569/725182570131751005/952564162792402976)

![logseq_implemented_task_states](https://raw.githubusercontent.com/charleschiu2012/image-hosting/main/img/logseq_implemented_task_states.png){:height 290, :width 1216}

---

In Hugo:

Problem: The regex pattern in the export script is only looking for adminitions terminated by a newline character. This does not work if the adminition extends over several lines.

Solution: Included newlines in the regex, excluded newlines from the pattern where they're not needed and terminated the search pattern by the string #+END_. Hope this works for all cases.

Problem: Data in Logseq: test 1/page 1 -> has link to page 2 [[test 2/page 2]] test 2/page 2 -> has link to page 1 [[test 1/page 1]]

Export with the plugin to Markdown: content/pages/test 1/page 1.md -> link to {{< ref "test 2/page 2" >}} -> not working! content/pages/test 2/page 2.md -> link to {{< ref "test 1/page 1" >}} -> not working!

Solution: Add /page/ before each page link; {{< ref "/page/test 2/page 2" >}

Hi, I would really love to see a demo of this project, however, If you click the "view demo" link, it doesn't really take you to a demo site, it only loops you back to the same github repo page.

Currently all exported markdown is placed into the “pages” folder. Although it works fine this way, it would be nice to have a setting to allow us to choose the destination folder. For example, I’d like to place the exported markdown in a folder called “notes”.

As noted in #29, I make use of Logseq's built-in hierarchy functionality, where creating a page like [[Mr Color/GX/3 Red]] creates a new page nested underneath parent pages. In this case, [[Mr Color]], [[Mr Color/GX]], and finally [[Mr Color/GX/3 Red]]. If the parent pages do not exist,they are added to the graph automatically, analogous to mkdir -p mr-color/gx/3-red.

Additionally, the generated pages are aware of their hierarchies:

• parents know about their children, and list them
• children know their path, and list it

Parent:

(Grand) child:

Schrodinger already creates these pages, but they lose awareness of their hierarchy links. It would be useful for these to be surfaceable in a published site link backlinks. Unfortunately, because they are not links present in the content, they do not get generated, and would require new work to do so.

Could these be added to page front matter? Maybe

# Mr Color
hierarchy:
  - {{ ref . "pages/mr-color/gx" }}
  - {{ ref . "pages/mr-color/gx/3-red" }}
  - {{ ref . "pages/mr-color/gx/1-white" }}
  - {{ ref . "pages/mr-color/surfacer" }}
  - {{ ref . "pages/mr-color/surfacer/500" }}

# Mr Color/GX
hierarchy:
  - {{ ref . "pages/mr-color/gx/3-red" }}
  - {{ ref . "pages/mr-color/gx/1-white" }}

# Mr Color/GX/1 White
hierarchy:
  - {{ ref . "pages/mr-color/gx" }}

I've been trying to get this set up, and every time I try to export the pages to Hugo nothing was happening.

I have the :publishing/all-pages-public? true setting configured in Logseq.

I tried setting one single page to public:: true, and then export, and finally got the destination dialog.

In my case, all pages in Logseq should be presumed public unless explicitly specified public:: false, since I'm using it as a topic-specific blogging tool, and I'd prefer not to have to remember to set all pages to public:: true, especially since I hierarchically nest pages in some cases, using the upper nodes of the hierarchy just as aggregation points. Eg:

• [[Mr Color/GX 3 Red]]
• [[Mr Color/Surfacer/500]]
• [[Mr Color/Surfacer/1000 Mahogany]]

In these cases, [[Mr Color]] and [[Mr Color/Surfacer]] don't need full pages of their own--they're useful primarily as catalogs of their child pages. I do this a lot (also for dates), so having to go through and edit each of these upper nodes would be tedious.

1. I use the table of content plugin in logseq. Let me think that is possible to put the plugin function into the hugosite.

2. On the other hand,the hugo site has some function that is similar to logseq-plugin. Maybe we can let it replace automatically.

For example:

• https://adityatelange.github.io/hugo-PaperMod/posts/papermod/papermod-features/#show-table-of-contents-toc-on-blog-post

Hello!

Would it be possible to make tweet embeds work like the YouTube video embeds?

Also, related: For the YouTube embeds, I see in the code that it is prompted by {{youtube insertidhere}}, but the embed in Logseq defaults to {{video insertidhere}}. Would you be able to change it so either works?

Thanks!