graph-node VS Tailwind CSS

A subgraph according to The Graph (which is a decentralized protocol for indexing and querying blockchain data) is a custom API built on blockchain data. They are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI.

Event is a log entity which EVM smart contracts can emit during transaction execution. Events are very good at signalling that an some action has taken place on-chain. Applications can subscribe and listen to events to trigger some off-chain logic or they can index, transform and store events in some off-chain storage (look at The Graph protocol or Ethereum ETL).

Subgraph cloned from repo :https://github.com/graphprotocol/graph-node/tree/master/docker

https://github.com/scaffold-eth/scaffold-eth-2 this repo comes with wagmi and hard hat preconfigured you can use it as a sample , but if you are large querying data I would advise you the graph https://thegraph.com/

The Graph

There are also decentralized network services like The Graph or Pocket Network that provide decentralized access to Ethereum and other blockchain networks. Note that these services primarily provide APIs for querying blockchain data, and may not provide full functionality for sending transactions or executing smart contracts like a full Ethereum node or services like Infura and Alchemy.

For read-only the way to use The Graph

See it for yourself.

thegraph.com is the only site operated by The Graph Foundation, and is the centrepiece for all activity on the protocol. Can a website/web dApp be hacked? Yes. Has it been hacked in the past two years since it launched? No.

Check out TheGraph, most of DEX has a subgraph indexing data

Lastly, Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.