Coder Social home page Coder Social logo

website-revamp's Introduction

Akash Network Website Guide

Akash Network Website

Explore the repository for the Akash Network website, skillfully developed by Hooman Digital. The website serves as a dynamic showcase, illustrating the prowess and capabilities of Akash Network—a decentralized cloud computing marketplace revolutionizing the digital landscape.

Getting Started Locally

To run the repository locally and explore the website on your machine, follow these simple steps:

  1. Clone the Repository:

    git clone https://github.com/akash-network/website-revamp
  2. Navigate to the Project Directory:

    cd website-revamp
  3. Install Dependencies:

    npm install
  4. Run the Development Server:

    npm run dev
  5. Open Your Browser: Visit http://localhost:4321 to view the Akash Network website locally.

Contribution Guidelines

Before contributing to the project, please adhere to the following guidelines to ensure the project's integrity and maintainability.

File Naming Convention

When creating files for components, pages, etc., follow this straightforward file naming convention:

  • Component Name: Utilize kebab-case, featuring lowercase words separated by hyphens.

    Example: my-component-name.js

Commit Message Structure

Each commit message should carry a meaningful structure, commencing with a type and followed by a concise description. Utilize the following types for commit messages:

  • feat: Introduce a new feature or functionality to the codebase.

    Example: feat: implement user authentication

  • fix: Rectify a bug or address an issue within the code.

    Example: fix: resolve issue with login page

  • docs: Focus on documentation-related changes, such as updating comments, README files, or documentation pages.

    Example: docs: enhance installation instructions

  • style: Implement code style changes, such as formatting, indentation, or variable renaming.

    Example: style: refactor CSS styles

  • chore: Undertake routine tasks, maintenance, or housekeeping activities, often not directly related to code changes.

    Example: chore: update dependencies

  • test: Contribute to or modify tests, including unit tests, integration tests, or end-to-end tests.

    Example: test: add test cases for login feature

  • perf: Optimize the code for better performance.

    Example: perf: enhance database query efficiency

  • ci: Implement changes to the continuous integration (CI) pipeline.

  • refactor: Enhance code structure without introducing new features or fixing bugs.

    Example: refactor: extract reusable function

  • build: Make changes related to the build process, such as build scripts or tools.

    Example: build: update webpack configuration

  • revert: Revert a previous commit.

    Example: revert: undo changes from commit abc123

  • deps: Update or modify project dependencies, such as npm packages or libraries.

    Example: deps: upgrade lodash to version 4.0.0

Commit Message Best Practices

  • Keep commit messages concise and to the point.
  • Utilize the imperative mood (e.g., "add," "fix," "update") in the description.
  • Provide context in the description when necessary..

How to Contribute to the Akash Website

How to write a blog

  1. Create a new folder under src/content/Blog/ with the name of the blog. For example, src/content/Blog/how-to-use-akash-web/
  2. Create a new file called index.md under the new folder. For example, src/content/Blog/how-to-use-akash-web/index.md
  3. Copy the following template into the new file and fill in the details.
---
title: "Example Blog Title" # <--- This is the title of the blog
description: "Example Blog Description" # <--- This is the description of the blog
pubDate: "2019-11-25" # <--- This is the date of the blog in the format of "YYYY-MM-DD"
draft: false # <--- If the blog is not ready to publish, set it to true
archive: true # <--- If the blog is not ready to publish, set it to true it will not show in the archive page but will show in the blog page
categories: # <--- This is the category of the blog
  - Category1
  - Category2
tags: # <--- This is the tags of the blog
  - Tag1
  - Tag2
contributors: # <--- This is the contributors of the blog
  - Greg Osuri
bannerImage: ./banner-image.jpg # <--- This is the banner image of the blog or the featured image of the blog
---
  1. Add the banner image to the same folder as the markdown file. For example, src/content/Blog/how-to-use-akash-web/banner-image.jpg
  2. Write the blog content in markdown format in the same file. For example, src/content/Blog/how-to-use-akash-web/index.md
  3. Commit and push the changes to the repository. The blog will be published automatically.

Community

