How astraly-labs/pragma works
Project type and purpose
• This is primarily a Next.js‑based frontend and minimal backend (API routes) for the “Pragma” provable oracle ecosystem.
• It serves both a marketing site (static pages) and a dashboard (dynamic, data‑driven UI) that interacts with Starknet contracts and event streams.
File structure
• Top‑level:
• README.md, LICENSE, .gitignore – project metadata
• assets/, components/, path/ – legacy or shared helper code
• pragma-ui/ – the real Next.js application
• Inside pragma-ui/:
• pages/ – React pages and API routes (pages/api/...)
• src/app/ – Next.js App Router directory with (marketing) and (dashboard) sections
• src/components/, src/hooks/, src/lib/, src/services/, src/providers/ – UI components, utilities, data-fetching hooks, service abstractions
• src/abi/ – contract ABIs (ERC20, Oracle, etc.) for on‑chain calls
• public/assets/ – static Lottie JSON, videos, images
• Config files – package.json, tsconfig.json, tailwind.config.ts
README for additional insights
• Describes “Pragma” as a modular provable oracle built on Starknet
• Mentions related repos (contracts, indexer, SDK) – this repo is just the UI
Final advice
• Every logical layer without overcrowding: client, framework, services, blockchain, assets.
• Data flow paths (SSR, CSR, SSE, JSON‑RPC).
• Review pages vs. App Router to distinguish static vs. dynamic routes.
Happy diagramming!