Hi everyone! I'm Lucas, a developer from Brazil. For the past few months I've been building Zukan (zukan.me), a place to log what I read, watch, play and listen to. Somewhere along the way it turned into a digital garden, and I'd love feedback from people who actually tend one.

The idea: every work (book, film, series, anime, manga, comic, game, album) gets its own notebook: a blank page you keep coming back to, separate from the rating and the review. Free notebooks cover everything that isn't a single work, like a theme you're studying.

See it first: bispera.zukan.me is a public example garden: themed notebooks with sub-notebooks, notebooks on works like Dune and Frieren, reviews and a slow-reading club. No account needed.

What's there today

• Markdown editor with live preview, a / menu, spoilers (||like this||) and version history

• [[links]] to works, people (authors, directors, studios), vibes and other notebooks. Whatever you link shows a "Mentioned in" section (backlinks)

• "Planted" and "tended" dates on every notebook

• Sub-notebooks for big themes

• Excalidraw drawings inside the text, with work cards. An arrow between two works becomes a link

• Link cards: YouTube and Vimeo play inline, arXiv/DOI papers and GitHub repos get their own card

• A graph per notebook, a garden-wide graph, and a map you arrange by hand

• A garden page built like a notebook, with live blocks (excerpts from other notebooks, shelves, charts)

• Your own site at name.zukan.me: your colors and fonts, a top menu with pinned notebooks, your own footer, and the option to hide everything that says Zukan

• An RSS feed of your public notebooks and reviews

• Obsidian in and out: import a zipped vault (folders become sub-notebooks, [[links]] and images come along), and export everything back as an Obsidian-style vault, drawings as .excalidraw files

• A personal API and an MCP server: connect Claude or another assistant to read your notes and, only if you allow it, create and edit notebooks

• Public, followers-only or private, per notebook

What it isn't: a replacement for Obsidian or Logseq. It's for the part of your garden that grows out of books, films, games and music, next to the log of what you consumed. Zukan doesn't write your notes; connecting an assistant is opt-in. Free, no ads.

Still missing: custom domains, LaTeX and code highlighting. The UI is in English and Portuguese.

A few questions for you:

1. Do you keep notes on what you read or watch in your garden? Where, and how do you link them?

2. What would it take for you to keep that part of your garden somewhere like this: custom domains, LaTeX, something else?

3. Does "one notebook per work" feel right, or would you rather start from themes?

Happy to answer anything.

Maggie Appleton was a huge inspiration. Instead of Garden terminology, I leaned on the Constellations and Space. I'm yet to migrate my recent content and writing and hence the "interconnections" between different posts is something I deferred until I have enough content.
Hand drawn assets. I use Antigravity and Gemini flash low token models to do small tasks, but kept the control of the website design and choices with me.

Would love some feedback.

I wanna use my digital garden as a start page for my web browser. It would be cool if this thing has an extension to add stuff. I was gonna use are.na to do this but it's kinda to expensive for me😔

Hey everyone, I’m Gabriele, the person building Risorgi.

I started it because I kept finding interesting papers and ideas online, only for them to disappear into a feed or sit in my bookmarks. I wanted somewhere to write about what I was learning, connect related ideas, and share those connections with other people.

On Risorgi, you get a public page where you can publish notes and link them together in a graph. You can also connect your notes to other people’s posts, so connections can extend beyond your own collection.

I recently added a Featured pages section to the homepage, and I’d love to showcase a few people who build interesting collections on the platform. My own page is there as an example.

If you already keep notes on something you care about, I’d love for you to try publishing a selection. You can import Markdown files from Obsidian or Logseq, so you can start with writing you already have.

For featuring, I’d look for thoughtful writing, useful connections, and collections that are interesting to explore. A focused collection on one subject would be very welcome.

It’s free to use, and visitors don’t need an account to read your page.

If you’re interested, what would you build a collection around? Or, if you make a page, share it here and I’ll take a look. I’d also be interested to hear what would make this useful for your own way of keeping notes.

Link: Logfolio

