export-html-pages | notes | kipras melnikovas

export-html-pages

words:	3 + 5965 = 5968
last update:

#public
parent:: [[roam-traverse-graph]]

Linked Mentions (51 in 36 pages)

November 27th, 2021 (2)

[[export-html-pages]]
- {{[[TODO]]}} exit on error
- {{[[TODO]]}} remove the live updates since they're misleading - we'd need to refresh to verify the page hasn't been re-uploaded
{{[[DONE]]}} created [[export-html-pages]] workflow! works!!!
- lol, i now understand the basis on how [[(hidden) CRbzoMPud]] works.
  - `#[[(hidden) T6ohXioC_]]`s or whatever & other logic in templates - u can make it whatever u want if you were creating a similar framework xd

November 29th, 2021 (2)

because currently in roam, nothing is auto-expanded, and in [[roam-traverse-graph]] [[export-html-pages]], everything is. this seems like the best alternative.
also i mentioned the exported codemods page via [[roam-traverse-graph]] -- whole point is that there's more transparency of what i'm doing, and i wanted it to be available earlier but only managed to create the mvp of the [[export-html-pages]] plugin this weekend. will be useful for later missions though.
- also showed the power of #roam . He first asked if I've used #[[(hidden) 7pX0uAw-4]], and ofc i have, so i told that, but quickly mentioned of why it's annoying (grouping, labeling manually etc), and highlighted how easy it is to do things in roam hehe. i think he'll easily join:D
- also saw him using the git plush alias for pushing - pretty sure that's the one i showed recently, mine being git pp - for pushing w/ automatically setting the upstream tracking (needed when pushing a branch for the first time), ah, awesome to see

December 4th, 2021 (2)

{{[[TODO]]}} [[export-html-pages]] fix urls (thus html filenames) - replace spaces with dashes `-`, keep only asciinumeric (latin letters & numbers) chars + `-_` (ez regex)
[[export-html-pages]]
- {{[[TODO]]}} get rid of custom domain.
  - {{[[TODO]]}} add docs on: 1. how to add the custom domain, 2. why you shouldn't. [[bus factor (tbd)]]
  - {{[[TODO]]}} add redirects from `notes.kipras.org/*` -> `kiprasmel.github.io/notes/*`
    - [[roam-traverse-graph]]
      - {{[[TODO]]}} oh just realised we need to handle math (wanted to convert from `->` to `$$\implies$$`). there was a lib that roam was using - we could use it to inline at compile time (if possible?)

December 7th, 2021 (2)

thinking about the [[export-html-pages]] plugin in [[roam-traverse-graph]] - would apply as well. maybe even plugins in general. will see.
- {{[[TODO]]}} another thought from this - instead of naming the utilities usable by other plugins `meta`, name them `core`.
[[git-stacked-rebase]] [[export-html-pages]]
- re: ((ECPmuH08j))
  - lol, i wanted to both use the linked reference for "clojure" ([[(hidden) d_BU9kVtB]]), and for the whole thing to be **in bold**. but that doesn't work in roam! and then i realized that when i'll be creating the Block's string parser, it'll need to be aware of the existing context / scope, i.e. what things wrap it already. i thought that you might want to walk upwards to check such things. and then i realized that [[(hidden) DTTuZxhoc]] (that i use for creating [[codemods]]) is exactly that. and that i could write a custom parser for roam's Block string (or, in general, any [[(hidden) XW4WLkPLe]] string i guess), and have it usable w/ jscodeshift. 🤯🤯🤯 [[(hidden) DY6wPnICE]] / [[(hidden) lVDvvGLLj]] i indeed thought/knew that the 2 projects are related, but this much? wow, no. i guess now all 3 are:D also: - [[(hidden) DTTuZxhoc]] is created by an engineer who works/worked at [[(hidden) unlH_9R0B]]. - [[(hidden) unlH_9R0B]] devs use [[(hidden) Qb76iqf_n]] + [[(hidden) iKtPaNgmv]] for version management (just like git) + [[(hidden) Qb76iqf_n]] has [[(hidden) mgTvVDjW-]] HOLY SHIT x2 it's all related (though 1 way, not both - $$\implies$$, not $$\iff$$)
    - (hidden) 2mF-JULeA #[[(hidden) 7c2C8PgIV]]
      - (hidden) BfPJvNsrx [[(hidden) M1UTLp3AY]] [[(hidden) DTTuZxhoc]]
        
        (hidden) 3pB5XzgfH
        
        (hidden) hL8svrdmT [[(hidden) eBB7dPivO]]
      - (hidden) Ovq0BggUq
      - (hidden) zK1n_TgGe
      - (hidden) E7qNUIATH

