Need a better configuration structure

[fewensa]

degov/degov.yml

Lines 27 to 37 in 83e38c8

	faqs:
	- question: What is DeGov.AI?
	answer: https://docs.degov.ai
	- question: How is AI integrated into DeGov.AI?
	answer: https://docs.degov.ai/faqs/#how-does-degovai-utilize-ai-capabilities
	- question: What's the difference between DeGov.AI and Tally?
	answer: https://docs.degov.ai/faqs/#whats-the-difference-between-degovai-and-tally
	- question: Is DeGov.AI secure?
	answer: https://docs.degov.ai/faqs/#is-degovai-secure
	- question: How can I create or vote on proposals?
	answer: https://docs.degov.ai/faqs/#how-can-i-create-or-vote-on-proposals

custom:
  theme:
    logo: ...
  faqs:
    - question: ...

[fewensa]

After modification, you need to adjust the schema at the same time

ringecosystem/degov-registry#39

[fewensa]

I reviewed the current degov.yml on main together with all 21 DAO configs in ringecosystem/degov-registry/daos, and I think the next step should be to reorganize the config by responsibility instead of continuing to extend the current flat structure.

The current schema already has a stable core, but it mixes several different concerns at the same level:

• DAO identity and public entry URLs
• governance runtime config (chain, indexer, contracts)
• external services (wallet, aiAgent, analytics)
• UI/product extensions (theme, apps, FAQs, treasury extras)

The clearest structural issue is that theme currently contains both branding assets and content like faqs. Those should not live in the same section.

There are also two smaller consistency issues:

• siteUrl, offChainDiscussionUrl, and editLink are first-party workflow URLs, but links is mostly external/community links
• governorToken is already an object, while governor and timeLock are still raw strings

From the registry side, the pattern is pretty clear:

• present in 21/21: name, code, logo, siteUrl, offChainDiscussionUrl, editLink, description, links, wallet, chain, indexer, aiAgent, contracts
• optional but common: analysis 19/21, theme 10/21
• optional extensions: apps 6/21, treasuryAssets 4/21, safes 4/21
• only 4/21 currently define FAQ content, and all of that is nested under theme
• only 1/21 currently uses apps[*].params

So I think the next schema direction should be something like this:

dao:
urls:
branding:
links:
services:
chain:
governance:
treasury:
ui:

For example, the current demo config could be reorganized like this:

dao:
  name: DeGov Demo DAO
  code: degov-demo-dao
  description: |
    It's a demo DAO for developers and users to experience DeGov's features, including the
    latest innovations features like AI agents, token wrapping, and more. The DAO is built
    on the Darwinia chain, an Ethereum-compatible chain.

urls:
  app: https://degov-dev.vercel.app
  discussion: https://github.com/ringecosystem/degov/discussions
  editConfig: https://github.com/ringecosystem/degov/blob/main/degov.yml

branding:
  logo:
    default: https://pbs.twimg.com/profile_images/1912415584257474560/GznnScP3_400x400.jpg
    light: https://raw.githubusercontent.com/ringecosystem/degov-registry/refs/heads/main/assets/logos/demo-light.svg
    dark: https://raw.githubusercontent.com/ringecosystem/degov-registry/refs/heads/main/assets/logos/demo-dark.svg
  banner:
    desktop: https://raw.githubusercontent.com/ringecosystem/degov-registry/refs/heads/main/assets/banners/demo.jpg
    mobile: https://raw.githubusercontent.com/ringecosystem/degov-registry/refs/heads/main/assets/banners/demo-mobile.jpg

links:
  coingecko: https://www.coingecko.com/en/coins/ringdao
  website: https://degov.ai
  twitter: https://x.com/ringecosystem
  discord: https://discord.gg/RingDAO
  telegram: https://t.me/RingDAO_Hub
  github: https://github.com/ringecosystem/degov
  email:

services:
  walletConnect:
    projectId: faf5e91ac5ed4d0a94d2648a6fcc9daa
  aiAgent:
    endpoint: https://agent.degov.ai
  analytics:
    ga:
      tag: G-XXXXXXXXXX

chain:
  id: 46
  name: Darwinia Network
  logo: https://pbs.twimg.com/profile_images/1742030786495500288/merX__YL_400x400.jpg
  rpcs:
    - https://rpc.darwinia.network
  explorers:
    - https://explorer.darwinia.network/
  nativeToken:
    symbol: RING
    decimals: 18
    priceId: darwinia-network-native-token
    logo: https://assets.coingecko.com/coins/images/9443/standard/RING.png

governance:
  contracts:
    governor:
      address: "0xC9EA55E644F496D6CaAEDcBAD91dE7481Dcd7517"
    governanceToken:
      address: "0xbC9f58566810F7e853e1eef1b9957ac82F9971df"
      standard: ERC20
    timeLock:
      address: "0x6AB15C6ada9515A8E21321e241013dB457C8576c"
  indexer:
    endpoint: https://indexer.degov.ai/degov-demo-dao/graphql
    startBlock: 5873342
    rpc: wss://rpc.darwinia.network
    gateway:
    finalityConfirmation: 50
    capacity: 30
    maxBatchCallSize: 200
    endBlock:

treasury:
  assets:
    - name: FT
      contract: "0x3ff4F23F328664FfD046eb4ca62be3d8aF3e452f"
      standard: ERC20
      priceId: FT
      logo:
  safes:
    - name: Test DAO Safe(Arbitrum)
      chainId: 42161
      link: https://app.safe.global/home?safe=arb1:0x80d180621B2f875269216f19A499e6fB9402776C

ui:
  faqs:
    - question: What is DeGov.AI?
      answer: https://docs.degov.ai
  apps:
    - name: Token Wrap
      description: Convert back and forth between the native token and the wrapped governance token
      icon: https://pbs.twimg.com/profile_images/1912415584257474560/GznnScP3_400x400.jpg
      link: https://token-wrap.degov.ai?config=https://degov-dev.vercel.app/degov.yml

Why I think this is the right direction:

• dao keeps only DAO identity
• urls keeps first-party DeGov workflow URLs
• branding keeps only visual assets
• services groups external integrations like wallet connect, AI agent, and analytics
• chain stays as the runtime network definition
• governance groups the protocol-critical config (contracts + indexer)
• treasury and ui keep optional product features out of the root

The migration from the current schema would be straightforward:

• name -> dao.name
• code -> dao.code
• description -> dao.description
• siteUrl -> urls.app
• offChainDiscussionUrl -> urls.discussion
• editLink -> urls.editConfig
• logo -> branding.logo.default
• theme.logoLight -> branding.logo.light
• theme.logoDark -> branding.logo.dark
• theme.banner -> branding.banner.desktop
• theme.bannerMobile -> branding.banner.mobile
• theme.faqs -> ui.faqs
• wallet.walletConnectProjectId -> services.walletConnect.projectId
• aiAgent.endpoint -> services.aiAgent.endpoint
• analysis.ga.tag -> services.analytics.ga.tag
• contracts.governor -> governance.contracts.governor.address
• contracts.governorToken -> governance.contracts.governanceToken
• contracts.timeLock -> governance.contracts.timeLock.address
• indexer.* -> governance.indexer.*
• treasuryAssets -> treasury.assets
• safes -> treasury.safes
• apps -> ui.apps

If we move forward with this, I think degov and degov-registry schema changes should be updated together, and it would be safer to keep a compatibility loader for the current flat structure during the migration window.