I tried also if my suggestion from the initial issue post to make the Table of Contents from your other plugin https://github.com/sethyuan/logseq-plugin-tocgen work to jump to anchors in the same HTML. see Note on TOCs: https://github.com/sethyuan/logseq-plugin-doc/issues/20

• It seems that the document export does not render those links in any way.
• In the preview in Logseq the links are working by opening the block in a new view limited to the block.
• The action sems to be executed by Javascript, not any HTML Link machinery.

It would be good to know if fixing the TOC challenge would be be fine here in the DOC plugin or better solved in the https://github.com/sethyuan/logseq-plugin-tocgen.

When solved there the Target Anchors could be opened in the same HTML only if anchors are included in the html. Otherwise the links can just point to the block itself in Logseq and opens in the app as well.

Feel free to ask if something is unclear.

I'd like to give my exported page to others and since they don't have access to my graph, I'd like to be able to disable the links to other pages of my graph.

Hi, thank you for making this plugin. It has been really helpful viewing my pages.

I have a question about export. I am using logseq latest version (version 0.7.9). When I click the export button it doesn't do anything, no pop-up windows. I am using manjaro, in case os will make something different. What do you think the issue might be? Thanks!

When the doc is being exported to HTML, the text for equation is not getting rendered properly.

For example, the text $m_ee^2c$ is being rendered as shown in the attached screenshot. You can see that is first shows the equation in correct form, but then it is followed by the equation text again.

因为用的主题一直都是yoyurec大佬开发的主题，非常美观大气，然后前段时间导出是可以带着主题样式一起导出，也就是在logseq上是什么样式就导出什么样式，后来因为插件不断优化，这个功能就变糟糕了，为此我向yoyurec大佬反映过，然后他向您提出请求你合并后，其效果也没有回到之前，想问下，这个功能可以有嘛，非常喜欢导出时保留在logseq上所选择的主题样式，目前情况如下

logseq上 导出时

一直很喜欢你的插件，很棒，yoyurec大佬的主题我也很喜欢，都想要保留

Theme developers can adjust styles for exported version of pages. B'cose just using existing .kef-doc (<div id="app-container" class="kef-doc"> ) also applied in preview can broke their theme.

The #.ul works already great and the #.ol and #.ol-nested from the https://github.com/sethyuan/logseq-plugin-ol plugin as well.

A similar #.ul-nested would help to simplify the markup of deeply nested lists by adding it just to the top level.

Since it is not directly related to the other plugin, I post it here.

The HTML source contains block ids for tags and named pages. When hovering the browser (Chrome) recognizes the link but does not complete a useful clickable URL.

Files printed to PDF from the browser, look nice but contain no remaining link references

It is possible to either

1. enrich the html to get full fledged Logseq links of the form logseq://graph/my-pkm?block-id=62cd38e0-5071-4bb0-8531-4a3c00012345 for tags?
2. add a javascript to enhance the links in the browser to achieve this.

Options:

• Limit to links inside of the export (useful for Tocs, Security)

Actually the full fledged Logseq Export does some parts this, but the boilerplate is overkill for just one document. I like your HTML to easily render to PDF.

This is just a suggestion. I need to dive deeper to find out if there is a chance to add it myself.

While in the view for doc mode, the bullet lines aren't going away fully in the latest version of logseq. Issue is stemming from the latest feature for clicking the lines to collapse and expand bullets.

this is how my note looks like in the exported html file

This is the printed pdf file (using Ctrl P on Google Chrome)

The bullet point is visible in the exported html file but not in the printed pdf file.

The indentation helps a lot in recognizing the hierarchy. But having a bullet point would help a bit more in recognizing the indentation level. Don't know if you could make it happen somehow?

When exporting HTML, if page contains images, the exported paths reference original image locations. I would expect to images be either embed into HTML document or exported to some assets directory for easy sharing.

I really like this plug-in you developed. It has been about two months since I started using it. It has brought me a lot of convenience. I just don’t know if it is possible to add the generated directory when exporting function is used