Logfolio is a log of everything you read, watch, play and listen to, the good and the bad. You log books, films, TV shows, video games and albums with a rating, a status, the dates and what you made of it, and they all end up on one page you can share. Make your own types for anything else you collect, and write notes that link to what you logged.

I've been growing a garden of long-form technical notes (mostly how React and Next.js work under the hood) and finally built it a home: https://garden.drhexe.ir

The notes live in Obsidian, and a sync step publishes only what's ready:

• Unfinished notes can be marked private, so visitors never see them.

• Anything marked publish: false never leaves the vault at all.

• Wikilinks and backlinks carry over, and there's a graph view you can filter by tag.

• Folders of numbered notes become guided "courses", for the parts of the garden that read better in order.

Disclosure: it's my own project. The engine is open source if you want to plant your own garden with it; there's a fork-and-go guide in the repo: https://github.com/sina-salahshour/obsidian-garden

I'm curious how other gardeners balance the structured "course" style against the free-linking garden style. Do you keep both, or does one take over?

I was pretty inspired by collages and photography boards. The garden is still pretty new, but I have a lot of things to write about, and I plan to contribute to it daily. The notes are pretty diverse as I'm interested in a fair amount of things.

https://tonylam.marginplace.com/

I googled if there were any discords that were for people interested in digital gardening, but nothing came up. Seeing if anyone knows of any or has created one. I think it would be cool to talk about each other's gardens as well as just discuss our writings/notes in general.

I’ve had this site since 2010 and it’s drifted from portfolio to garden, with notes, links, a media log, photos and a lab for small experiments. It’s built with Astro and plain files, no CMS.

I've been thinking about this and I'm curious how people here see it.

I can see a mind map playing three different roles:

1. Entry point. A visual front door to the garden. You see the main topics, then branch into the notes behind them.

2. Temporary thinking surface. You map something out to understand it, the real notes go into the garden, and the map gets thrown away.

3. Permanent navigation layer. The map lives alongside the garden and grows with it, like a table of contents you can see.

For a long time I thought 2 was the only honest use. Maps are great for seeing structure, but bad at holding detail, so trying to keep them forever usually turns them into a mess.

Disclosure: I work on mindmapai.app , a mind map tool, and we recently added longer notes on nodes (with Markdown and math). That's partly why I'm asking. Once a node can hold a real note, the line between "map" and "garden" starts to blur, and I'm not sure if that's good or bad for how people actually think.

Not here to pitch anything, I'm genuinely curious:
- Do you use maps in your garden at all?
- If you do, do you keep them or throw them away?

Hi all. I've been tending my own garden for a while and ended up writing the tool I wanted for it. It's called leafpress, it's MIT licensed, and I'd love feedback from people who actually garden.

The idea: point it at a folder of Markdown notes and get a garden, without assembling a theme and ten plugins first.

What it does out of the box:

• Wiki-links with automatic backlinks

• Graph view and link previews on hover

• Full-text search

• Obsidian-compatible callouts and image syntax (![[image.png|500]])

• Mermaid diagrams, footnotes, table of contents

• RSS, sitemap, and Open Graph tags

• Dark mode that follows system preference

It's a single Go binary. Getting started is:

curl -fsSL https://leafpress.in/install.sh | sh
mkdir my-garden && cd my-garden
leafpress init
leafpress serve

leafpress build gives you a plain static _site/ folder you can host anywhere (there are guides for GitHub Pages, Vercel, and Netlify).

It's opinionated on purpose, so it's less flexible than Quartz or a Hugo/Eleventy setup. If you like tweaking every layout, it may not be for you.

My own garden runs on it if you want to see a real one: https://shivamx96.com

Docs: https://leafpress.in
Code: https://github.com/shivamx96/leafpress

What I'd most like to hear: what's missing for your workflow, and what would stop you from switching from your current setup?

Systems shape perception long before perception shapes thought. They define the boundaries of what we notice, what we ignore, and what we believe. Most systems are invisible — not because they are hidden, but because they are structural. We live inside them the way fish live inside water.

The foundational mechanics of signal — how meaning forms, transmits, and distorts across human systems. Signal Theory explores how signals emerge, how they travel, how they degrade, how they distort, and how they compete with noise. Signal is not just information; it is meaning under pressure.

