Skip to content

A collaborative repository featuring community-contributed guides for developing on zkSync Era.

License

Apache-2.0, MIT licenses found

Licenses found

Apache-2.0
LICENSE-APACHE
MIT
LICENSE-MIT
Notifications You must be signed in to change notification settings

zkSync-Community-Hub/community-code

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Community Code

License License: Apache 2.0 Contributor Covenant Contributions Welcome X (formerly Twitter) Follow

Welcome to the ZKsync Community Code repository. This project serves as the community hub for ZKsync, providing comprehensive documentation for developers written by developers. Whether you're a beginner looking to get started with ZKsync or an experienced developer seeking advanced guides, you'll find the resources you need here.

πŸš€ Quick Start

  1. Install Bun: Follow the installation instructions.

  2. Install Dependencies:

    bun install
  3. Run Locally: Start the development server at http://localhost:3000.

    bun run dev

πŸ› οΈ Built With

Local Preview πŸ‘€

To locally preview the production build, first run bun run build to build the project, then run the following:

bun run preview

Lint & Formatting ✨

This project provides lint commands to check the project.

Run CI Checks βœ”οΈ

This command will run all of the lint commands together.

bun run ci:check

Markdown Linting πŸ“

Markdown files are found in the /content directory. The following lint commands will run within that directory:

bun run lint:spelling
bun run lint:markdown

Linting 🧹

The following commands are available to run code linting on the project:

bun run lint:prettier
bun run lint:eslint

πŸ“œ Conventional Commits

We follow the Conventional Commits specification. Make sure your commit messages adhere to these guidelines.

For documentation changes, we recommend using the "docs:" tag. For example:

git commit -m "docs: fix spelling error"

🀝 Contributions

We welcome contributions from the community! Check out our Contributing guide to learn how to add your own guides to Code Community.

πŸ‘ͺ Join the community

If you haven't already, join our community! We have GitHub Discussions for developers to ask questions and share their work. We also have a Discord server for real-time conversations with the team and community.

Be sure to follow us on Twitter to keep up to date with announcements from the ZKsync dev team.

About

A collaborative repository featuring community-contributed guides for developing on zkSync Era.

Topics

Resources

License

Apache-2.0, MIT licenses found

Licenses found

Apache-2.0
LICENSE-APACHE
MIT
LICENSE-MIT

Code of conduct

Stars

Watchers

Forks