How to add to the Events

  1. Create a new folder under src/content/Community_Akash_Events_Page/ with the name of the event. For example, src/content/Community_Akash_Events_Page/ai-world-congress/
  2. Create a new file called index.md under the new folder. For example, src/content/Community_Akash_Events_Page/ai-world-congress/index.md
  3. Copy the following template into the new file and fill in the details.
---
title: AI World Congress # <--- This is the title of the event
image: "./project-banner.png" # <--- This is the banner image of the event
eventDate: "2024" # <--- This is the date of the event in the format of "YYYY"
tbd: true # <--- If the date is not confirmed yet, set it to true
location: Singapore # <--- This is the location of the event
link: "https://www.asia.token2049.com/" # <--- This is the link of the event
description: ​TOKEN2049 brings together the global Web3 industry, uniting entrepreneurs, investors, developers, industry insiders and global media - and creates unparalleled networking opportunities.
---
  1. TBD means the date is not confirmed yet. If the date is confirmed, remove the tbd: true line.

  2. Add the banner image to the same folder as the markdown file. For example, src/content/Community_Akash_Events_Page/ai-world-congress/project-banner.png

  3. Commit and push the changes to the repository. The event will be published automatically.

How to contribute to the Akash Edu

  1. Create a new folder under src/content/Community_Akash_Edu_Page/ with the name of the contribution. . For example, src/content/Community_Akash_Edu_Page/console-101/

  2. Create a new file called index.md under the new folder. For example, src/content/Community_Akash_Edu_Page/console-101/index.md

  3. Copy the following template into the new file and fill in the details.

---
title: Akash EDU - Console 101 # <--- This is the title of the contribution
image: "./project-banner.png" # <--- This is the banner image of the contribution
pubDate: "2020-01-19" # <--- This is the date of the contribution in the format of "YYYY-MM-DD"
tags: # <--- This is the tags of the contribution
  - Upcoming
description: In this course, you will learn how to deploy your project onto the Akash Network using Console — a simple, point and click deployment tool.
link: "https://akash-edu.ctlabs.in/" # <--- This is the link of the contribution
---
  1. Add the banner image to the same folder as the markdown file. For example, src/content/Community_Akash_Edu_Page/console-101/project-banner.png

  2. Commit and push the changes to the repository. The event will be published automatically.

How to contribute to the Community Contributions

  1. Create a new folder under src/content/Community_Contributions_Page/ with name of the contribution . For example, src/content/Community_Contributions_Page/akash-101/

  2. Create a new file called index.md under the new folder. For example, src/content/Community_Contributions_Page/akash-101/index.md

  3. Copy the following template into the new file and fill in the details.

---
title: "Akash Network Live with Greg Osuri: Akash’s progress in 2023, open community development, and more" # <--- This is the title of the contribution
image: "./project-banner.png" # <--- This is the banner image of the contribution
pubDate: "2023-02-24" # <--- This is the date of the contribution in the format of "YYYY-MM-DD"
readTime: "5 min" # <--- This is the read time of the contribution
author: "Robert Del Rey" # <--- This is the author of the contribution
link: https://www.youtube.com/watch?v=aVRqwXOxoe8 # <--- This is the link of the contribution
tags: # <--- This is the tags of the contribution
  - Video
description: Greg Osuri, CEO of Overclock Labs and Founder of Akash Network, will cover the progress Akash has already made in 2023, our new open community group structure, and what to look out for in the coming months.
---
  1. Add the banner image to the same folder as the markdown file. For example, src/content/Community_Contributions_Page/akash-101/project-banner.png

  2. Commit and push the changes to the repository. The event will be published automatically.

Ecosystem

How to contribute a project to the Ecosystem

  1. Create a new folder under src/content/Ecosystem_Page/ with the name of the project. For example, src/content/Ecosystem_Page/akash-chat/

  2. Create a new file called index.md under the new folder. For example, src/content/Ecosystem_Page/akash-chat/index.md

  3. Copy the following template into the new file and fill in the details.

  4. There are four categories deployed_on_akash, akash-tools

