Skip to content

FEE-86 Roam guides01#1217

Open
KarolaKirsanow wants to merge 20 commits into
DiscourseGraphs:mainfrom
KarolaKirsanow:roam-guides01
Open

FEE-86 Roam guides01#1217
KarolaKirsanow wants to merge 20 commits into
DiscourseGraphs:mainfrom
KarolaKirsanow:roam-guides01

Conversation

@KarolaKirsanow

@KarolaKirsanow KarolaKirsanow commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

This PR adds a first draft of the "Track your projects & experiments" guide for the roam research plugin, now using the canonical styling & file mgmt. Opening for visibility as I add image captions and correct typos, etc.

@vercel

vercel Bot commented Jul 10, 2026

Copy link
Copy Markdown

@KarolaKirsanow is attempting to deploy a commit to the Discourse Graphs Team on Vercel.

A member of the Team first needs to authorize it.

@KarolaKirsanow KarolaKirsanow added the documentation Improvements or additions to documentation label Jul 10, 2026
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

An error occurred during the review process. Please try again later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@KarolaKirsanow

KarolaKirsanow commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

2 notes:

  • There is some duplicate material now that the long-lost "experiment tracking" guide has been rediscovered but afaict there is no conflicting information.
  • the canonical node tag styling matches the Obsidian app styling, but not the colors used in the roam research template lab, which afaict were inherited from the MatsuLab graph in the mists of time. Flagging to solicit any Expressions of Personal Preference.
image

@KarolaKirsanow
KarolaKirsanow marked this pull request as ready for review July 14, 2026 16:50
@graphite-app

graphite-app Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

PR size/scope check

This PR is over our review-size guideline.

  • Recommended: ~200 lines changed
  • Acceptable limit: up to 400 lines when well-scoped/self-contained
  • Preferred file count: fewer than 5 files

Please split this into smaller PRs unless there is a clear reason the changes need to land together.

If keeping it as one PR, please add a brief justification covering:

  • What single problem this PR solves
  • Why the files/changes are coupled

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

Open in Devin Review

Comment thread apps/website/content/obsidian/use-cases/build-utilize-personal-knowledge-base.mdx Outdated
@mattakamatsu

Copy link
Copy Markdown
Contributor
  • Flagging to solicit any Expressions of Personal Preference.

I strongly recommend that we group similar node types with similar colors -- that reduces cognitive overhead by a significant amount, and encourages people to think of eg EVD as semantically equivalent to RESult

https://mira-science.github.io/schema/schema-explainer.html
image

image

res-candidate -> reddish
iss-candidate (are we calling it req-candidate now?) -> blueish

@KarolaKirsanow

KarolaKirsanow commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

I am inclined to prefer the restricted range of colors used in the template lab (possibly excluding the "caveat", which is not a canonical node atm).
image

@mdroidian Atm the colors in the obsidian documentation accurately reflect the defaults in the obsidian app; could we add another set of pill stylings targeting website/content/roam to match the roam app?

(2) ['discourse-graph/nodes/Hypothesis', '00eb1b']
(2) ['discourse-graph/nodes/Result', 'd10000']
(2) ['discourse-graph/nodes/Claim', '48df34']
(2) ['discourse-graph/nodes/Question', 'e9cd16']
(2) ['discourse-graph/nodes/Evidence', 'fb1313']
(2) ['discourse-graph/nodes/Issue', '2b00ff']
(2) ['discourse-graph/nodes/Source', '7a7a7a']
(2) ['discourse-graph/nodes/Caveat', '9d78d9']

mdroidian commented Jul 22, 2026

Copy link
Copy Markdown
Member

I checked the current defaults. Roam and Obsidian both ship Question, Claim, Evidence, and Source-not the eight-node set above. Question, Claim, and Evidence already use the same colors in both apps and the docs. Source is the only default mismatch: Roam uses #9E9E9E, while Obsidian and the docs use #3B82F6. The eight colors you posted don’t appear in the codebase.

I would much prefer if we kept to a single default color list, unless we have a strong reason for maintaining multiple separate colors lists.

Related, I created: FEE-876 but maybe we should create a ticket to discuss aligning on a larger set that includes [[HYP]], [[RES]], [[ISS]], and Caveat?

@KarolaKirsanow

Copy link
Copy Markdown
Contributor Author

I checked the current defaults. Roam and Obsidian both ship Question, Claim, Evidence, and Source-not the eight-node set above. Question, Claim, and Evidence already use the same colors in both apps and the docs. Source is the only default mismatch: Roam uses #9E9E9E, while Obsidian and the docs use #3B82F6. The eight colors you posted don’t appear in the codebase. I would much prefer if we kept to a single default color list, unless we have a strong reason for maintaining multiple separate colors lists.Related, I created: FEE-876 but maybe we should create a ticket to discuss aligning on a larger set that includes [[HYP]], [[RES]], [[ISS]], and Caveat?

Great - I opened FEE 878 to ringfence that convo. I believe that this PR should be ready to merge if the content meets approval (the styling Q was a sidebar)

@KarolaKirsanow KarolaKirsanow self-assigned this Jul 23, 2026
@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
discourse-graph Ready Ready Preview, Comment Jul 24, 2026 2:42pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants