Plugin to support Digital Garden form of blogging.

[viaahmed]

Digital Gardening is a form of blogging. It is rage now-a-days.

Highlight of such blogging is wiki-linking. Click to know what exactly are Digital Gardens

People use tools like Roam Research, Obsidian, Notion, Foam for VS Code, Custom Made Solutions for spinning such gardens

It would be great if you consider this in @GetPublii

Thanks

[viaahmed]

It would be great if you go over to Obsidian to check how other tools has a variation of the feature @GetPublii provides but not open source.

Actually a great number of Obsidian users want an open source alternative to Obsidian publish.

[JOduMonT]

The first time I heard about digital garden was related to https://indieweb.org/principles and how to interconnect WordPress At the end it seems you request the webmention function, which is to ping others directly from our site. By hosting your Publii on Netlify It would be easily possible by activating this plugin: https://github.com/CodeFoodPixels/netlify-plugin-webmentions#readme but obviously not necessarily universal with others possible hosts.

[viaahmed]

Oh, I think you misunderstood me, I just wanted that it would be nice if @GetPublii could turn an Obsidian Vault to a Static Site.

Answer to "Why such Plugin?"

Publii could be the world's first free and opensource no-code solution for Digital Gardening if such plugin is implemented. It would compete with these solutions. Btw, Dendron is not really a no-code solution.

[viaahmed]

Why Publii should take interest in supporting for Obsidian Vault?

Down below I tried to collate some args.

• [x] Obsidian and Publii are both Desktop based Offline Apps.
• [x] Publii will get a readymade user base. Obsidian has an exciting and enthusiastic community.
• [x] Both are built to be extensible and customizable.
• [X] Both will complement each other.

[viaahmed]

Growth Strategy For @GetPublii : My open source contribution.

I am a Business Management Student, I am not a programmer. I am impressed with Publii, and I want to contribute in my way. I thought of strategies by which Publii may increase its user base in short time. I respect the road-map planned by the contributing members, and these ideas are not at all against the roadmap planned for 2021.

Strategy 1: Horizontal Integration

• Under this, Publii could build a out of the box full featured CMS for Digital Gardening as a fork of exisiting Publii or as part of same app.
• As per this, Publii will be free to design its own syntax (just like how Roam, Obsidian, Bear and several others have their own variations in syntax).
• This would require users to import their existing Digital Gardens into Publii's proprietary format of syntaxing (if in case it is all different).

Strategy 2: Backward Integration

• Under this strategy, Publii can gradually support every form of Data Input and do the old good job of weaving a static site.

• In my opinion, we can start from providing support for Obsidian Vaults (it is just a directory of markdown files) and later extend it to Roam DB, then Notion (if possible), then Jekyll/Hugo/Gatsby implementation of Digital Gardens.

• Here, we have look into each App's unique requirements for making plugins. However, If Publii gets a rich API and extensibility via Plugin's (this is what Obsidian has done), then users themselves will make plugins for their respective Apps.

• The users will at advantage in this strategy because they don't need to switch to Publii, since they can keep using their choice of App. They just need to pass their Input through Publii CMS and voila! a site to publish is ready.

*(these would be nothing but markdown files, and thus just require a simple import mechanism)

Conclusion

I recommend the Strategy 2. It is better. It don't deviate from existing road map as well as brings in a happy user base.

cc: @dziudek

[dziudek]

Hi,

I think that integrating with 3rd party API/data format will be very time consuming and at this moment (this year) it is out of our possibilities.

But as the idea of digital gardens is not sticky to a specific service I suppose that we will gradually add features which will allow Publii users to use it as own digital garden - as in a basic usage it is just good old blogs but maintained in a different way.

So adding features like: synced blocks, more digital-garden friendly blocks to our block editor, custom post types, some themes which will focus on such way of storing data will be enough at this moment and should easily fill the gap between blogging and digital gardens in the long-term future :)

[viaahmed]

Thanks for the reply 🙂 I actually meant that you could make Publii's API approachable enough that users of respective apps may build plugins to convert their databases into Publii websites.