December 10th, 2021 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} "public-recursive" tag - public on itself, and all of it's children. if a page is marked as "public-recursive" on first-level child block w/o any children & only it (exactly how public global tags work now), it should also make itself and it's children public __when it is mentioned__.
  - hmm. but now think about block mentions. if a block contains a mention to another block that has this recursive tag, then does that mention make the block who mentioned it also recursively public? kinda unwanted!
  - maybe we need separate ones for:
    - "public when mentioned as a linked reference" (which would normally be the default, or so i though, until i realised that e.g. ppl names are not very good to be public by default, and well that the default wasn't very good, so we changed it)
    - "public, as in make the page & it's children public, but nothing else",
    - "public recursive" - make
      - wait. maybe:
        
        "public recursive _marker_" - do not make itself's children public, but make itself's title, and all _direct_ mentions of it public + their children.
        
        same as [1], but recursive
        
        [1] ((bzzfvHav8))
        
        "public
  - hmm, now that i think of it, seems like this "public or not, when mentioned" will always be a problem w/o a good default. instead, it seems like it should be something you do directly. e.g., have a triple `[]` mean a public linked reference (since more effort, less likely to accidentally make something public), and double `[]` - same as is now. could do this myself unofficially, the only problem is that the roam search breaks - roam starts looking for a `[]` in pages' titles, but ofc they don't have this, and so the completion list ends up empty, which sucks big time!
    - {{[[TODO]]}} create an issue in #roam to change the behavior (ofc explain why i need this)
- {{[[TODO]]}} as for security, i keep thinking about: should i include the security info in the default setup when explaining how to use the plugin in e.g. [[github actions]], or should i put it afterwards
  - i think the defaults matter. and so i should definitely put it in the default setup, because that's what everyone's gonna do.
  - the easiest thing to do, for starters, is to fork the repository and use the fork, instead of the main repo, as the source of the plugin(s)
    - updating is very easy. `fetch upstream` button available in [[github]] right next to the latest commit's info
    - {{[[TODO]]}} the repo could have security tests that should pass before each plugin run, so that in case we push to master and accidently get something messed up and a person also fetches the update at that time - they would immediately see the problem, instead of getting pwn'd.
    - {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] `git-rebase -i` right inside [[github]]'s PR UI lmao
- {{[[DONE]]}} simple docs for the plugin (just some notes + link to public notes on it)

December 15th, 2021 (2)

could be very useful for [[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} try out [[alpine.js]]
[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} maybe we only need the 2 public tags - "public" & "public-recursive"?
  - would apply the same way for a page & for a block
    - for a page - when mentioned in a first-level child block that doesn't have any children & any other text (just like now)

December 17th, 2021 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] have a folder w/ literally all blocks as filenames, and inside them have js/html to redirect to the actual page that contains the block lmao

December 23rd, 2021 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} new #[[(hidden) jOMmlCP4S]] - public recursive tag, but only if the page that is made public recursive, is mentioned in root level of a page (1st lvl child block) & has nothing else inside it (just like i often do in daily notes when referencing other pages & "writing into them" via linked references).
  - though, hmm, sometimes we still want it even if it's not on the root lvl of the page. e.g. just like right here.
    - then, maybe it's fine if it can be on any level, as long as it's the only one mentioned there
      - though, in this case, still wouldn't apply. perhaps if both (all) linked references mentioned there are public, and no private ones (or private-making ones?), only then could give an exception.
        
        though, also gotta think if it's worth "complicating" so much the logic that it's no longer worth
- {{[[TODO]]}} oh snap, inspired straight from the [previous one](((HW3tg57Ww))) - having a `roam/js` or whatever "extension" to add the simplest of indicators if something will be public -- would be great!
  - {{[[TODO]]}} maybe on hover, could even explain why
  - {{[[TODO]]}} but, for this to work smoothly, we kinda would need to double down on the "having most things in [[roam-traverse-graph-settings]]" that we want configured, instead of configuring things there such as "tag-that-makes-other-pages-public-recursive", whom would in turn be used in pages directly - this would mean it's easier for the [[roam]] user to use (probably? + info via linked references), but harder for tools to parse, because instead of parsing just the 1 single settings page, you have to parse it, and then parse all the related pages as well.
    - ofc, maybe [[roam]] in the future could provide APIs that would help work around this (e.g. user gets best xp w/ 2nd option; tools can use API to quickly find all pages that have the tag mentioned)
      - {{[[TODO]]}} wait but now that i say it this way, isn't it __exactly__ what `roamAlphaAPI.query` is like? 🤯
