TheBuilderDAO / kafe

Kafe Learning Platform
https://dev.builderdao.io
MIT License
13 stars 13 forks source link

web 3 profiles with near and ceramic #207

Open ALuhning opened 2 years ago

ALuhning commented 2 years ago

Guide Outline

Learn to integrate NEAR Personas in your applications. Built with Ceramic/NEAR, you can access a data object with information about your users and users can manage their personas in one location and have changes propagate everywhere

Link to Proposal

https://dev.builderdao.io/vote/web-3-profiles-with-near-and-ceramic

Comments

Testing publishing process

changeset-bot[bot] commented 2 years ago

⚠️ No Changeset found

Latest commit: bddcfa178938f6e1a38b616f6afb375eb56f7d2a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel[bot] commented 2 years ago

@ALuhning is attempting to deploy a commit to the BuilderDAO Team on Vercel.

A member of the Team first needs to authorize it.

vercel[bot] commented 2 years ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
docs ✅ Ready (Inspect) Visit Preview May 30, 2022 at 10:54AM (UTC)
kafe ✅ Ready (Inspect) Visit Preview May 30, 2022 at 10:54AM (UTC)
github-actions[bot] commented 2 years ago

:open_book: Tutorial Details

ID: 221
SLUG: web-3-profiles-with-near-and-ceramic

REVIEWER1: pyr0gan REVIEWER2: paulpomerleau See :scroll: Proposal

Necmttn commented 2 years ago

@ALuhning your branch is currently behind the upstream, you can sync your fork quickly via; https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork 🙌

pyr0gan commented 2 years ago

@ALuhning your branch is currently behind the upstream, you can sync your fork quickly via; https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork 🙌

Does this need to happen before we merge @Necmttn ?