---
projectTitle: Akash Chat # <--- This is the title of the project
projectImage: "./project-banner.png" # <--- This is the banner image of the project
pubDate: "2021-01-19" # <--- This is the date of the project in the format of "YYYY-MM-DD"

tags: # <--- This is the tags of the project
  - AI & ML

category: deployed_on_akash # <--- This is the category of the project which can be "deployed_on_akash", "tools"

description: Mistral-7B-v0.2 Large Language Model (LLM) is a pretrained generative text model with 7 billion parameters by Mistral AI. This application is running on NVIDIA GPUs leased from the Akash Supercloud.

showcase: true # <--- This is the showcase of the project in the ecosystem page/showcase

websiteLink: "https://chat.akash.network/" # <--- This is the website link of the project
githubLink: "https://chat.akash.network/" # <--- This is the github link of the project
twitterLink: "https://chat.akash.network" # <--- This is the twitter link of the project

featured: true # <--- This is the featured of the project in the ecosystem page/showcase
---
  1. Showcase is used to show the card in showcase in ecosystem tag

  2. Featured is used to show the card on the top of the page

  3. Add the banner image to the same folder as the markdown file. For example, src/content/Ecosystem_Page/akash-chat/project-banner.png

  4. Commit and push the changes to the repository. The event will be published automatically.

Docs

How to change sequence of docs

  1. Go to the src/content/Docs/sequence.ts
  2. Change the sequence of the docs