- {{[[TODO]]}} another one re: the total global word count as a number in the landing page
  - we could have it be a button (well, a tag with href) that navigates to a page that has a graph (chart) of (top secret what it shows)
    - {{[[TODO]]}} oo even more ideas - something like [[(hidden) btHMgS_i0]] has w/ "cool" statistics (normies represent, am i right?)
      - {{[[TODO]]}} #[[(hidden) D1lY0CG5e]] [[roam]] lmao just noticed - let me scroll to the very bottom of the page, even though there's no content there (i.e. like vim) - would be useful when i have some block opened & editing & want to scroll the current text higher into the view w/o creating a bunch of empty blocks below it.

December 25th, 2021 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} sort "terms" (public references but not public recursive ones -- tagged via public tags) __after__ public recursive ones (i.e. order should have lower prio)
- {{[[TODO]]}} replace spaces in URL with dashes to make the URLs easily copy-paste'able, clickable, if shared, etc.
  - {{[[TODO]]}} uh oh, would require replacing not in the URLs but in filenames because of how gh pages work
    - {{[[TODO]]}} buuut, in index.html file, we can keep it raw so that when searching in the landing page, it looks normal. same with the page title (h1) when we generate the page.
  - {{[[TODO]]}} also, implementing a `#[[(hidden) gmEjXMPhW]]` tag to set a custom url (well, slug), by us internally setting a custom filename, would also help.

(hidden) qtEMrD1aX (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} if a page is marked as private, then it should count as "privateRecursive" i.e. should act as if "private" tag was mentioned directly & makes others private
  - {{[[TODO]]}} exception with "private-only"?
    - nah doesn't even make sense, since it's private by default. tho idk, maybe does if u want 1 block private & then continue w/ public ones, but idk idk unlikely - once u go into private u stay in private, and having to mark it as "public" explicitly is a good thing imo
  - i.e. public non-recursive by default, private yes-recursive by default

roam-traverse-graph (1)

the public notes exported here as html pages are by one of the plugins -- [[export-html-pages]]

January 3rd, 2022 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- wait wtf literally everything's hidden :D
  - {{[[DONE]]}} let's un-push the temp changes & have a branch for them instead
    - {{[[TODO]]}} e2e tests we need!
- {{[[TODO]]}} some empty blocks are still getting hidden - fix
- {{[[TODO]]}} also, public linked references are being hidden in the linked mentions of a page
  - actually i think it's only for daily notes pages, because we have an exception for them to __not__ hide them, because their uid gives it away anyway
    - {{[[TODO]]}} thus, fix the exception - make work properly everywhere
- re: ((4EHmILvQ3))
  - {{[[TODO]]}} hmm. maybe the thing still applies that historically for legacy it's good to not have it under a custom domain, __but__ we become dependant on [[github]] and e.g. if they change something up (which they shouldn't, because crazy [[(hidden) C3WBaKpP3]], but [[(hidden) fx7rnQ3uc]]), then we're kinda screwed & if other ppl were linking into gh, we no longer control it...
- {{[[TODO]]}} figure out what causes the sometimes occuring git error in github actions runner (self hosted), which you need to manually resolve by removing the whole notes-private/ directory
  - {{[[TODO]]}} figure out if affects only self-hosted or [[github]]'s own as well
  - {{[[TODO]]}} figure out the actual problem

July 10th, 2021 (1)

{{[[TODO]]}} could we use the same logic for cleaning up filenames so the urls are clean as well in [[export-html-pages]]?

January 4th, 2022 (6)

since this is getting so wide, i wonder how the generated html pages via [[export-html-pages]] will look like - i'd actually prefer if there was no wrapping and you could just scroll horizontally. will see soon once the export goes live
e.g. instead of [[roam-traverse-graph]] [[export-html-pages]], i could have a page titled "export-html-pages-plugin-of-roam-traverse-graph" or smthn, i don't yet know what'd be the optimal naming convention, but we could try to figure it out.
- i've even seen some people on [[roam]]'s [[(hidden) VZrbM9KJQ]] talk about some conventions
[[roam-traverse-graph]] [[export-html-pages]]
- thinking about how you can e.g. do in [[roam]]:
  - ```javascript - further: - link - link```
  - vs ```javascript - further: link - further: link```
- and how you could do that with linked references, if you were doing it:
  - ```javascript - [[further]]: - link - link```
  - vs ```javascript - [[further]]: link - [[further]]: link```
