You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 9, 2024. It is now read-only.
Goal 1: Console is going to serve as a way to demonstrate deploying workloads for 3 high level user segments:
(RPC/ Validator) Node Deployment.
Web Hosting
AI & ML Model Hosting (inference/ fine-tuning)
We want to make this clear to the users and not mix each of these user segments
Goal 2: We want to make a better landing page for Console than just dropping them into the list of Cosmos chain tiles, like we do today
REQUIREMENTS
Design a new top level page that has two sections:
- The top half should provide clear guidance on the user segments we want to target. Ideally a single call-to-action like "What would you like to do today?" on top and then 3 tiles below it, arranged horizontally next to each other: "Deploy a Blockchain Node"; "Host a Website or BlogSite"; "Deploy an AI/ ML Model". Each should have a logo and a "Choose a Template" action that the user can click. The look-and-feel of these tiles should be same as the look-n-feel of the tiles under /new-deployment today.
- The bottom half of the page should provide a high level overview of the deployment process for anyone not familiar with it.
The above page should be the default route when someone navigates to console.akash.network and must replace the existing /new-deployment default. The endpoint could be /landing. Note that the current /new-deployments page (with all the cosmos chains) would link from the "Deploy a Blockchain Node" tile and the other two tiles will have their own pages, so set those to "Coming Soon" in place of "Choose a Template" in the below image (we will update them when we add the pages for those specific routes)
Update the Console code to add that top level page
- The content of the page should be driven by a metadata file located in https://github.com/akash-network/deploy-templates -- can put it under "landing/metadata.json" (see this issue for context: Bugfixes/add missing redirects console#98). The metadata.json file should have a version and specify the logo file location, the title for each tile, the destination (URL) that it leads to and the max number of tiles to show when the browser window is expanded horizontally. The number of tiles shown should be based on the number of entries in the file, with tiles displayed from left-to-right corresponding to entries in the file from top to bottom and a max of maxHorizontalTiles (specified) in the file per row.
Update the routes in Console so that the individual tiles point to routes that make sense:
Community Bounty: $100 (paid in $AKT)
GOALS
Two goals here:
Goal 1: Console is going to serve as a way to demonstrate deploying workloads for 3 high level user segments:
We want to make this clear to the users and not mix each of these user segments
Goal 2: We want to make a better landing page for Console than just dropping them into the list of Cosmos chain tiles, like we do today
REQUIREMENTS
- The top half should provide clear guidance on the user segments we want to target. Ideally a single call-to-action like "What would you like to do today?" on top and then 3 tiles below it, arranged horizontally next to each other: "Deploy a Blockchain Node"; "Host a Website or BlogSite"; "Deploy an AI/ ML Model". Each should have a logo and a "Choose a Template" action that the user can click. The look-and-feel of these tiles should be same as the look-n-feel of the tiles under /new-deployment today.
- The bottom half of the page should provide a high level overview of the deployment process for anyone not familiar with it.
Below is the design we've come up with. Please email anil [at] akash.network to request access to full figma. The icons and illustrations are uploaded to https://github.com/akash-network/deploy-templates/tree/main/template-icons/nodes/landing
The above page should be the default route when someone navigates to console.akash.network and must replace the existing /new-deployment default. The endpoint could be /landing. Note that the current /new-deployments page (with all the cosmos chains) would link from the "Deploy a Blockchain Node" tile and the other two tiles will have their own pages, so set those to "Coming Soon" in place of "Choose a Template" in the below image (we will update them when we add the pages for those specific routes)
- The content of the page should be driven by a metadata file located in https://github.com/akash-network/deploy-templates -- can put it under "landing/metadata.json" (see this issue for context: Bugfixes/add missing redirects console#98). The metadata.json file should have a version and specify the logo file location, the title for each tile, the destination (URL) that it leads to and the max number of tiles to show when the browser window is expanded horizontally. The number of tiles shown should be based on the number of entries in the file, with tiles displayed from left-to-right corresponding to entries in the file from top to bottom and a max of maxHorizontalTiles (specified) in the file per row.