da0-da0 / docs Goto Github PK

The splash page should feature some DAOs.

It's possible to request 01 amount of token for unstaking when I have 1 token staked

.

When I create a proposal and add a send message with token's amount 0.05 then the proposal is created with an incorrect amount: 50000

.

Names of options and the tooltips that describe them should be the same across the documentation and the UI.

How exactly does quorum work? How exactly does threshold work? How exactly is your voting power on a proposal determined?

a good meta-contribution: improving the process for new contributors to contribute. I think our contributor guidelines could use some sprucing up with more details under each of the categories under 'how to contribute': https://docs.daodao.zone/docs/how-to-contribute. for example, in dao-contracts there are several issues with the good-first-issue tag, we could link to those in the doc: https://github.com/DA0-DA0/dao-contracts/issues?q=is%3Aissue+is%3Aopen+label%3Agood-first-issue. Could also use a description of how to fork the repo and create a PR against it without needing to be added to the github repo. Also, I feel like i've noticed some non-technical folks wanting to contribute but being unsure how to. Maybe we could differentiate between technical / non-technical contributions in the guidelines, and add some more non-technical contribution examples such as user interviews or writing. after our guidelines are better we can pin them in some of the channels. the goal is to make it easier to bring more voices in from the periphery (and with us having a contribution-first culture, the process should be as streamlined as possible)

Support internationalization

Blocked on DAO DAO design: https://github.com/DA0-DA0/design

Ideally this synchronization should be programmatic: pulling from a repo that defines colors, fonts, and so on.

An unsuccessful and successful message appears when rejecting the staking transaction in the wallet

.

Document the options that define a DAO.

Document the types of messages users can send with proposals, and what their parameters are.

When sending a custom message within a DAO, the proposal creator needs to enter a json object every time. This is not easy to do for some people without technical skills and contract knowledge.

With the help of custom component templates for DAOs, people can select from pre-made messages and execute those easily.

Add a box after the "On this page" sidebar that invites users to contribute edits on GitHub.

For design inspiration, see the Cosmos docs.

No action on UI after clicking the button "DELETE DRAFT" on the proposal window.

Not ideal. : )

A linter should check for spelling and style, as well as consistent terminology when possible.

I am building a website working on the Juno chain that connects Keplr wallet.
I have connected the Keplr wallet on the desktop version and want to connect Mobile Keplr Wallet.
I tried it using cosmodal but failed and found that https://daodao.zone/starred works well.
I would be very thankful if you could share the code for connecting Mobile Keplr Wallet.

Include information about how to manage tokenomics, key considerations, etc.

Page shows error message (See screeshot)
Connecting Kelpr wallet doesn't help

Documentation should have screenshots for UI flow.

Ideally, these screenshots would be generated programatically by a build process. This would keep the screenshots up to date even as the UI changes.

In the build process, some code should describe how to achieve the desired application state. Once the state is reached, the screenshot should be generated and added to img/.

Ideally, the actions that describe how to achieve the app state could be parsed to produce dynamic natural-language "steps" for the documentation.