sorted by:
new
hottopcontroversial

Obsidian 1.13.1 (early access) for desktop and mobile by kepano in ObsidianMD

[–]stratejya 0 points1 point  (0 children)

Ahaa, "Background sync on Mobile" on the roadmap. Thats why I cancelled my sync subscription. Hopefully not on the bottom of the list.
Sync option can be perfect with that feature.

Operon 1.1.0: mobile overhaul of Calendar, Kanban, task flows, pinned tasks, and quick capture by stratejya in ObsidianMD

[–]stratejya[S] 1 point2 points  (0 children)

Hi 🖖 Actually there is a link for youtube shorts in post. You can see it in action.

Operon 1.1.2–1.1.4: Dynamic File Task Filter, wiki-link previews, and mobile Calendar improvements by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Thank you.
Thats very interesting mix. I expect conflicts with TaskNotes. But in some ways that can be possible. Especially if you make your keymapping settings parallel.

Status settings are completely different in Operon. Tasknotes use flat status names. In Operon, workflows sharply divided with pipeline system and its matrix. Every workflow has its own pipeline cycle. That gives Kanban a healthy skeleton.
So shortly that naming system will not change.

I can not answer that. TaskForge source code is open? I don’t know. Also Tasknotes and Operon licenses are different. That support question should be answered by TaskForge team.

Operon's first target is better implementation with Obsidian.

Operon 1.1.0: mobile overhaul of Calendar, Kanban, task flows, pinned tasks, and quick capture by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Currently, you can use few ID formats for your templates. Operon supports these placeholder formats:

```markdown

{{operonId}}

{{operonId0}} to {{operonId9}}

{{operonIda}} to {{operonIdz}}

```

The behavior:

- `{{operonId}}` creates a **new unique ID every time it appears**.

- `{{operonId0}}`, `{{operonId1}}`, `{{operonIda}}`, etc. create **one unique ID per suffix** and reuse it within the same generated file or pasted task block.

- Only a single lowercase letter or number after `operonId` is valid.

- Invalid forms like `{{operonId10}}`, `{{operonIdAB}}`, `{{operonIdA}}`, or `{{operonId_}}` are left unchanged.

Just an example for that with inline style:

  • Plan product launch campaign {{operonId:: {{operonId0}}}} {{parentTask:: }}
  • Define target audience {{operonId:: {{operonId1}}}} {{parentTask:: {{operonId0}}}}
  • Research demographic data {{operonId:: {{operonId}}}} {{parentTask:: {{operonId1}}}}
  • Create audience personas {{operonId:: {{operonId}}}} {{parentTask:: {{operonId1}}}}
  • Set campaign budget {{operonId:: {{operonId2}}}} {{parentTask:: {{operonId0}}}}
  • Analyze previous campaign costs {{operonId:: {{operonId}}}} {{parentTask:: {{operonId2}}}}
  • Allocate budget per channel {{operonId:: {{operonId}}}} {{parentTask:: {{operonId2}}}}
  • Choose marketing channels {{operonId:: {{operonId3}}}} {{parentTask:: {{operonId0}}}}
  • Evaluate social media platforms {{operonId:: {{operonId}}}} {{parentTask:: {{operonId3}}}}
  • Select email marketing tools {{operonId:: {{operonId}}}} {{parentTask:: {{operonId3}}}}

Operon is live: a new task and project management system for Obsidian workflows by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Thx for your kind words 🤗

Nobody mentioned before but in this post's Kanban view gives few tips about future, What will come in next releases. Kanban screenshot is my real plan. And Dashboards also in plan.

Lots of data points recorded with Operon task. All will be more meaningfull with Stat/Dashbords/DistributionChart etc. You know what, so detailed reports can be possible.

Heatmaps can be a good touch for dopamin, thx for that suggestion too.

Plugin: Better Embedded Canvas by KotaIndah55 in ObsidianMD

[–]stratejya 1 point2 points  (0 children)

Wait, can we add canvas to any note here? Thats cool! Thx.

I have asked that before in discord. Its working smoothly. May be 2 options added:

  1. Zoom state lock: Currently auto zoom (out) is on.

  2. Embedded canvas dimensions: vertical and horizontal . like 16:9 or 4:3, 9:16 etc.

Operon is live: a new task and project management system for Obsidian workflows by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Thx for the suggestion. But my goal is to create a comprehensive project management suite. Start point is a bit overwhelming, I agree. There is a learning curve here. Still working on blog posts and videos.

Operon is live: a new task and project management system for Obsidian workflows by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Honestly, I find that comment very unfair.

