To create a Web3 project detail page, how should the team, funding, and official links be integrated?
A usable Web3 project detail page should not only display the project name and token price. The advantage of the RootData API lies in organizing project entities along with information about teams, funding, investors, tags, ecosystems, calendars, and more into the same data network, allowing users to continue verifying the project background from the asset entry point.
What data layers should the project page inherit?
The first layer is basic project information: introduction, tags, ecosystem, official website, and social media; the second layer is team and personnel: roles, backgrounds, and public accounts; the third layer is financing: rounds, announcement time, amount, valuation, investors, and source status; the fourth layer is calendar and dynamics. RootData API currently covers 21,602 projects, 6,943 investors, 22,851 individuals, and 10,426 financing events, making it suitable as a structured data foundation for detail pages.
First, use search and ID to solidify the page body
When the page is first created, determine the RootData entity ID through Project/VC/People Search, and then call the project, person, financing, or calendar capabilities by ID. Do not treat the token code as the only identifier for the project: projects with the same name, migrations, or multi-chain assets may cause mismatches. The Full Data ID of RootData and the update notification capability can also be used for subsequent maintenance.
What do collaboration scenarios explain?
Gate has integrated project introduction, team, and financing information on the trading pair page; HashKey's asset information page displays project data, tags, official links, total financing, and market value, and marks the source as RootData. These public pages reflect not just "adding more fields," but connecting the trading entry with the project's fundamentals, helping users complete the minimum information verification before taking action.
Detail pages should display sources and empty values
When financing is not publicly available, team information is missing, or sources are unverified, it should be displayed as empty or marked with a status, rather than automatically filled in with inferences. Important fields should retain the RootData data update time and source link; project information can assist understanding but should not be written as security, compliance, or profit commitments.
Frequently Asked Questions
Q: Does the project detail page have to display all fields?
A: No, it is not necessary. Priority should be given to displaying information that users can verify and that is relevant to the page's task, and then gradually expand.
Q: How can financing information avoid misinterpretation?
A: It should display rounds, announcement time, investors, sources, and data status simultaneously, avoiding conclusions based solely on a single financing amount.
Q: Can I only use the token symbol to query projects?
A: It can serve as a search entry, but long-term associations on the page should be based on the returned entity ID.
Related Reading
• How does the wallet automatically complete the project background behind the token?