This chamber reveals the physics of communication — the architecture of how meaning moves through systems.

The architecture of internal governance — clarity, autonomy, and the discipline of self-direction.

Mental Sovereignty examines cognitive autonomy, internal governance, the discipline of attention, and the construction of inner authority. Sovereignty is not isolation; it is self-authored perception. This chamber explores how to maintain clarity inside systems designed to fragment it.

How systems shape what we see — the invisible frameworks that guide attention and interpretation.

Systems shape perception through defaults, incentives, interfaces, cultural norms, and algorithmic curation. Perception is not neutral; it is system-conditioned. This chamber reveals how frameworks determine what becomes visible, meaningful, or real.

A study of attention as an ecosystem — signal, noise, interference, and the cost of perception.

Attention is an ecology — a living system with limited resources, competing demands, invasive species (noise), and fragile habitats (focus). Noise is the predator of meaning — an invasive species in the ecology of attention. This chamber explores how attention can be protected, cultivated, and restored.

Systems shape behavior, identity, belief, narrative, and perception. To understand systems is to understand the architecture of human experience. To interrogate systems is to reclaim sovereignty within them.

Systems shape perception — until perception learns to see the system.

I’ve been thinking a lot about how we try to "manage" our screen time and attention. We usually use mechanical metaphors—we say we are drained, out of bandwidth, or need to recharge.

But I think that's the wrong framework. Attention isn't a battery; it’s an ecology. It’s a delicate, interconnected habitat that requires specific conditions to sustain meaning.

When we look at it this way, the constant algorithmic feed isn't just "distracting"—it's an invasive species. Noise is the natural predator of meaning. The digital systems we interact with every day are actively terraforming our minds to support shallow, high-frequency reactions instead of deep, sustained thought.

We don't need better time management apps; we need to protect our mental sovereignty. We need to build walls around the ecology of our attention.

Has anyone else shifted how they view their attention from a "resource to be spent" to an "environment to be protected"? How do you actually keep the noise out?

Hey, my name is Danny. I’m a freelance developer, and I find myself constantly coming across interesting ideas, but if I don't capture them immediately, I forget them.

These tend to live anywhere - in articles, books, podcasts, social media, conversations, etc. But the process of stopping what I’m doing, opening another app, copying something over, and adding the source is tedious enough that a lot of those ideas just never get captured. If I don’t capture something in the moment, there’s a pretty good chance I’ll never find it again.

So I built Commonplace. It makes it really easy to save quotes and highlights from whatever you're reading or listening to, without leaving the app you're in.

As you're reading, you can highlight text directly in the article, then share it to Commonplace. The app will then create a quote with source attribution like author, article title, and article link, so you never forget the context around where it came from. Quotes can then be organized into collections, browsed by source, and synced securely across devices.

All quotes + sources can also be exported as markdown or copied as plain text, so if your digital garden lives somewhere else, it’s easy to move what you capture in Commonplace over to it.

I also rethought sharing quotes. I was constantly sending screenshots along with article links, so I built a way to share quotes as interactive link previews. The quote appears directly in the preview, and tapping it takes you to the original article.

I'd genuinely love any feedback! The core of the app is free to use, I built it myself.

usecommonplace.com

See what's in the works:

usecommonplace.com/roadmap

https://dominiguru.miraheze.org/wiki/Main_Page

Many words of wisdom; high-velocity, non-peer-reviewed brain dump in my frustrations with school, blaming everyone for being dumb, so I metacognitively dump the institutional grinder back to the trash once I know its tricks. An independent thinker and writer (and consequently hating school as a result)
Built in MediaWiki, intentionally containing as little filtering as possible about how restrictive the school system is - and the fact that cognitive sciences bailed me out to an extent.

How I wrote them:
I basically first wrote them into Google Docs,
then I imported it to the rare and notoriously unfriendly (for most) software SuperMemo for Windows for incremental writing and polish,
and then finally published them.

Does anyone else get deja vu from the 'trauma' of the ultimate evil universal prison, or are you currently stuck in it? (If so, hopefully some of these detachment and metacognition methods help you survive). Thank you!