Please don't forget the wiki-links in markdown editor! Since many users use the markdown editor for gardening. Other features like inline hash-tagging, link references etc are will make it a real gardening tool. Thanks again for taking consideration.

[StoltHD]

I actually don't think you even need to support/sync with any "API", but what's needed is that Publii support the same syntax' as e.g. Obsidian in the markdown, so that the markdown notes/files that users of i.e. Obsidian or Foam (or Zettlr) can be used directly from Publii to generate a static website not based on Github or other services heavily based on development/coding knowledge.

Of course it would be great if Publii could support functions and features that 3rd party plugins for i.e. Obsidian gives, for example a way to show a network graph view online, or visualize all the different charts and graphs that can be visualized in the Notes (in block code style etc.) in Obsidian because of all the plugins that users have developed.

But I think the most important thing for many people that are not developers or coders is to be able to publish their notes or writings without the need of writing a lot of script code...

Something as simple as supporting piped wiki links the way Obsidian and Foam use it with the link first and alias after the pipe character.

I know I am looking for a software that I can run on my own computer, not being online, but be able to publish some research to my own domain website when I want to, and not being depended on Github or other similar services.

So I support @viaahmed in this question... it would really be great.. I am not a developer, so I do not know how to do something like that or even how much work it would be, but I would be forever grateful if I found a software that gave me an easy way to publish some of the research notes I have created in Obsidian and Foam...

I just found Publii, so I have not tested it yet, but it will be downloaded and tested as soon as I have typed the last character in this comment :-)

---

I think that if you allow it, multiple of the plugin developers of plugins to Obsidian and VS Code/Foam will jump in and create port some of their plugins for Publii to...

[quesada]

Amazing opportunity to seize a large market of obsidian users who want a public site but won't pay for 'obsidian publish' nor deal with setting up a SSG. My 2c

[ih8snow]

You don't need to work with an API for this idea. The main challenge is to understand and convert the Obsidian markdown version into one that Publii can handle. That would i.e. help to export a folder of markdown files into a static local website, with working links etc.

[viaahmed]

Yeah this is also right

On Tue, 21 Jun, 2022, 9:57 am Jörn, @.***> wrote:

You don't need to work with an API for this idea. The main challenge is to understand and convert the Obsidian markdown version into one that Publii can handle. That would i.e. help to export a folder of markdown files into a static local website, with working links etc.

— Reply to this email directly, view it on GitHub https://github.com/GetPublii/Publii/issues/1005#issuecomment-1161252796, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALAYY7RYIXU5RDVE3VX5POTVQFADTANCNFSM5A4OMUXQ . You are receiving this because you were mentioned.Message ID: @.***>

[lkhrs]

If Publii is CommonMark compliant, it only needs to support [[wikilinks]] (including ![[image]]) for it to be mostly compatible with Markdown files from Obsidian. See Obsidian docs.

Mermaid diagrams, callouts, and highlights would be nice as well, but I don't think those features get enough use to warrant special support in Publii.

Alternatively, while we're waiting for the Publii plugin API to be finalized and documented, consider converting your wikilinks to regular Markdown links and images, there are several Obsidian plugins available, and you can still trigger page autocomplete with [[. This is what I'm going to end up doing for my Hugo site.

[candideu]

Hi! I know this is an old post, but I just wanted to add my two cents, since I use both Publii and digital garden-style apps.

I would recommend using Logseq. It's free and open source, and can export to HTML, allowing you to host a digital garden blog online for free on the platform of your choice. I'm using GitHub Desktop to update and GitHub pages to host mine.

Plus, you can update the look and feel for most of the app using CSS, or by downloading custom themes.

Here's a guide on getting started with Logseq and Publishing to Netlify: https://briansunter.com/graph/#/page/logseq-getting-started

Here's an example of a project I created using a modified version of Logseq for my Master's thesis:

www.demo.diasporamemory.com

I also used Publii to create the main website:

www.diasporamemory.com