- {{[[TODO]]}} would [[roam attributes]] work better for this?
  - i.e., you'd do the mentioning twice probably, like in the second part of either examples
    - thought is that necessary? i think it's irrelevant actually
  - initial thought - no, because the `(hidden) G97ohL3l8::` is in the end, and you'd have to manually write out the page's title instead of being able to search
    - but wait, i never really use attributes, and that's not right! you can do `(hidden) G97ohL3l8::` and roam throws you in the beginning, and you can search just fine!
    - okay so then that's no longer a problem
  - next up - is this useful
  - re:: ((EfE5J1OtG))
    - why i thought it'd be useful is that you can only have one attribute per block. thus it'd force you to have more specific (verbose?) page titles instead of combining multiple ones:
      - e.g. instead of [[roam-traverse-graph]] [[export-html-pages]], i could have a page titled "export-html-pages-plugin-of-roam-traverse-graph" or smthn, i don't yet know what'd be the optimal naming convention, but we could try to figure it out.
        
        i've even seen some people on [[roam]]'s [[(hidden) VZrbM9KJQ]] talk about some conventions
      - but the main question here is -- is this overall a good thing?
- {{[[TODO]]}} #observation am i using attributes wrong?
  - {{[[TODO]]}} more complex attribute handling in [[roam-traverse-graph]]
    - ```javascript {{[[TODO]]}} ~~observation::~~ #observation am i using attributes wrong?```
  - or maybe like this? XD
    - observation:: {{[[TODO]]}} am i using attributes wrong?
      - {{[[TODO]]}} would need some extra integration help w/ the [[TODO]] toggle from [[roam]]
  - {{[[TODO]]}} figure out what [[roam attributes]] are all about / what their purpose is
    - [again](((vssQKBfFO))), the learning material of datalog could help
    - {{[[TODO]]}} thought also interesting what the [[roam]] people intended with them
      - cc:: [[(hidden) 1h9jVJvM-]]
#observation people have been doing [[export-html-pages]]-like stuff for a while already!
- [[(hidden) zawAAHB3b]]
  - https://github.com/mathieudutour/gatsby-digital-garden/issues/31#issuecomment-752807330
    - https://github.com/roam-garden/roam-export/tree/757a777aac27777021f3ebab3c073893d7884951
    - https://github.com/nikvdp/roam2agora
      - {{[[TODO]]}} checkout [[(hidden) jZNl6HGob]]
        
        https://anagora.org/index
    - [[(hidden) X3vwrXyD7]]
      - https://github.com/dvargas92495/generate-roam-site-action
        
        #observation oh snap, they're doing everything __directly in [[roam]]__, and then using [[lambda functions]] ([[(hidden) g2-_urXV9]]/[[(hidden) _Ekrn0YvL]] or whatever)
        
        further https://github.com/dvargas92495/generate-roam-site/blob/main/src/index.ts
        
        further https://github.com/dvargas92495/roamjs-components
- [[(hidden) zJw7j5jxr]] holy shit, so much thoughts coming from this
  - (hidden) b7GCT2svs:: "The Killers - Mr. Brightside (Lyrics)" ("it was just a kiss")
    - https://youtu.be/UFKf08us2AI
  - [[roam-traverse-graph]] [[export-html-pages]]
    - thinking about how you can e.g. do in [[roam]]:
      - ```javascript - further: - link - link```
      - vs ```javascript - further: link - further: link```
    - and how you could do that with linked references, if you were doing it:
      - ```javascript - [[further]]: - link - link```
      - vs ```javascript - [[further]]: link - [[further]]: link```
    - {{[[TODO]]}} would [[roam attributes]] work better for this?
      - i.e., you'd do the mentioning twice probably, like in the second part of either examples
        
        thought is that necessary? i think it's irrelevant actually
      - initial thought - no, because the `(hidden) G97ohL3l8::` is in the end, and you'd have to manually write out the page's title instead of being able to search
        
        but wait, i never really use attributes, and that's not right! you can do `(hidden) G97ohL3l8::` and roam throws you in the beginning, and you can search just fine!
        
        okay so then that's no longer a problem
      - next up - is this useful
      - re:: ((EfE5J1OtG))
        
        why i thought it'd be useful is that you can only have one attribute per block. thus it'd force you to have more specific (verbose?) page titles instead of combining multiple ones:
        
        e.g. instead of [[roam-traverse-graph]] [[export-html-pages]], i could have a page titled "export-html-pages-plugin-of-roam-traverse-graph" or smthn, i don't yet know what'd be the optimal naming convention, but we could try to figure it out.
        
        i've even seen some people on [[roam]]'s [[(hidden) VZrbM9KJQ]] talk about some conventions
        
        but the main question here is -- is this overall a good thing?
    - {{[[TODO]]}} #observation am i using attributes wrong?
      - {{[[TODO]]}} more complex attribute handling in [[roam-traverse-graph]]
        
