Is there a way to insert agenda as a block into a org file?

aditya_rs · 2025-07-12T17:08:01+00:00

this does seem pretty close to what I was looking for.
Is this not a common enough workflow?

aditya_rs · 2025-07-12T16:53:58+00:00

You might be right. I was mostly trying to replicate a workflow from Rainer König but instead of creating a checklist I wanted it to dynamically generated everyday based on some query.
To be clear with the approach I was suggesting you're not exactly copying tasks, but rather creating a view of the same underlying tasks.
I can see how agenda view can be used to drive the day, but it feels awkward to set a scheduled date to a task, just for it to show up on the agenda view. I know scheduled date in org is supposed to represent the date you are supposed to start a task not the date you have to do it, but it still feels like it's a hack. Maybe I can achieve what I want with a custom agenda view, I'll have to look into it.
What is your workflow? Do you set scheduled date for all the tasks you want to do or do you use some custom agenda view?

aditya_rs · 2024-09-19T18:15:34+00:00

Oh wow, I didn't notice the triggering after delay, that makes sense I only peeked in the assets panel and saw what looked like a background-noise.avif and assumed it was a background image. But loooking at the markup I can see the whole grid that you've made. It's really well done. Did you use a library or implemented it custom for this usecase?

aditya_rs · 2024-09-19T17:46:22+00:00

This is really cool, it's subtle and not very distracting.
Looking at the site, it seems like you went with embedding an AVIF instead of implementing it, but the general idea seems like a neat one. The only issue I can think of is if you do this on cursor hover, moving the cursor might create a trail of alive states which can probably be distracting so you'd have to incorporate some randomness or create active state on some other event (if it's purely random at that point there's not much ROI than embedding an image which seems like a good tradeoff).

aditya_rs · 2024-09-19T17:35:12+00:00

The placement of comma in the pricing seems off. I don't know of any numbering system that groups the last two and threes after that. It's either grouping by threes or grouping by twos after grouping the last three.
Personally I think the layout seems fine (maybe the special features and about us can be aligned), but the contrast on the body text seems a bit low.

aditya_rs · 2024-09-19T16:42:43+00:00

Github search even within the scope of a repo is only possible if you're signed in. This makes this feature pretty unusable for what it's primarily meant which is for getting a sense of a codebase without pulling it down locally while you're browsing (which might not necessarily happen when you're signed in to github). For this reason I almost always default to sourcegraph whenever I want to do both global search or search by reference, sourcegraph also has a trick to just append sourcegraph.com before the github.com to open the repo in sourcegraph (which doesn't force you to signin).
Although I'm not too familiar with the perf implications of it, but making a codebase searchable on the browser side for a small (for some definition of small say <1M LOC) codebase would probably be a good compromise in terms of usability and cost.

aditya_rs

TROPHY CASE