feat(devtools): initial setup

[arashsheyda]

🔗 Linked issue

#2880

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

this PR adds support for sqlitie viewer inside devtools

note: this is the code that I had when I created the issue, just pushed it, honestly haven't work on it and it needs a lot of changes... (haven't tested the build as well)

@farnabaz what do we think about the directory structure?

a current demo:

Screen.Recording.2025-01-24.at.10.43.38.PM.mov

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15291502	Triggered	Generic Password	30bee78	pnpm-lock.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[farnabaz]

Thanks for the PR it looks great

The directory structure looks good to me 👍

I was wondering which one is more useful:

• Viewing the database
• Listing the files, show a markdown editor, and update database

WDYT?

/cc @larbish @atinux

[atinux]

Thanks for starting this @arashsheyda ❤️

I would rather see the list of content collections with the ability to update them with a Monaco editor (we plan to extract the MDC editor at one point so we could integrate it)

Not sure if the viewing the database is very helpfull here

[arashsheyda]

@farnabaz @atinux thanks! Ah yes, makes much more sense 😄