```javascript {{[[TODO]]}} ~~observation::~~ #observation am i using attributes wrong?```
- or maybe like this? XD
  
  observation:: {{[[TODO]]}} am i using attributes wrong?
  
  {{[[TODO]]}} would need some extra integration help w/ the [[TODO]] toggle from [[roam]]
- {{[[TODO]]}} figure out what [[roam attributes]] are all about / what their purpose is
  
  [again](((vssQKBfFO))), the learning material of datalog could help
  
  {{[[TODO]]}} thought also interesting what the [[roam]] people intended with them
  
  cc:: [[(hidden) 1h9jVJvM-]]
- {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] if [[roam]] could provide a hooks/events api that you could listen from,
  - then the stuff that people are doing directly on roam, and we do in our runner locally / on github actions with [[roam-traverse-graph]] -- we could do all that in a remote environment as well, __but with much faster time intervals__ - they wouldn't even be intervals anymore, rather - reactions to events [1] happening live, as the user acts.
    - [1] in [[(hidden) xH-Ph8S9m]], it's [[(hidden) Vr3N0zG5Q]] isn't it?
    - (hidden) AV7J4zqkD:: ((YG-4tevRA))
    - this would likely require [[(hidden) BislYexyN]]s - detecting if changes have side effects that impact not only the edited block, but the whole page, or even the whole graph / parts of it
      
      (hidden) AV7J4zqkD:: linking to a page - both pages need updating now
      
      and if it's a meta page / has powers, then extra works to potentially any pages in the graph.
      
      i.e. annoying stuff!
      
      idk, maybe if we manage to keep the stuff fast, like it is now [1], then going thru the whole graph shouldn't be as bad?
      
      e.g. we could have a queue of incoming events, and we'd only do 1 at a time, and if a new one comes in too fast, we'd wait for the currently one to complete, and in the meantime if more come in, we'd discard all the new ones except the newest, and then could go again.
      
      [1] it takes ~5 seconds? to go from a `notes-private/graph.json` into a `notes-public/*.html`
      
      and probably ~20 seconds when i introduce the stuff from the [[(hidden) nicjeov_l]] branch which is currently WIP.
      
      ((yxHMW9jlb))
      
      ofc there's a lot of [[(hidden) BislYexyN]]s to be done, it's currently fairly naive. and, they seem more doable / easier than the side effect detection:
      
      ((RpqCi8rWX))
      
      both assume 1. my size of the graph (1K pages, 8K words)
      
      ((FI6sCM5cI))
      
      ((xUKym_BXn))
      
      ((gf1mkreMz))
      
      ((spuKqLoxE))
      
      ((m1Fk_dVUP))
- {{[[TODO]]}} datalog query builder w/ live preview, directly in [[roam]]?
  - maybe first gotta go thru the learning material above, lol
- since this is getting so wide, i wonder how the generated html pages via [[export-html-pages]] will look like - i'd actually prefer if there was no wrapping and you could just scroll horizontally. will see soon once the export goes live
- observation:: putting everything inside daily notes, vs referencing today's date in a specific page / block
  - if the page is public, but your daily notes aren't, then the stuff will also be public
    - but wait this is irrelevant because if using linked a linked reference which makes the stuff public, then it's the same effect, it juts ends up in the linked references of a page instead of directly inside it. [[duh]]!
      
      {{[[TODO]]}} wait but i'm still confused myself now on how does the public vs public recursive logic work in [[roam-traverse-graph]] lol - is making a page "public" makes it public recursive as well?
[[roam-traverse-graph]] [[export-html-pages]]
- re: parsing AST - #watch "Monoidal Parsing—Edward Kmett"
  - https://www.youtube.com/watch?v=Txf7swrcLYs
  - from https://www.reddit.com/r/rust/comments/9ij2p7/do_you_like_the_rust_syntax/e6kay69/
    - from "why learn [[(hidden) KMBIAt8MO]] for [[(hidden) d_BU9kVtB]] developers" (couldn't find the meme on [[(hidden) 3uMj-Ki8x]] though)
      - from [[(hidden) mtMPoV2M4]] @ [[(hidden) S-ygYfi0j]]'s [[(hidden) VZrbM9KJQ]]
        
        https://pipedrive.slack.com/archives/C024G6CBP/p1641293440337200
[[roam-traverse-graph]] [[export-html-pages]]
- in the AST parsing, extracting links out of text as separate things ("begin" and "end") because will be used w/ e.g. an `a` tag

January 5th, 2022 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} what's happening with the ordering of linked mentions? lol
  - cc:: ((beLdGUUuT))
  - (hidden) pfjyTGHet #[[(hidden) 7c2C8PgIV]]
    - {{[[TODO]]}} (hidden) ozvPuo0Nb [[(hidden) BC3_6P1lo]]