export const docsSequence = [
  {
    label: "Docs",
    subItems: [
      {
        label: "Getting Started", // <--- Change the sequence here
        subItems: [ // <--- Change the sequence here
          { label: "Intro To Akash" }, // <--- Change the sequence here
          { label: "Akash Overview" }
          { label: "Stack Definition Language (SDL)" },
          { label: "Tokens and Wallets" },
        ],
      },
  }
]
  1. Name of the label should same as rendered name of the doc in the website

  2. Commit and push the changes to the repository. The event will be published automatically.

How to add new file in docs

  1. Create a new folder under src/content/docs with the name of the file. For example, src/content/docs/akash-101/

  2. Create a new file called index.md under the new folder. For example, src/content/docs/akash-101/index.md

  3. Copy the following template into the new file and fill in the details.

---
categories: ["Akash Nodes"] # <--- Change the category here
tags: ["Blockchain"] # <--- Change the tag here
weight: 1 # <--- Change the weight here
title: "Akash Node CLI Build" # <--- Change the title here
linkTitle: "Akash Node CLI Build" # <--- Change the link title here
---
  1. If you want to add sub items, add the folder under the folder of the doc. For example, src/content/docs/akash-101/akash-node-cli-build/

  2. Create a new file called index.md under the new folder. For example, src/content/docs/akash-101/akash-node-cli-build/index.md

Contact

Discord - Akash Network

Twitter: Akash Network

Website: Akash Network

website-revamp's People

Contributors

dharamveergit avatar hiroyukikumazawa avatar oiclid avatar hoomandgtl avatar zachhorn avatar chainzero avatar andy108369 avatar rakataprime avatar shinysyntax avatar brewsterdrinkwater avatar tgrecojs avatar piber-dev avatar captainsplince avatar gosuri avatar nick134-bit avatar anilmurty avatar cloud-j-luna avatar baktun14 avatar dk3775 avatar okhaimie-dev avatar zblocker64 avatar rangojo avatar vatsal2809 avatar

Stargazers

 avatar Chaitanya Rai avatar Victor avatar  avatar Amit Palomo avatar Domi avatar AnnMargaret Tutu avatar Nathan Lloyd Ward avatar  avatar  avatar Arthur Emmanuel avatar

Watchers

 avatar Artur Troian avatar  avatar Forbes avatar

website-revamp's Issues

add clarity on how on the GPU model format for `price_target_gpu_mappings` config

I've noticed one provider did set 4090 instead of rtx4090 in his price_target_gpu_mappings (in provider.yaml)

Need to bring clarity to the doc on that, that it should match the name set by the operator-inventory based on the gpus.json file, and can as well be viewed by running the following commands:

kubectl get nodes --show-labels

Example

$ kubectl get nodes --show-labels
NAME    STATUS   ROLES           AGE   VERSION   LABELS
node1   Ready    control-plane   29h   v1.28.6   akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090.interface.pcie=8,akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090.ram.24Gi=8,akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090=8,akash.network/capabilities.storage.class.beta3=1,akash.network=true,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=node1,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=,node.kubernetes.io/exclude-from-external-load-balancers=,nvidia.com/gpu.present=true
node2   Ready    control-plane   29h   v1.28.6   akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090.interface.pcie=8,akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090.ram.24Gi=8,akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090=8,akash.network/capabilities.storage.class.beta3=1,akash.network=true,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=node2,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=,node.kubernetes.io/exclude-from-external-load-balancers=,nvidia.com/gpu.present=true
node3   Ready    <none>          29h   v1.28.6   akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090.interface.pcie=8,akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090.ram.24Gi=8,akash.network/capabilities.gpu.vendor.nvidia.model.rtx4090=8,akash.network/capabilities.storage.class.beta3=1,akash.network=true,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=node3,kubernetes.io/os=linux,nvidia.com/gpu.present=true
$ kubectl -n akash-services get pod akash-provider-0 -o yaml |grep -A1 AKASH_FROM
    - name: AKASH_FROM
      value: akash1cnzkdynwd4u6j7s8z5j0fg76h3g6yhsggmuqta
...

$ provider-services query provider get akash1cnzkdynwd4u6j7s8z5j0fg76h3g6yhsggmuqta -o text
attributes:
...
...
- key: capabilities/gpu/vendor/nvidia/model/rtx4090
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx4090/ram/24Gi
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx4090/ram/24Gi/interface/pcie
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx4090/interface/pcie
  value: "true"
...

as you can see it is rtx4090, not the 4090.

Website not using https

When visiting the website from either mobile safari or mobile chrome a triangle with a ! Symbol pops up indicating https is not being used and the website is not fully secure. Here's screenshots of this problem from safari and chrome image

image

Creating meaningful seperation / integration of users docs X engineering docs

Overview

Currently, the documentation is laid out in such a way that there are 2 distinct sections: "engineering docs" and "user docs" the engineering docs.

Engineering docs holds documentation for people who are working closer to the internals of the system should refer to. Inside users docs you'll find a information that caters to a wide audience ranging from individuals who are non-technical, to individuals who are technical to the point that they also frequent the "engineering docs" sections.

Below as a screenshot of showing how these sections are separated.

ss_04232024_000310

You can view this for yourself by visiting akash.network/docs.

Goal

This issue is intended to be an area for discussing and ultimately coming to an agreed upon layout for how this should be structured so that non-technical users aren't forced to sift through content that is foreign to them and similiarly, technical users can easily navigate through the sections of the docs without having to navigate past "cloudmos deploy" sections (for example)

docs: fix issue with rendering text inside SDL section

The SDL section of Getting Started is showing no text where it should be showing :latest.

ss_04272024_000315

Below is the line that corresponds to this issue.

if you scroll to the end, you'll see that :latest is present but for some reason it isn't rendering. perhaps because of the use of HTML within the markdown file as the semantics of the code block seem a bit odd.

| `image` | Yes | <p>Docker image of the container<br><br>Best practices:</p><ul><li>avoid using <code>:latest</code> image tags as Akash Providers heavily cache images</li></ul> |

suggestion: instead of using the code blocks we should be able to use backticks as well as the markdown syntax for paragraph text and unordered lists.

cc @HoomanHQ as he may have some input as to why HTML is being used here, and why this text isn't appearing at all on the page.

Enhance Hero Section on Homepage

Couple of community members have expressed concerns regarding the effectiveness and engagement level of the hero section on the homepage. Feedback suggests that the current hero section may not be sufficiently engaging, fun or representative of Akash Network.

To address this issue we talked about possible solutions during sig-design and wg-akash-website. Below I'm sharing an option that attendees of our meetings liked.

Screenshot 2024-02-21 at 13 43 32

I did some research and found an example in the wild:
Screenshot 2024-02-21 at 13 44 26

link:
https://wellfound.com/

This solution would provide two things;

  • We would add an interactive layer, which would bring dynamic to the section
  • All of the floating buttons are linked to dedicated pages which would enhance engagement

Action item no. 1 would be the copy part. @zachhorn can provide that, when other stakeholders are aligned on the positioning statement.
2. Additional exploration of design possibilites and figuring out what pages are linked to floating buttons
3. Hand-off and implementation

Development page content should be moved to Community

The content in the development section should really be apart of the community section, so new and existing users can learn about sigs, wgs, Akash Insiders and other community based programming.

The Development section should focus on technical contributions including ways for technical users to contribute to areas like:

  • Support repo
  • Awesome Akash
  • technical bounties
  • technical documentation
  • Cloudmos open source tools
  • technical product and engineering roadmap
  • discussions for further technical conversations

extra spacing on each page of the documentation

looking through the docs I found that each page had an unnecessary amount of spacing between the top of the page and the first appearance of any words. I noticed that there is always at least one line of bit of spacing below the metadata atop each page, so I just took a second to do a bulk removal of this space only to learn that this is not a valid fix as the spacing still appeared.

It must be a global setting that needs to be changed in order for this to be fixed. I'm not sure what the setting is though so rather than sink any time into it i'm opening this issue. Additionally, some feedback would be appreciated as I want to ensure i'm not alone in feeling as though this spacing is a bit odd.

Below are screenshots from the new docs.

When there is some heading text to start the page, then it can go unnoticed. I still think that it warrants fixing though.

ss_03042024_000186

Without heading text the extra spacing is very noticeable imo.

ss_03042024_000185

Getting Started section reorg

The Getting Started section is in need of an overhaul and so in this issue I've included screenshot of the getting started section with some proposed changes. I apologize in advance if it looks a bit cluttered! Please read into each section below to get a better understanding of what i'm proposing and also please comment below your thoughts.

ss_04282024_000317

Summary of proposed changes

1. Intro to Akash Section

I think the "Getting Started" does a great job of appealing to a wide audience. Both groups of people, technical and non-technical, can read through it and get the information they need to continue moving forward with making use of the network. That said, it's essentially a FAQ page so if this #76 is still something we're interested in, then I'm curious to here peoples thoughts on transforming this section into the FAQ page.

2. Consolidate Providers, RPC Nodes, and Validators section into one.

These sections are all fairly closely related. Taking this into account, along with the fact that each page contains a fairly small amount of text, I'm proposing that we merge all of these sections into one section, name TBD.

3. Move sections into "deployments category"

I don't think there is much benefit to having these pages baked into the first section of the docs. They actually contain some really useful information, however this information isn't what i would consider to be "entry level", which is why i'm proposing moving the OSEQ, DSEQ, GSEQ and SDL pages are best suited for the "deployments" section.

Also, there is currently a need for the "Akash CLI" section to be re-written, and I think this is an opportunity to supplement the new, useful guides present within that section

Docs: GPU pricing page explainer

add a page that explains the GPU pricing page

non exhaustive list of what it should cover....

  • gives users an entry-level understanding of the chip set, what the cost means, etc.
  • provides any contextual information regarding the components show on gpu pricing page that may be unclear to readers --> points them in the right direction to learn about these areas in greater detail

[docs] Easier UX for a new user to deploy "Hello World" SDL in 5 Minutes or Less

There should be an easy way for users to have step by step guides to deploy hello.world on Akash Network.

The ideal page has a step by step guide using CLI, as well as a step by step guide + video for using Akash Console.

This page should be easily accessible from akash.network/docs so new users can deploy in just a few clicks from the docs.

improve docs search

feedback: docs search seems unusable sometimes.
Searching for keyword maintenance doesn't provide the clear links..

Update "Deployed on Akash" Section on Homepage to include the latest projects

The "Deployed on Akash" section under the "Akash Ecosystem" on the akash.network homepage currently showcases various projects utilizing the Akash Network. To keep this section up to date I suggest we keep updating it with the latest prominent projects.

First update:
Remove the "Osmosis DEX" tile and replace it with "Solve Care".
The tile would link to this blog post: https://akash.network/blog/akash-network-and-solve-care-bring-true-patient-data-ownership-to-the-healthcare-industry/

@zachhorn can you whip a short text for Solve Care? Thank you!

Screenshot 2024-03-01 at 16 48 03

Unsupported file type issue

upon firing up the new website in development mode i found a handful of warnings inside my console informing me of an "Unsupported file type". It seems simple enough to solve but this is my first time interacting with astro so i felt it was best to open this up quickly and hold off on any sort of search efforts for resolving.

I've added a screenshot below:

ss_02232024_000169

Note: I assume devs are aware of this and likely have some input on the topic. Still, i hope calling attn here is useful! And i look forward to learning more about what's going on here 🙂

docs: akash CLI Epic

The documentation for the Akash CLI needs a complete overhaul, and so this issue is intended to be a reference point for all changes made to this section of the docs as well as any discussions related to these changes.

Issue in docs search.

After searching, close and reopen
Remaining the search query, but not effect
So need clear search query when open modal, or filter with previous query.

image
image

docs: improve accessibility of visualizations in engineering docs

While viewing the pages on an ipad i found myself unable to read the text inside the diagram shown within the engineering doc's provider service page.

Click the link above or navigate to: engineering docs > Akash Provider Operators > Provider Service and you'll see the view shown in the image below.

akash-visualization

feedback from others would be great as i'd like to ensure i'm not the only one who finds the text on the image difficult to read. there are tools for doing such analysis but not sure of them off the top of my head and would need to do some research.

i think modifying the images all together would be ideal but i am not sure what the timeline would be for something like that. @HoomanHQ what are your thoughts on implementing a modal, or some feature would would make it easy or users to see a zoomed-in version of the image? if we had that, then we could use it whenever images like the one above appear. Notes: this isn't the only instance where this occurs (look around engineering docs)

Improving Akash Documentation Structure and Naming

During wg-website meetings, we discussed the possibilities of organizing Akash Docs and Engineering Docs.

A simple solution we mentioned during the meeting would be to add labels above each of the category;

Akash Docs

  • menu item
  • menu item
    ...

Engineering Docs

  • menu item
  • menu item
    ...

An easy fix that would visually separate the Docs in half.

But digging deeper I feel some concepts or menu items fit in the same group - but are currently separated or located in a sub-menu section. That's why I'm proposing to reorganize the menu and divide it into groups, with a dedicated label above each group.
I believe this approach would provide clarity and guidance for users.

Structure:
Starting of with

  1. Intro to Akash, where we provide an overview of the Supercloud concept
    items:
  • Intro to Akash
  • Supercloud Architecture
  1. Getting Started
    items:
  • SDL
  • Tokens and Wallets
  • Technical Support
  1. Services
    items:
  • Deployments
  • Providers
  • Guides
    Note: We have to evaluate the relevance of outdated guides (e.g., Chia and Kava) and consider linking external guides created by users. That could live in the "Community contributions" page - but that's another issue.
  1. Network
    items:
  • Akash Nodes
  • Network Features
  • Validators
  • Testnets
  1. Core Documentation
    items:
  • Provider Service & Sub Services

  • Akash Providers Operators

  • Akash Nodes

  • Akash App

  • Development Environment

  • Code Contributors Guidelines

  • End to End Testing Provider

  • Akash API


  1. Other Resources
    items:
    -Experimental

  • Security

  • Containers

  • Marketplace

  • Payments

  • Authentication

  • Akash Mainnet8 Upgrade
    Note: Some of the items from this group could easily be moved to a dedicated group. Like "Marketplace" for example.
  1. Support
    Note: Support is mentioned 2 times in the menu. First in the "getting started" and as the last menu item

Attaching a mockup of the structure above here:
Screenshot 2024-02-29 at 15 08 38

As you see some of the items are renamed. Which opens up another topic. And that is:

Naming:
Next to organizing items, the Akash Docs (items) would benefit from some naming improvements. Stating some of the possible improvements below.

  • at the section "Engineering notes" each item starts with Akash. It seems redundant and repetitive and does not align with the rest of the items in the menu. For example we could shorten "Akash Code Contributors Policies and Standards" to "Code Contributors Guidelines." Same goes for the rest of the items in the "Engineering notes" section.

  • from a first glance we rarely or don't even mention "Supercloud". We could add it to the item "Architecture" so it says "Supercloud Architecture"

  • "Testnet", renaming to "Testnets" (plural form)

  • We have to bring a final decision on how to name the "Engineering Notes/Docs". I tried a couple and ended up liking something with a word "Core" inside. Since I've heard Arthur often talk about core product, platform etc. - so, here is my take: "Core Documentation" or "Core Network Documentation. @zachhorn what are your thoughts?

Improve UX around linking

This issue is for updating the user experience surrounding this issue intends to provide an improved UX regarding navigation of the documentation.

You can get a full understanding of this problem by checking out the video below.

The TLDR: clicking on a section in the sidebar users should automatically bring the user to the first page within that section.

akash.docs.navigation.mp4

Remove the Akash Accelerate Save the Date Button

Akash Accelerate 2024 was a great event, and the call to action brought in over 1400 registered guests.

The event is over now, so the Call to action is not necessary.

If we want, we can change copy and push to the blog.

Contact Page Improvements

Users have mentioned that it is difficult to contact the core team via the Akash.network website.

Was wondering if we can add a simple contact page that sends messages to different departments. This would be a quick thing that can be a page accessible from the footer.

Search feature in the documentation with the hotkey(Ctrl + K)

When using the search feature in the documentation with the hotkey (Ctrl + K), the focus does not work correctly; it requires a double-click every time.
Auto focus is needed.
Additionally, pressing Esc to exit also requires pressing it twice.

docs-search.mp4

Update homepage with the latest relevant testimonials

To showcase the real-world applications of Akash Network, I propose we keep updating the section of "Testimonials" with relevant quotes.

First one would be to include the latest from Solve care;

  1. Care.Wallet is now yours for life.
    @gregosuri and @akashnet_
    decentralized compute network helped achieve our goal to make every Care.Wallet a permanent #Web3 container, that no #AWS admin can shut down.

link to x post: https://twitter.com/Solve_Care/status/1755951636844007848

  1. Solve.Care is migrating Care.Nodes to @akashnet_
    to reduce cost, scale faster, and get rid of #AWS.

link to x post: https://twitter.com/_PradeepGoel/status/1755951930067816607

This issue is intended to remain open to allow community members to contribute additional testimonials they find relevant and impactful. How to contribute? If you come across a testimonial that showcases the effectiveness, efficiency, or innovation of Akash Network, please share it here in the comment section.

Re-organizing the two main network provider pages

Currently, we have two pages on the site that give an overview of Akash's active providers:

I would suggest that we organize these pages into a single Providers page that could live either in the Network dropdown in the main nav, or as a standalone nav item. Both of these pages give prospective (and current) Akash users a sense of the network scale and currently available resources, as well as a detailed look at current providers (including audit status, available resources, and uptime).

Screenshot 2024-02-07 at 3 01 38 PM Screenshot 2024-02-07 at 2 53 03 PM

Repositioning of the "Get Started" section

I suggest moving the "Get Started" section to a prominent position above the fold on the homepage. This change aims to immediately engage visitors, guiding them on the Akash Network journey from the moment they arrive on the site.

This repositioning provides an opportunity to introduce an additional card dedicated to showcasing GPUs on Akash Network. It could highlight the availability of GPUs, potentially driving more users to leverage this feature.

Design Proposal
Screenshot 2024-03-15 at 14 38 46

cc @zachhorn for content

`GPU Resource Enablement` page should contain directions to `Provider Feature Discovery - GPU Configuration Integration Guide` & `Akash Provider Feature Discovery Upgrade/Enablement` pages

Page https://akash.network/docs/providers/build-a-cloud-provider/gpu-resource-enablement/ should contain some link/info about these two pages, critical for enabling GPU support:

As new providers may find their provider does not detect the GPU because it is not in the https://github.com/akash-network/provider-configs/blob/main/devices/pcie/gpus.json file and they have to run the following command in order to update the gpus.json file:

provider-services tools psutil list gpu | jq '.cards[] | .pci | {vendor: .vendor, product: .product}'

Also, this page https://akash.network/docs/providers/akash-provider-feature-discovery-upgrade-enablement/#akash-provider-upgrade does not reflect all the attributes necessary, e.g.:

  - key: capabilities/gpu/vendor/nvidia/model/a100
    value: true
  - key: capabilities/gpu/vendor/nvidia/model/a100/ram/80Gi
    value: true
  - key: capabilities/gpu/vendor/nvidia/model/a100/ram/80Gi/interface/pcie
    value: true
  - key: capabilities/gpu/vendor/nvidia/model/a100/interface/pcie
    value: true

Adding FAQs Page

A suggestion to add FAQs page. It would serve as a resource to address common questions and concerns from users, devs and community members.

Rationale:

  • By consolidating FAQs in one location, users can easily find information without having to search through multiple sources.
  • A FAQs page provides users with quick access to answers for common questions, thereby improving the overall user experience.

Action items:

  • Defining a range of FAQs, including but not limited to: getting started with Akash, deploying apps, becoming a provider, troubleshooting common issues, etc.
  • Providing clear answers, with links to relevant docs or resources for further information.
  • Implementation (adding FAQs to Akash Docs or creating a dedicated page (ex https://cosmos.network/learn/faq/))

Feedback and suggestions from the community are always welcome.

intro to akash dection - bids and leases section

I'm currently working to proof read through the documentation while gearing up to provide video-based walk through of each section. Instances like this, where the material at hand seemingly jumps into a new context, makes this task more difficult.

This section is seemingly geared to users who are non-technical, and I think most would agree that this section of the docs should stray from giving fine-grained details such as the ones it currently contains. I don't think that the solution is total deletion, but instead, reorganization. I believe this may fall within the scope of #16, or at least the motivation behind this is the same.

IOU: A proposed area for where I think this would fit better.

Copy updates to the token page

The header copy section on the Token page has a capitalize class that's transforming the text.

Currently looks like this:
Screenshot 2024-02-13 at 1 06 39 PM

We should remove it so that the text looks like this:
Screenshot 2024-02-13 at 12 52 17 PM

docs audit - RFC on homepage changes

Looking at the docs home page, the essentials section in particular could use some updating. I'm opening up this issue to get feedback on whether or not others think these changes are warranted.

akash-docs-homepage-essentials

So just to provide an example of what an update would look like, here is a new excerpt for the first card, "What is Akash"

Example

What is Akash

The last few years have seen the Akash community succeed in their collective efforts to provide an alternative route for obtaining cloud compute services that are not only more cost-effective but also more resilient. At the heart of this success is the Akash marketplace, which provides a secure, transparent venue for buying and selling compute resources.

make `chrony` a default/standard suggestion in the Akash provider build docs

We should advertise chrony to be a standard in our Akash Docs

it's literally zero-config, just apt -y install chrony and it automatically works out of the box.. (as well as it automatically masks the systemd-timesyncd service after installed [via post scripts]).

Rationale

We found some servers were out of sync, all attempts to fix systemd-timesyncd were not successful.
I also remember from my past job experience that systemd-timesyncd isn't ideal choice.

And we've been using chrony everywhere we could, it makes sure servers are in a perfect time sync.

Replace the "ComfyUI" tile with "Ray cluster on Akash"

On the homepage, we should replace the "ComfyUI" tile with "Ray cluster on Akash"

image

Title: Ray cluster on Akash
subheadline: This post explores the difficulties of parallelizing and scaling AI/ML workloads. We present Ray, a leading open-source framework (used by top ML teams) for large-scale parallel computing and distributed training.

graphic:
raycluster-akash-graphic

link to: https://akash.network/blog/distributed-machine-learning-on-akash-network-with-ray/

cc @anilmurty

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.