-
{{[[TODO]]}} might even be useful for [[roam's multiplayer mode]] and the #[[(hidden) jOMmlCP4S]] of [["putting" things into multiple graphs]], or, rather, giving other, shared-graphs e.g. read access to some of your notes, if they're under that tag (while still being able to own them?)
-
#[[(hidden) jOMmlCP4S]] / #[[(hidden) D1lY0CG5e]] for [[roam]] - would having a central place for settings, provided by the [[(hidden) AqlNqCYG6]]s / extensions, be useful?
-
something similar to [[vscode]] i suppose
-
thought about it because it'd likely save time / less http requests to do -- even if you have [[meta tags]], you don't need to 1. fetch your custom settings page, 2. fetch the linked references of the tags - you'd be ensured that 1. is always done & up-to-date (it's easier for roam if it itself tracks what's updated & when it is - just updates, otherwise caches)
-
but, maybe inconvenience if you're using some other languages for the [[(hidden) AqlNqCYG6]]s (if even possible?), and in general feels less [[wild west]]-like / less [[(hidden) NWcsO1fe0]]. will see.
-
-
{{[[TODO]]}} okay more [[(hidden) jOMmlCP4S]]s coming in from thinking about this:
-
oh fuck another #[[(hidden) jOMmlCP4S]] while thinking about this -- if we setup roam for further automations, e.g. [[creating jira issues / sub-tasks from roam's TODOs]]
-
WAIT i thought you'd have like a custom server and use [[roam-traverse-graph]] to parse the graph, and then have like a frontend dashboard SPA or whatever to confirm stuff.
BUT hold up, we have [[roam/js]]. we can get rid of literally all of the #bs, and do everything directly in [[roam]] 🤯
for API calls to some endpoints, sure could use a server, or e.g. lambda functions. but perhaps roam directly is also fine, if we can securely keep secrets stored?
-
-
re:: [[creating jira issues / sub-tasks from roam's TODOs]]
-
-
[[philosophical question]] (because [[bus factor (tbd)]]) if this is a good #[[(hidden) jOMmlCP4S]] or not.
-
(hidden) MiCFAw2Mi #[[(hidden) jOMmlCP4S]]
-
{{[[TODO]]}} yet another #[[(hidden) jOMmlCP4S]] - being able to copy a link to a page, or rather - to a specific block which will end up in that page
-
use case e.g. - creating a git commit, and instead of inlining stuff that you already wrote down, instead linking to it.
-
extra stuff to work out though because depends on where you want the link to end up at -- the daily notes page, or within some page as a linked mention.
-
{{[[TODO]]}} would need to have a predefined base url for the notes in the [[roam-traverse-graph-settings]] page.
-
-
{{[[TODO]]}} another #[[(hidden) jOMmlCP4S]] -- instead of having every single line to recursively, why not follow in a $$45\degree$$ or whatever angle and highlight only the right-most lines?
-
haha i guess fair, but don't worry much - [[roam-traverse-graph]] is first and foremost a low-level utility/library that one can use to build tools such as [[export-html-pages]]. and if we take our own shot at it - it's how we want it to be, and if we have some [[unique]] (?) [[(hidden) jOMmlCP4S]]s & are able to explore them - the better it is for all!
-
{{[[TODO]]}} yet another #[[(hidden) jOMmlCP4S]] - directory-like history when exploring / going into pages? similar to the [[macos]]
-
{{[[TODO]]}} another #[[(hidden) jOMmlCP4S]] from the [[re]] attribute above - in the html, consider having previews of pages on hover.
-
{{[[TODO]]}} (hidden) 9jAzVgueo [[roam/js]] [[(hidden) AqlNqCYG6]] #[[(hidden) jOMmlCP4S]]
-
(hidden) WlA4To-QK [[(hidden) jOMmlCP4S]]
-
{{[[DONE]]}} (hidden) 6rkQXVP8m
-
{{[[DONE]]}} (hidden) zux6b7yIa
-
{{[[DONE]]}} (hidden) bpTX0L0rL
-
{{[[DONE]]}} (hidden) 7HoO5Byz1
-
(hidden) ir8Phk9pS