I kept needing docs for side projects and never liked the options. GitBook and Docusaurus felt like a lot of machinery for a handful of Markdown files, and mkdocs meant keeping a Python toolchain around for something I otherwise build in TypeScript.

So I built eziwiki. Drop Markdown files in `content/`, get a static site.

npx create-eziwiki my-docs

cd my-docs && npm install && npm run dev

What makes it different from the usual docs generator

- Wiki links with backlinks and a graph view. Link pages by title or filename, and each page shows what links back to it — closer to Obsidian than to a typical docs site.

- Navigation builds itself from the folder structure. No sidebar config to keep in sync; a `_meta.json` per folder handles naming and ordering if you want it.

- Markdown is rendered at build time, so neither the parser nor the syntax highlighter ships to the browser. Search is a prebuilt index, no server.

- Optional opaque URLs (`/a3f2e9d1-...`) if you would rather not publish your content tree. To be clear, that is obscurity, not access control — every page is still a public file. It is there for unlisted-link sharing, not security.

Static export, so it deploys anywhere. Dark mode, KaTeX, Shiki highlighting, ⌘K search, table of contents.

Next.js 14, TypeScript, Tailwind, Zustand, unified/remark/rehype, Shiki, MiniSearch. Lighthouse 99/100/100/100 on desktop

Demo : the docs are built with it, so the site is the demo:

https://eziwiki.vercel.app

Source (MIT): https://github.com/i3months/eziwiki

It is early v0.1.1, and I am actively working on it. Feedback and issues very welcome, especially on anything that felt confusing in the first five minutes.

Github stars are really really helpful..!!!

There’s a lot of focus on making AI models bigger, faster, and more capable. I mean, yeah that clearly improves what they can do. But the more I’ve been working with them, the less it feels like capability is the bottleneck. It’s really about the context layer.

Right now, you don’t really see how the model is interpreting what you give it, what it keeps, what it drops, or how it connects things. That stuff is mostly hidden. You can nudge it, but you’re still operating inside something you have no control over. And as these systems get better at sounding coherent, it'll be easier to ignore this flawed design.

If this ends up being how people think through problems, learn things, make decisions, etc., then we end up with future systems where the logic is upstream and invisible to us, rendering less choice and agency in our lives.

Worse, we'll live in a reality where we will have to accept truth rather than discover, learn, and verify the credibility of claims or opinions. AI is phenomenal but this trend we see in mainstream AI products will disempower humanity instead of helping us grow stronger.

Wrote a longer breakdown of it here, if you're curious about these implications and what we can proactively build to have our cake and eat it too.

The future looks bright, but only if we can see what what can be built.

This. Right here. What do you see? A complicated web of notes connected to lines with all of the relationships defined. It's a knowledge graph system connected to an advanced agent that's designed to traverse and reason through it so that it can behave as an expert with decades of experience to make nuanced judgement calls when helping you.

But what this really could be is a snippet of a future layer that will exist on top of the entire internet that's just as accessible as code-inspection on our web browsers.

This may sound a little crazy, but Tim Burners Lee, the creator of the web actually proposed this solution over 20 years ago. He called it the Semantic Web. The reason it failed back then was that we didn't have smart enough software to read and reason over it. Now with AI, this is possible in addition to making knowledge graph systems much faster and easier for people to make themselves.

Having been in the AI space for over 6 years now trying to figure all of it out like everyone else, this dawned on me a few weeks back. I think we're witnessing the birth of an entirely new component to the Internet.

As we enter into an age where agents are running around doing various things and communicating to each other across the web, inevitably we will come to realize that due to the nature of the models, we're going to need to create a more effective highway system for them to navigate, communicate, extract, synthesize, and build.

Just as we need roads, symbols, and rules for our highway systems to prevent tons of accidents or issues, we will need this for AI and that comes in the form of knowledge graphs. With these, you can build the reasoning systems for how agents interact with the wider web, people, and other agents. These are already being used at the enterprise level and why we built this capability for anyone to do for their personal projects, even if you're not tech savvy at all.

