Skip to content

verify&access run local with docker and next.js setup#1489

Open
bogacyigitbasi wants to merge 6 commits intomainfrom
verify-access-tutorial
Open

verify&access run local with docker and next.js setup#1489
bogacyigitbasi wants to merge 6 commits intomainfrom
verify-access-tutorial

Conversation

@bogacyigitbasi
Copy link
Collaborator

Purpose

Created a tutorial to show how to setup a verify&access tutorial utilizing the verification web-ui and ZK proofs.

Changes

Checklist

  • My code follows the style of this project.
  • The code compiles without warnings.
  • I have performed a self-review of the changes.
  • I have documented my code, in particular the intent of the
    hard-to-understand areas.
  • (If necessary) I have updated the CHANGELOG.

CLA acceptance

_Remove if not applicable.

By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0

@dragosgd dragosgd added the preview Trigger a documentation preview for a PR. label Mar 3, 2026
@github-actions
Copy link

github-actions bot commented Mar 3, 2026

PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://developer.concordium.software/pr-preview/pr-1489/

Built to branch gh-pages at 2026-03-03 10:26 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Copy link
Contributor

@dragosgd dragosgd left a comment

Choose a reason for hiding this comment

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

I fixed the mermaid problem by adding an extension, will commit if that's ok.
Regarding the tutorial overall, content is good, comprehensive, but it's very difficult to follow as is, it's 1.5k lines in 1 article. I'd change the structure.
I suggest breaking it up in subarticles, my suggestion is:

  • Entrypoint: intro description, Table of Contents, What You'll Build , Disclaimer, what this tutorial provides, Prerequisities, Resources; regarding the table of contents, it's huge, it takes up more than the entire screnn, you could maybe reduce the x.0 points if you agree;
  • Subarticle 1: Project setup, Running the verifier service , Setting up WalletConnect
  • Subarticle 2: Integrating the Verification UI (it'd be great to have a page dedicated to this bit),
  • Subarticle 3: Requesting additional proofs, Testing, What You've built/learned

@bogacyigitbasi
Copy link
Collaborator Author

Agreed, will decompose and give it a try again.

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

Labels

preview Trigger a documentation preview for a PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants