GitHub Hot Board

GitHub Hot Board · Archivo del repositorio

fxhash/fxhash-website

fxhash front-end, nextjs (Esta descripción procede del propio repositorio.)

Datos al October 27fxhash

Mejor puesto

#51

Gemas ignoradas

100

Estrellas totales

52

Forks totales

4

Días en rankings (30 d)

Estado del proyectoLicencia: desconocidoÚltimo push: October 15Issues abiertos (PR incl.): 54

Recolectado desde 2026-10-25; desconocido = aún no recopilado

Pon la insignia en tu README · fxhash/fxhash-website[![Pon la insignia en tu README](https://git.vaiox.xyz/api/badge/fxhash/fxhash-website.svg)](https://git.vaiox.xyz/es/repo/fxhash/fxhash-website)

Badge · 任何仓库都可以挂 —— 未上榜的仓库显示灰章,上完榜会自动点亮。

<a href="https://git.vaiox.xyz/es/repo/fxhash/fxhash-website"><img src="https://git.vaiox.xyz/api/badge/fxhash/fxhash-website.svg" alt="Pon la insignia en tu README" height="20"></a>

Documentación del proyecto

fxhash front-end

This project is the front-end of fxhash. The front-end uses Nextjs, a React framework. If you want to contribute, being familiar with React might be required. However, Nextjs is pretty easy to pick-up knowing React ! Just get familiar with the basic concepts in their doc and you're good to go.

Installation

git clone https://github.com/fxhash/fxhash-website

Go to the project directory

npm install
# or
yarn install

Warning

The front-end is set up to run against the main fxhash API and the contracts on the mainnet so BE CAREFUL. If you buy a token using this front-end running on your local machine using your wallet, it will be as if you ran the same operation on the official website.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

How to contribute

You can find opened issues on the https://github.com/fxhash/fxhash-website/issues tab. If you want to implement a feature, please check first if an issue is opened and see what needs to be implemented in that regard. If no issue is opened, feel free to implement your feature as you wish.

Workflow

  • fork the dev branch of this repo
  • create a branch to implement a feature or fix a bug
  • when done, push the branch to your git repository fork
  • create a pull request againts the dev branch
  • the team will review it, and either request changes or merge it

If you find a bug with the front end, you can create an issue.

Branch naming convention

  • feature/_: add a feature
  • change/_: a change on a particular feature
  • bug/_: fix a bug

Stack used

Project structure

  • /articles [deprecated]: markdown files, generated in html at build time, they populate the about tab of the website
  • /components: reusable components used multiple times in the app
  • /containers: bigger building block components. They often use multiple components and have some more complex logic
  • /context: react context
  • /doc: the articles from the doc - website doc is derived from this folder
  • /hooks: react hooks
  • /pages: the different pages of the website (see nextjs doc)
  • /queries: graphQL queries (not all of them are in there, to be done)
  • /services: modules to interact with external services
  • /styles: the generic styles of the app
  • /types: type definitions
  • /utils: general-purpose utility functions

Clasificaciones actuales

  • 51

    Gemas ignoradas

    100 estrellas · 52 fork · Star acumuladas (ascendente)

    Ignoradas →

Evolución de los últimos 30 días

Estrellas acumuladas

Evolución del puesto

Ganancia diaria

Vecinos de ranking en el mismo tablero · Ignoradas

← Volver a los rankings