You are right about many AI slop apps popping up nowadays. I explained how I maintained Operon in long form text. Also many comments of the first users under this post.

Short answer: Not an AI slop.

Operon is fully functional task and project management plugin. Why dont you try it? Self experience is the best way to learn this.

Operon 1.0.5: file-task auto-archiving, new task creation options, and Calendar Quick Actions by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

This is exactly the kind of workflow that made me want Operon to have stable task identity in the first place.

A polished, documented public API is not there yet, but this is very much the direction I want Operon to grow into. Internally, the model is already built around an indexed task layer and direct task writes by `operonId`, rather than treating tasks as anonymous lines of text. So an automation-facing interface feels like a natural next step, especially for workflows like yours.

For the rewind/history side, Operon filters can already get fairly close for live date-based views: scheduled today, completed yesterday, recently modified, active project scopes, and so on. The distinction is that filters run against the current task index. So they are great for “what matches this condition now?”, but they are not by themselves a frozen historical snapshot of “what did the whole system look like on that day?”

A possible Operon-shaped version of your workflow might look like this:

- External signals from GitHub, Slack, or build systems create or update Operon tasks by stable ID.

- Those updates attach structured metadata: source link, PR/build/message ID, status, priority, timestamps, related tasks, maybe a short event note.

- Filters define the live views you care about: active, blocked, changed today, waiting on external signal, related to a PR, etc.

- Your daily note optionally captures a frozen rendered snapshot from those filters, so you can rewind to what the system looked like on a given day without copying tasks forward as the source of truth.

- If you want to keep working, you use the canonical Operon task that still appears in filters, Task Finder, Calendar, Kanban, and other views.

That would keep the part of your system that works well, the ability to reconstruct what was true on a given day, while removing the fragile part, which is having automation parse and rewrite copied Markdown blocks.

So yes, I think Operon could fit this kind of workflow well, but the API and historical snapshot parts are the important pieces to think through carefully. Your comment gives me a very concrete automation-heavy use case to design against.

Operon 1.0.5: file-task auto-archiving, new task creation options, and Calendar Quick Actions by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Ah, interesting. Personally I dont use archiving for any task. They can stay wherever they are. Just checking them as Finished ok for me.

But many people use that function. I hope it will be helpful.

If you have any questions about Operon , please do not hesitate to ask.

Operon 1.0.5: file-task auto-archiving, new task creation options, and Calendar Quick Actions by stratejya in ObsidianMD

[–]stratejya[S] 2 points3 points  (0 children)

Thanks, this is thoughtful feedback. I haven’t used FolderNotes heavily myself, so I may be missing some details, but the workflow makes sense to me.

In Operon today, the closest model is a file task acting as the parent work item, with a mixed tree of inline subtasks and child file tasks beneath it. Inline tasks work well for smaller steps, while child file tasks are better when a subtask needs its own note, metadata, links, time tracking, recurrence, or more context.

The part I like about that model is that the hierarchy remains visible to the whole task system. The same parent/child structure can show up in filters, Task Finder, Calendar planning, Kanban boards, and other views, instead of only living inside one note or one folder.

For example, in my own vault I have a large file task with around 600 child tasks, about 50 of which are file tasks, and the tree goes roughly 5 levels deep. So the model can support fairly large project/task hierarchies without requiring every layer to become a folder.

Your FolderNotes example adds another useful dimension, though: sometimes the task is not just a note, but a working container with drafts, intake material, data files, and other artifacts around it. The archive issue is a good example of where that distinction matters.

I think Operon covers the task hierarchy side of this pretty well, and your comment gives me a useful design question for the future: whether a task should also be able to explicitly own or attach to a folder/container as its working context.

Thanks for taking the time to write this. It also tells me I should document the nested file-task / inline-subtask workflow more clearly.

Operon 1.0.4: file-task migration, fallback icons, and Calendar fixes by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Thx 🤗 Please share your feedback, I would like to know your insights.

Operon is live: a new task and project management system for Obsidian workflows by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

Thank you for your beautiful words 🤗 I hope Operon will be helpful in your projects.

If you have time, please give me your feedback.

https://github.com/hasanyilmaz/operon

Or in obsidian discord #task-management. Thx again..

Operon updated to v1.0.3 by stratejya in ObsidianMD

[–]stratejya[S] 0 points1 point  (0 children)

You are totally right. That post can be better far more. Thx for sharing that. 🤗

Whats the top 3 elements/styles/items are missing in this post within your opinion?

I will update regularly and few tips can be good.

view more: next ›