the question of using a custom domain vs github pages (1)

parent:: [[export-html-pages]]

January 6th, 2022 (5)

(hidden) gMHHeC8kL [[export-html-pages]]
- {{[[TODO]]}} (hidden) kRLHA3mZU
  - (hidden) t2qMGRgpn [[(hidden) tYWs3ih5V]]
  - (hidden) ym0gQ9Nlu
    - (hidden) UXHYBRAi3
      - (hidden) JoMguI-IG
    - (hidden) 8qnli-A6I
  - (hidden) bRlfUp2jy
- (hidden) qbG5bn1U4
re:: `publicRecursive` tag @ [[export-html-pages]]
- maybe instead of `publicRecursive`, we need to make it a point that the purpose of this is to have everything in daily notes, and under that tag, blocks become public and end up in the page as a linked mention.
  - so that it'd be made clear that this is the purpose of it, and not a general `publicRecursive` meta-tag. then, we'd be able to very easily detect if something is a "page collector" or whatever better name we come up with, and then e.g. the coloring stuff becomes way more precise
    - {{[[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?)
      - cc:: [[roam "enterprise"]]
    - re:: ((wiW41Si-y))
      - #[[(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]]}} is [[re]] an [[anti-pattern]]? i.e. it becomes unclear if what you are "referring to" is from the content above, or some other page (if it's not a linked ref (of a page or a block) and just text) - you might start looking at the previous content but not find the thing that i meant to refer to, or even worse - could find something that is actually not the thing, and then get further confused. idk idk
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!
- cc:: [[(hidden) zJw7j5jxr]]? or at least [[(hidden) EPYV31rY-]]
[[export-html-pages]]
- {{[[TODO]]}} would be interesting to explore connected relationships, even if the pages do not directly reference themselves, but e.g. like here w/ (re)discover & algebraic effects - they're in the same block
  - re:: ((crag_e60m))
    - 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!
      - cc:: [[(hidden) zJw7j5jxr]]? or at least [[(hidden) EPYV31rY-]]
- re:: coloring public blocks' lines
  - {{[[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?
    - ok some blocks are obv. longer than others so maybe wouldn't look good the diagonal part (the vertical part -- all good regardless), and a completely horizontal line to go from one level to another would be fine?
      - or maybe it's fine actually. would have to test it out & [[see what feels better]]
  - {{[[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.
      - [[philosophical question]] (because [[bus factor (tbd)]]) if this is a good #[[(hidden) jOMmlCP4S]] or not.
        
        as long as it's static html w/ everything inlined, so that if anything goes down, you're still good - then maybe not too bad?
        
        cc:: [[the question of using a custom domain vs github pages]]
        
        re:: [[(hidden) _d7I12UTL]]
        
        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?
        
        [[(hidden) DY6wPnICE]]
        
        [[roam]] as the personal "[[(hidden) pCdH3SJhT]]" / no-code / automations platform???
        
        re:: "no-code" - lol, ofc you'd have to code up the [[(hidden) AqlNqCYG6]]s, but then you can share them and use them and everything's directly in roam. fuuuuuuuck this is [[(hidden) -MiVLWUzx]]
        
        (hidden) D1lY0CG5e:: {{[[TODO]]}} ideally you'd be able to [[self-host]] [[roam]] because at this point you'd be [[running critical infrastructure]]
        
        cc:: [[roam "enterprise"]]
        
        thought beware -- remain user-focused, never [[(hidden) 6jcY_WnAD]], [[you gotta zuck'em]], stay [[(hidden) EJItNRkJG]], do not give power to the [[professional managerial class]]
        
        {{[[TODO]]}} okay more [[(hidden) jOMmlCP4S]]s coming in from thinking about this:
        
        re:: `publicRecursive` tag @ [[export-html-pages]]
        
        maybe instead of `publicRecursive`, we need to make it a point that the purpose of this is to have everything in daily notes, and under that tag, blocks become public and end up in the page as a linked mention.
        
        so that it'd be made clear that this is the purpose of it, and not a general `publicRecursive` meta-tag. then, we'd be able to very easily detect if something is a "page collector" or whatever better name we come up with, and then e.g. the coloring stuff becomes way more precise
        
        {{[[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?)
        
        cc:: [[roam "enterprise"]]
        
        re:: ((wiW41Si-y))
        
        #[[(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]]}} is [[re]] an [[anti-pattern]]? i.e. it becomes unclear if what you are "referring to" is from the content above, or some other page (if it's not a linked ref (of a page or a block) and just text) - you might start looking at the previous content but not find the thing that i meant to refer to, or even worse - could find something that is actually not the thing, and then get further confused. idk idk
        
        re:: [[creating jira issues / sub-tasks from roam's TODOs]]
        
        {{[[TODO]]}} must avoid cluttering the raw UI of [[roam]].
        
        {{[[TODO]]}} as a minimum, could have an option to `onlyEnableUnderFollowingTags: []`, but this shouldn't be used an excuse to allow trashing the UI when the option matches and we are inside a specified tag
    - 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]]}} could have a selection to choose from, given that we'd already be parsing the other linked references to find out publicity & to do the coloring
    - {{[[TODO]]}} would need to have a predefined base url for the notes in the [[roam-traverse-graph-settings]] page.
      - observation:: hmm, a reason why you wouldn't want to have meta-tags (e.g. tags that make other tags have [[magic]])
  - {{[[TODO]]}}
- re:: custom domain - ((UUaQUFGpI))
  - hmmm hmm. now again i think non-breakage / longevity are higher prio than the possibility of losing control.
    - simply because who can be blamed if it goes wrong
    - & overall value(ability) of having it available vs controlling it
    - though, URLs are less [[/comfy/]] for sure. idk
[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} inlining [[github]] permalinks, much like people do in [[medium]] with [[github]]'s gists?
- {{[[TODO]]}} another #[[(hidden) jOMmlCP4S]] from the [[re]] attribute above - in the html, consider having previews of pages on hover.
  - must be done right though - i think [[wikipedia]] has a not bad UX for it
- {{[[TODO]]}} yet another #[[(hidden) jOMmlCP4S]] - directory-like history when exploring / going into pages? similar to the [[macos]]

thread (1)

the #[[(hidden) L_G_h4Jr_]] is that if you write new paragraphs, but related to the previous one, you tend to indent them, and the indentation continues so much, when it really shouldn't. the #[[(hidden) jOMmlCP4S]] i had for [[(hidden) -NklLsZCV]] when doing [[export-html-pages]] is that when you have a block that has children, but only 1, you can safely undo the indentation, as long as 1. the first (top-to-bottom) child that is not the only 1 child, is not being un-indented, and 2. to separate it out from the other children which are not related as much because you didn't originally indent them, you'd have to indent the 1 child.
- and this (specifically, (2)) is when i realized that something like a [[thread]] or [[(hidden) g2IT-5G5b]] would work well.

(hidden) qfvr4m1gA (1)

(hidden) GVz6_qmNA [[export-html-pages]] parent::

January 11th, 2022 (1)

(hidden) 7bEvNFyIs [[export-html-pages]]
- {{[[TODO]]}} (hidden) QY0GmCzHA [[(hidden) BfzxvGFk0]]
- (hidden) HvzrRI3v6

January 21st, 2022 (1)

(hidden) N-JiXMeEm [[export-html-pages]] [[roam]]

January 24th, 2022 (1)

(hidden) wSbFkfavN [[export-html-pages]]
- {{[[TODO]]}} (hidden) nzj1oetkj [[syntax highlighting]] [[github]] [[vscode]]
- (hidden) 4RvqfbYPc

January 29th, 2022 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] both [[roam]], and us, in the linked references / linked mentions of a page, only show __where we have been referenced__ (backlinks?). but, we never just give a list of the things __that we referenced__. of course, that's fine, because you can read the text & find all references.
  - but, this idea came when i was exploring [[roam's graph]]. it doesn't really give you much insight of the relations of things.
  - i have a few ideas. some -- with the [[parent]] & [[sibling]] attributes i've been using; others, probably more robust, because they'd be automatic -- by proximity of "related-ness" in text.
  - i'm still not sure what'd be best to visualize them, but simply playing w/ some visualizations i think will turn out very interesting, & by [[exploration]], good results could be found
  - 3D [[(hidden) J78K2glnu]]s, even 4D if time is the 4th, especially if one uses [[the "everything inside daily notes" approach to roam]], sound fun, though idk how possible and especially if valuable they'd be. worth a try tho!

February 2nd, 2022 (1)

(hidden) kVl0yLWDH [[export-html-pages]]
- {{[[DONE]]}} (hidden) 3t2iCnmw5
  - {{[[DONE]]}} (hidden) FQ0tjVqOT
  - {{[[DONE]]}} (hidden) 3Sed5u4gY
    - {{[[DONE]]}} (hidden) tts6froAr
      - (hidden) 2xqrjm0DR
    - (hidden) IAaF3wiWH
  - (hidden) VZq1R4KMd
- (hidden) aDA8LWvR6

February 4th, 2022 (1)

{{[[TODO]]}} (hidden) B20WndO8p [[export-html-pages]] #observation

the magic toggle (1)

parent:: [[export-html-pages]]

February 6th, 2022 (1)

(hidden) OeVfmCq1G [[export-html-pages]]
- {{[[TODO]]}} (hidden) 5AXvLIrD7
- (hidden) fkq2tNonc

February 10th, 2022 (1)

(hidden) Zr37ZcKhD [[export-html-pages]]
- {{[[TODO]]}} (hidden) WifqADuDq
  - (hidden) R09hzYe-V
  - (hidden) -hGYZe7pg
  - (hidden) PDNcCbZtS
- (hidden) S9aVSuw93

February 14th, 2022 (1)

(hidden) m4Kd24nRH [[export-html-pages]]
- {{[[TODO]]}} (hidden) 9Q0IgMcrr

March 21st, 2022 (1)

{{[[TODO]]}} (hidden) _MAWOhokz [[export-html-pages]] [[git]]

TODO (1)

see also [[roam-traverse-graph]] / [[export-html-pages]]

July 9th, 2022 (1)

nice format. cc [[roam-traverse-graph]] [[export-html-pages]]

3D graph of outgoing & incoming connections (1)

parent:: [[roam-traverse-graph]] [[export-html-pages]]

July 28th, 2022 (2)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} change URLs (thus filenames) of daily notes pages - use their `id` from roam, because already fits what's needed -- YYYY-MM-DD, no spaces
  - because current URL is very ugly w/ spaces!
    - e.g. for
      - `https://kiprasmel.github.io/notes/July 28th, 2022.html#[[(hidden) G97ohL3l8]]6QYFdIi0d`
      - it's
        
        https://kiprasmel.github.io/notes/July%2028th,%202022.html#[[(hidden) G97ohL3l8]]6QYFdIi0d
        
        ewww
  - #prereq
    - {{[[TODO]]}} figure out if it's possible to do redirects w/ github pages, so that we can avoid breaking existing links
      - if can, then we can easily build a list of redirects
        
        if not, then probably need to create a file for each of the existing daily notes page, and provide a redirect there w/ js + w/ html a href for a manual click if [[js]] disabled
[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} for runfull.sh, add a new env variable `FIXUP_LAST_DOWNLOAD` to fixup last commit in private-notes repo
  - in case u just downloaded, and cancelled the publishing, because made a few minor changes & want to re-run the whole thing, but w/o creating a new commit in private notes dir
    - actually, need to make it `FIXUP_LAST`, and amend the last commit in the public notes as well
- {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] on the right side in the top of the page, before we have a [[3D graph of outgoing & incoming connections]], we could simply show a list of the outgoing & incoming linked references
  - rendering logic would be exactly the same as is for the index.html page!
    - except for the wrappers like head, some in body.
      - everything else can abstract into a function
        
        would need to take in a list of linked references
        
        can use for both outgoing & incoming
        
        {{[[TODO]]}} not sure if i like the naming yet. seems opposite to what it should be (in vs out)
- {{[[TODO]]}} when we'll be implementing block-references, we have to have a way to detect self-referencing blocks, to prevent infinite rendering/expansion :D

August 8th, 2022 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} move out from gh pages to personal website host

October 14th, 2022 (1)

[[roam-traverse-graph]] [[export-html-pages]]
- {{[[TODO]]}} something's wrong w/ the script [[git-add-file-if-has-meaningful-changes]]
  - e.g.
    - https://github.com/kiprasmel/notes/commits/master/civilization.html
  - [[(hidden) YXzh9BHCa]]
    - {{[[DONE]]}} getting the correct DIRNAME & location of script
      - https://stackoverflow.com/a/24112741/9285308
        
```javascript DIRNAME="$(cd "$(dirname "${BASH_SOURCE[0]}")"; pwd -P)" printf "DIRNAME $DIRNAME\n" ```