pimato / dxdao-landing-page Goto Github PK

“Get DXD” currently links to https://dxtrust.eth.link/#/

However, often the best place to get DXD is on exchanges. We should update this somehow so that we don't mislead newcomers. I think @pimato can provide guidance on how this should be done. One idea I have is to also link to DXD trading on Swapr

Since Mix.eth has not entered development yet, I think we should consider removing it from the home page.

In addition we should add Rails.eth

Also add Discord under the Community link in the header.

We have removed it frome the menue, becaus reedit is dormant. on the footer its still there

Swapr Links

• Link to swapr.eth from product panel on homepage
• Add Swapr Dapp link to codebase page

Miscellaneous Links

• "Create a Proposal" should link to Proposals tab on Alchemy instead of DAO homepage
• Update youtube channel link to https://www.youtube.com/c/dxdao
• Update Manifesto ratification link to go to alchemy instead of etherscan
• Update Worker Compensation guidelines ratification links to alchemy instead of etherscan

• The header and footer are used for more than just the landing page, so they should not be in the landing page directory
• Instances of header and footer should not be named LandingPageHeader and LandingPageFooter, e.g. in App.js

Hey everyone,

now that the compensation guidelines are getting ratified by the DXdao, we need to add it to the DXdao.eth landing page:

Figma:
Design Specification

https://dxdao.eth.link/#/worker-compensation

Standard is, but maybe double check with @pulp and doku: 2 weeks trial, at least 40h. Payed 50%. This is not part of the monthly payment. Then the first two months is 80%.

Now it looks like this:

Also change this, DXD is calculated at ATH at coingecko

ping me on the pull request or commit if I should double-check.

On desktop, it looks okay

-instead of having 2 links in Links.js page one for pure .eth and one for eth.link we should have a function that dynamically adds .link to pure ipfs link if user has Metamask

For improved maintainability, we should clean up the directory structure. Here are some notes I have:

• Should be a pages directory
  • Each page should have it's own folder that contains all associated components
• containers directory:
  • Omit NavbarContainer and FooterContainer
    • Unless someone has a good reason to keep them
  • We should do what we've done in LandingPageContainer for the other pages
    • Then we can use the containers directly in the router
• Directory names should be all lowercase
• links.js should be moved to the misc directory

This is all opinionated, and simply rough notes on the topic. Further discussion is very welcome.

Rails should be removed from https://dxdao.eth.link/#/

We will be using just-the-docs Jekyll theme as you can see in this github repo https://github.com/pmarsceill/just-the-docs, it will be forked and converted to our needs. As for now we will focus on Worker Onboarding Dashboard as outlined in this daoTalk post (https://daotalk.org/t/dxdao-onboarding-refresh-update/2418)

• Add categories as outlined in this doc (https://docs.google.com/document/d/14gUD_GY2QkrJ0QKNFXoQd5w9Sjh5DN49yBhzeveYGFU)

• Host it on ipfs without issues (here is the first version which has some things missing https://bafybeidlwtumxjeiperp7uywexafy2rd2perlenzzprpjeelyjvllvsa3y.ipfs.dweb.link/)

• Add all the content (yet to be made)

• Create fork of just-the-docs repo and convert it to our needs

Hey everyone!

Now that the DXdao is getting creating more important content around all things DXdao it is important to think about a way to let newcomers explore those pages. Therefor I am proposing to add on-hover navigation items at the top right corner of the page:

Desktop:

Mobile Idle:

Mobile Collapsed:

Figma - Desktop:
Design Specifications
Playground

** Figma - Mobile:**
Design Specifications
Playground

Maybe something like: "Get DXD tokens:" ?

Hey everyone,

now that the DXdao ratified the first version of the Manifesto we need to add it to the main landing page.

Figma:
Design Specification

Does "DeFi’s Governance Layer" make sense? To me this sounds like something that plugs into other projects or that other projects use to do governance. If anything, might be a good tagline for DAOstack.

Personally I think sticking with "We Decentralize DeFi" makes sense.

-when you click on dxstats button on landingpage nothing happens

"There is no boss." sounds a bit like there is no accountability. Maybe the text under "No Hierarchies" can say Work with a distributed collective that finds consensus through voting.

DXD is the DXdao native ERC20 token, DXD token holders have an economic claim to the DXdao´s revenue and it also grants its owners future access to a suite of services and premium features in decentralised applications, such as gasless transactions, feeless anonymizing of assets, reduced trading fees on DEX protocols and more. I think this should be updated. Probably requires some discussion from multiple members.

As found in S/N 7 of Annex C;

"API endpoint that displays ONLY 'Total Supply' as a numerical value (e.g. http://chainz.cryptoid.info/grs/api.dws?q=totalcoins)
Total Supply = # of coins in existence right now (minus any coins that have been verifiably burned)."

After some discussion with John, it appears they want this externally. We were unsure if this would work since DXdao hosts no servers; regardless I would like to discuss an avenue to satisfy this provided it will not work via IPFS.

• dxswap-core v0.3.1
• dxswap-periphery v0.3.1
• dxswap-dapp v1.0.0 Alpha 1
• mesa-dapp v1.5.2 / ipfs: QmWP3AHj4d9zWfbKxhHgF5tWKTQrgg8WQC24F8ew6cFiHV
• omen-dapp v1.2.0 / ipfs: QmUqN9F8gbmgS933U2ubvrqWGCibNuVdG6FjQny8ywKJVp
• rails v1.1.0 / ipfs: QmSzjFGSGmbm7anc6pJV5kCWESQcCAGBw6byTvcrW8UDdN

Should complete #12 first.

• In App.js we shouldn't have any repeating components. Instead, we can wrap the routes in the reused components.
• Refer to the method used in #12

Please we NEED Dark Mode on https://dxdao.eth.link/#/

When there are elements in the background behind a dropdown menu you have two issues:

• Can see background elements

• Dropdown menu closes once you hover over the part of the dropdown covering the background element

Currently we have added margins to the whole page on full resolution but should only apply those margins if the width is < 1054. Everything above should not have any margin.

In mobile, the content is very much towards the edges and adding padding will be good.

Source:
https://daotalk.org/t/published-dxdao-audits/2505

• Homepage should make it clear that REP has the voting power and DXD has only financial interest
• Could maybe link to some info about Governance 2.0 efforts and how there is a goal to align the two in voting power