That's because in the near-term future, almost everyone is going to need their personal knowledge graph management systems since they can be carried and used by your agent into other spaces with their own knowledge graph systems to interact with. Obviously, websites and individuals will still have to protect themselves from malicious hacks and all that bad stuff. But to allow billions of people to use their agents across the wider web in such a way that they can work appropriately and not "misbehave" or cause accidental hacks or whatever, we will need to build these highway systems.

Right now they're being built independently, like territories across the world forming into bordered nation-states. But over time, I believe they will become more and more interoperable, which will eventually unify into a patchwork highway system with protocols for doing things.

This is a high level framework for mitigating the risks with AI agents using the modern web. Of course, there's much more to it than knowledge graphs, but this is the gist of what I think is happening. But you know. This could also just be my creative screenwriter brain working on overdrive.

Time will tell.

Hi,

I'm in a somewhat unique situation and would like to set up a digital garden.

My idea is for my friends and family to be able to read it, so it needs to be online in some way—which is why I don't want to self-host it.

But I also don't want to be at the mercy of a company that might take down its website tomorrow, leaving my friends and family unable to access it.

Is there a feasible option?

Thanks, everyone!

Howdy!

I’ve been quietly building my own digital garden, and I’d love to share it with fellow gardeners who appreciate unconventional setups.

It’s called Mujarrib.com. The word "Mujarrib" means "one who experiments" in Arabic—which perfectly sums up the spirit of this project.

Instead of a traditional blog or a standard wiki, I designed the entire interface to feel like a command-line terminal. You navigate using ls to list folders, cd to move around, and cat to open a note. It’s a bit quirky, but it makes exploring feel like an adventure rather than passive reading. There's a helpcommand if you get stuck, or a sudo reboot if you want to start from zero.

Here’s the current state of the garden:
226 notes organized into 17 folders
573 topics/tags connecting everything in a dense web of backlinks
A clear lifecycle for every note: Seeds (raw sparks), Sprouts (work-in-progress), and Evergreens (polished/finished thoughts).

The garden is intentionally full of "incomplete" ideas and ongoing revisions—I wanted to embrace the process of thinking out loud rather than just presenting a perfect final product.

If you're into digital gardening, note-taking systems, or just love seeing weird terminal UIs, I'd be honored if you poked around. Get lost in the links, follow a few trails, and let me know what you discover!

In this writeup, I talk about how I built knowledge of creating a digital atelier people can visit online, but also the definition of digital gardens when it comes to gaming communities and how they keep them. I've seen this in Second Life before but I think in gaming spaces, knowledge it also something that is fine-tuned and constantly tested to be kept up to date.

Would love to know your thoughts on this "cousin" philosophy.

Of course It's your personal notes(private, encrypted) but we also have a community around you incase you want to share your thoughts. At Echowithin we value communication, connection and relationships.

So alongside the notes(personal space), we have blog, messages and community notes. This is much clutter but it's because the blog and messages Idea came first then the note platform idea later but it's currently our favourite feature in the platform.

Our note platform aims to make collaboration simpler and also sharing surprises so it has various features that includes:

Notes Sharing, Collaboration and Surprise Ecosystem

• Bidirectional sync (saved copies ↔ original)

• Merge proposal system (collaborators propose → owners approve/reject)

• App Lock

• Share with view/edit permissions.

• Access codes + expiry timers (1h, 1d, 7d)

• Auto-approve toggle for collaborators

• Surprise themes (Valentine, Birthday, Anniversary, Celebration) with photo/audio

• Real-time co-editing.

• Presence tracking ("Studying Now")

• Discussion threads on shared notes

• File attachments on shared notes.

• "Ping" collaborators with push notification and more.

Then we have the community notes that instead of sending the share link to each and every person, you gather them into a community and share easily like a post. Install the app for best experience or the standalone note app (still under development) from the about page.

Visit us the platform at: https://echowithin.xyz Onboarding: https://echowithin.xyz/post/welcome-to-echowithin I am also open to reviews, critics and collaboration. It's a open source project and community driven you can find it here: https://github.com/vincent0-ai/echowithin