Issue 5 Mol Blog Weba Issue Notes
Establish Private vs. Public posts logic using Clerk.
Okay, how is frontmatter even parsed how cna we discriminators to it?
Now, we can get it where they can't SHOW it, we need to get it where, the user cannot see it at all and in order to do that we need to denote roles.
No Orgs just public metadata.
Okay, we got the Org functionality back because ig we NEED an org because this seems to be the only way to connote roles but this is a busted option because if we want to have a bunch of people comment then it's going to ruin the org, so I think we are just going to use private metadata.
...
Getting private metadata seems easy, here.
...
Hopefully I don't ruin this with bad code.
Aside: The invitation logic isn't working will for localhost using Clerk.
toDo: It's a good idea to add backup functionality for this in case someone wrongly turns on org functionality.
Turn off, org functionality.
The various roles in public metadata:
Okay, so the roles.
Commenter, Admin, Contributor
Start: Thu Mar 27 2025 19:52:44 CST
Aside: It would be dope, if I could include the git hash in here as well as the PR number, etc.
...
Trying to fix the ts-ignore issue with the MDXRemote component.
Notes on note taking,
What I should have done was been like what is and isn't the current state of the weba, we could've also take pictures of the weba and dated it, to know how it was because currently not sure how much of it works GREAT.
So, I tried to write out the ts-ignore, vibe coding it didn't work AT ALL, big waste of time, so need to think critically about it.