diff --git a/wg-akash-website/meetings/2026-07-16.md b/wg-akash-website/meetings/2026-07-16.md
new file mode 100644
index 00000000..22850f6e
--- /dev/null
+++ b/wg-akash-website/meetings/2026-07-16.md
@@ -0,0 +1,295 @@
+# Akash Network - Website Working Group (WG-Website) - July 16th, 2026
+
+## Agenda
+
+* Website and documentation updates
+* Console onboarding improvements
+* New website content
+* AI-friendly documentation
+* Open action items
+
+## Meeting Details
+
+* Date: July 16, 2026
+* Time: 6:30 AM PST
+* Recording: coming Soon
+* [Transcript](#Transcript)
+
+## Participants
+
+* Piyush
+* Joe Deng
+* Tyler Wright
+
+## Meeting Notes
+
+### Website Updates
+
+* Regular website and documentation updates continued across the Akash homepage, ecosystem pages, and roadmap.
+* The $100 GPU credit promotion for new Console users ended due to high demand.
+* The homepage was simplified to communicate Akash’s GPU value proposition more clearly.
+* Ecosystem links were updated, while roadmap changes continued to publish automatically through GitHub Actions.
+* Three documentation-related pull requests remained under review.
+
+### Console Documentation
+
+* Tyler highlighted that documentation must reflect the separation between Akash Console and Console Air.
+* Existing onboarding guides contain outdated copy and screenshots and do not clearly explain which product users should choose.
+* Rodri prepared a screenshot-based onboarding guide, while Max was also updating the Console onboarding flow.
+* The team aimed to publish improved documentation before the Akash-sponsored hackathon.
+* Piyush agreed to review the structure, screenshots, and relevant pull requests.
+* Joe agreed to follow up with Rodri and prepare an additional guide for the main Console experience.
+
+### New Website Pages
+
+* Joe proposed a dedicated GPU page showing the different GPU models available on Akash.
+* He also proposed an enterprise page covering managed services, SLAs, implementation support, and case studies.
+* Denis will support the visual design, while Piyush will provide technical and website implementation guidance.
+* Community contributors are expected to prepare the initial content.
+
+### Blog and AI Improvements
+
+* Joe proposed updating older blog posts with FAQs, summaries, keywords, and clearer structure.
+* The goal is to improve visibility across search engines and AI tools while preserving relevant existing content.
+* Piyush confirmed that blog tags already exist but agreed that FAQs and short summaries could be added.
+* Joe also requested Markdown export and options for using documentation in tools such as ChatGPT, Claude, and Perplexity.
+* Piyush confirmed that this is technically possible and recommended creating GitHub issues to track the work.
+
+### Closing Remarks
+
+* The immediate priority is publishing accurate Console and Console Air onboarding documentation.
+* Longer-term priorities include the GPU page, enterprise page, blog modernization, and AI-friendly documentation tools.
+* Contributors were encouraged to submit website issues and feature requests through GitHub.
+
+## Action Items
+
+### Piyush
+
+* Review the Console documentation pull requests.
+* Check the structure and screenshots before publication.
+* Support planning for the GPU, enterprise, and AI documentation features.
+
+### Joe Deng
+
+* Follow up with Rodri and Max on the onboarding guides.
+* Create issues for blog modernization and AI-friendly documentation.
+* Coordinate content for the GPU and enterprise pages.
+
+### Tyler Wright
+
+* Ensure the onboarding documentation is reviewed and published.
+* Support documentation readiness for the hackathon.
+
+### Rodri R and Max
+
+* Complete the Console onboarding guide.
+* Add updated screenshots and submit the final pull request.
+
+### Denis Lelic
+
+* Support the design of the GPU and enterprise pages.
+
+## Transcript
+
+### **00:00:00**
+
+**Joe Deng: **so I'll ask you later.
+
+**Piyush: **Yeah. So, uh let me just share the screen first. Um okay everyone, welcome to the work group uh Kash website meeting. We host this meeting bi-weekly. Uh I was absent in the last meeting uh due to some u non availability uh for some reasons. I think uh Dennis handled the last meet last meet as far as I remember. So today we'll be covering uh some quick updates on what happened on the card website for the past two to four weeks. So as usual I'll go through it and then we can discuss and take some questions from the community members and also Joe. So first of all like we have some regular updates on the documentations been done by Zeke and other core team members. We have one major change that happened uh in the last two weeks is uh the we had a bonus or you can say a kind of a offer where whoever was signing up getting this 100 USD GPU credits on the Akkash console that is now gone due to the high demand and uh uh few other changes like minor changes on the Kosh network uh homepage.
+
+
+### **00:01:24**
+
+**Piyush: **So if you are following Akash website you may have seen there are frequent updates going on across multiple pages. So right now if you see the state of the homepage it's very uh to the point we don't have any components which are uh overexagating overexaggerating the things. So we have to the point uh uh you can say presentations of what a cash network is and how it benefits the uh AI industry by providing amazing amazing uh GPUs uh at a cheaper cost and also like instant while other competitor takes uh approval and then you get the GPUs and stuff like that. So we have some updates and then we have I noticed that there are few PRs being merged by ZK which uh edited the URLs on the ecosystem aash ecosystem page uh in case they were changed by the project. So we have uh those updates. So these are the overall updates that we had and then we have the automated a updates which keeps on happening over time. So whatever that's updated on the road map repo gets pushed to the website automatically via the GitHub actions which we set up a while ago.
+
+
+### **00:02:48**
+
+**Piyush: **So these are some of the updates. Now we have three open PRs. I think work on these PRs are still going on. B they are also kind of related. related to the documentations. None of the PR is approved by ZK but after the approval there are more updates been done on the same PR. So I had followed up with ZK uh to see if this PR is good to merge. If it is worth to merge then we'll merge it very soon. So these are the overall updates on the website and if you're interested to explore the full code base of Aash website, you can always go to pub.com/ashnetwork/webite. Thank you. Okay. Uh now uh I think we can take some questions from Tyler and Joe and if they would like to share anything so feel free to uh uh pick the mic.
+
+**Tyler Wright: **Perfect. Um, the only thing that I wanted to bring up,
+
+**Piyush: **Okay.
+
+**Tyler Wright: **um, we talked about this at a a previous meeting, uh, but there's been a lot of work that's been happening around console and console air.
+
+
+### **00:04:02**
+
+**Tyler Wright: **Obviously, in the last month or two, those those um, two items have been split. There used to be one console where people can use a crypto wallet and use a manage wallet. Um, now there's two different tools. So again, if anybody wants to self custody and use, you know, crypto wallet, um they can use console air, they can self-host it. There's an air uh network where again there's a hosted version um as well as console. There's been a lot of onboarding flow changes and as a result the documentation needs to be updated. So I know there's some up updation updates that documentation that P is displaying on the screen but I think just like how to go through the onboarding experience um how to leverage these tools I think uh choosing your console getting getting started could be a little bit uh improved upon. I know there's some outdated information we wanted to showcase some of the new images from the new
+
+**Piyush: **Thank
+
+**Tyler Wright: **experience.
+
+**Piyush: **you.
+
+**Tyler Wright: **So I know that Joe has been working with a community member on this.
+
+
+### **00:05:06**
+
+**Tyler Wright: **I just wanted to see where this was um because there's a hackathon tomorrow. It's a that Akash is sponsoring. There's an opportunity to um showcase this docu excuse me showcase this onboarding flow which is going to be happening. I was trying to see if we can update the documentation ahead of that hackathon. Um if not then again people can just go through the flow um and we'll have a couple of folks from the core team there in person to support but um yeah just wanted to make just want to bring this to light um I can probably make an issue for it but again we just want to make sure that the onboarding experience for folks that maybe don't know Akash as well is as seamless as possible through the documentation especially with a lot of changes happening to uh products.
+
+**Joe Deng: **Uh so I want to provide a quick update on that. There are two things that happened uh yesterday that I wanted to show. The first is going to be the work from uh our community member Rajri who has uh produced this onboarding documentation with um screenshots and things like that to make it easier.
+
+
+### **00:06:18**
+
+**Joe Deng: **So he has told me that this has already been uh there's a p a pull
+
+**Piyush: **Following
+
+**Joe Deng: **request to basically have this added in the documentation. So this has already been completed but if anything else for the hackathon we can always send people the actual guide because obviously that's a lot faster to just share this. Uh but that's something that's here. Another thing that I want to share is as I was uh uh you know syncing up with uh with Max he uh was showing me that there's this uh onboarding flow that you know he was updating as well and so I have asked Rodri to assist with the screenshots so that he can add them to his uh to to this guide. I don't know if this is what is uh P is showing right now as the as the official
+
+**Piyush: **Okay.
+
+**Joe Deng: **uh documentation. I don't know if this is approved yet, but I'm just saying that this exists and we are working on uh making this the the best that it can be. So, that's the update from this uh console side.
+
+
+### **00:07:18**
+
+**Joe Deng: **And then I believe that I will be also making a guide uh coming up soon for the main account as well.
+
+**Piyush: **Oops.
+
+**Joe Deng: **So, there will be plenty of coverage on this issue or on this up upgrade actually. So, uh looking forward to that.
+
+**Tyler Wright: **Perfect. That sounds amazing. I I'll have make sure that Max reviews both of those PRs um and we have a plan to get those live.
+
+**Piyush: **that
+
+**Tyler Wright: **Um so yeah, I'll follow up with either you push or I know that Zeke can also uh look at things as well. So maybe P if you have some time today, you can take a first pass and see if there's anything from a structural standpoint that needs to be updated knowing
+
+**Piyush: **first
+
+**Tyler Wright: **that some of the copy might change. Um, and then we'll just wait for Max to have a final version,
+
+**Piyush: **Mhm.
+
+**Tyler Wright: **then we can uh get it
+
+**Piyush: **Yeah. Yeah. For sure. So, uh I think like uh Max is probably working on one of the issue that you're mentioning.
+
+
+### **00:08:06**
+
+**Tyler Wright: **merged.
+
+**Piyush: **The only thing that Joe mentioned is uh it still has uh little probably like very less uh visual uh elements like the screenshots and stuff like that. So either what we can do is like we can create a PR with uh the visual docs u and the images and the screenshots or else uh we can wait for the max uh to uh do the uh I think we can work on the same PR that the max is working on. Uh and once this is approved we can just merge it to the website.
+
+**Joe Deng: **Yeah. So from uh Rodri's up latest update. He said I don't I don't actually know what this means, so I apologize for that, but he says just waiting on approval to add to the docs. So, I think he would have submitted a PR somewhere. So, uh that should be available. If you don't see it, I'll follow up with him. And uh absolutely. I think Max invited Rodri to help with his uh issue. So if uh if you are good to assist as well, I think that that would be the the way to
+
+
+### **00:09:25**
+
+**Piyush: **Yeah, sure. Uh I don't see any PRs along the road as you can see. So we have the PR from Max uh ZK u even in the merged PR also probably I think this No is not the one we can follow up with Rodri I think he may have worked up to create the PR to the main website or something. So if he has already decreed something um do I would love to see the PR and see like uh if it's a good job or something.
+
+**Joe Deng: **Okay, sounds good. Um, I guess I can ask you this here. So, I am uh the community is working up a couple of new things that I wanted to know how we should integrate with you so that we can add it to the main website. So I will be talking with Dennis as well in order to uh work on the looks
+
+**Piyush: **in order
+
+**Joe Deng: **and feel of it because obviously we want these new pages to be uh coherent with the rest of the website.
+
+**Piyush: **to
+
+**Joe Deng: **Um but I also wanted to invite you P to be a part of the discussions and and and you know ask you for guidance as the community works through uh what what we want to put up.
+
+
+### **00:10:43**
+
+**Joe Deng: **And so what we want to put up is uh two two sets of pages as well as a new blog. So the the two sets of pages is going to be a GPUs page so that we can showcase the
+
+**Piyush: **I
+
+**Joe Deng: **different models of GPUs that we have on the network and then I want to create a
+
+**Piyush: **think
+
+**Joe Deng: **enterprise page which is going to host uh maybe doubly host some case study examples and you know the the services that we provide for enterprises right uh because it's not so obvious that we can do SLAs's that we can do all these behindthe-scenes services the managed services that the overclock team does for uh you know enterprises that need that extra handholding. And so obviously Aos network itself doesn't really do handholding for the most part. So this type of service is something that's not currently represented on the website. And so that's something that I'm going to be working with Dennis to add. And so I wanted to give you a heads up on that. And uh again invite you to be a part of the planning stages.
+
+
+### **00:11:42**
+
+**Joe Deng: **uh I expect that the community will be producing these pages and ultimately give them to you to uh format and edit. And then another thing that I am looking forward to is going to be a re uh retrofit of previous blogs and previous content because we want to make it more mo we want to modernize it for the post LLM world. And so I want to add things like FAQs, tags, keywords, things like that into previous posts. And so I plan on trying to sync up with you to see how we can do that in a way that you know makes sense to you, right? Because ultimately we are uh outsiders in in in the in the web website portion and so we want you to be a part of that uh and assist the community so that we can produce the work that is easier for you to understand and uh quicker for you to implement.
+
+**Piyush: **f***. uh we do we do have the tags uh in the blog the one thing that we can probably add is the FAQs that you're mentioning at the end of the blog.
+
+
+### **00:12:51**
+
+**Piyush: **So uh if you see we have the topics uh rest we can figure out as we plan and what is your thought process and if it aligns with the website we can uh go ahead with the implementation.
+
+**Joe Deng: **Yeah. So, I think it's going to be just like a mass upgrade. So, well, FAQs on every p on every one of these posts and maybe like a TLDDR at the front of it as well. Uh, so those are just some of the the changes. I think that, you know,
+
+**Piyush: **Mhm.
+
+**Joe Deng: **a lot of the work is is going to be just those two sections because uh we will just do a better a different job. I wouldn't say a better job, a different job uh a different format going forward with the future blog posts.
+
+**Piyush: **Sure,
+
+**Joe Deng: **But I just wanted to retrofit some of the older ones so that we can uh take advantage of the new way of search and have people find our previously made content which is still very relevant.
+
+**Piyush: **sounds good. Right. Um I think uh the most instant item is to uh look after this P console and by P console here uh documentations so that we can have something really good for tomorrow's hackathon.
+
+
+### **00:14:05**
+
+**Piyush: **I will also be taking a look at it. Plus uh Zo if you can follow up with Max. I'll also follow up with blacks to see if this PR is good to merge uh or like if it needs uh some images. Uh if it does need some images, I can help with it. So I'll I'll follow up with Max as well. You can also follow up with him to see where this stands right now.
+
+**Joe Deng: **Perfect. Uh I actually have one more question for you P and that is uh for the documentation we I really ideally want to add a uh easy way to export as markdown
+
+**Piyush: **Lord
+
+**Joe Deng: **files and as well as uh be able to open the documentation within claude chatgbt perplexity things like that how difficult is that
+
+**Piyush: **and
+
+**Joe Deng: **technically because I I just I don't have an idea idea. So, it's something that I would like to be implemented. Is that something I can ask you to look into or is that something that I need to task a community member to find
+
+
+### **00:15:08**
+
+**Piyush: **It it it does need some technical work on the technical front. So we have to add this feature where it becomes easier for the claude code to read the documentations or any other AI agents. So if you have seen mainti so mainti is a documentation site. So which provides right now if you go to the documentation we have all this written in the markdown which we just have to add some feature here with a drop-down where we can have some copy buttons for LLMs or something like that similar to Minkly. So it does require let's say uh 3 to 4 days of work and then the approval and then the merging uh and it should be live on the documentation. But I do like your suggestion. It also uh works well. I I'll show you how it
+
+**Joe Deng: **Yeah,
+
+**Piyush: **works.
+
+**Joe Deng: **I just wanted to know how how do I uh coordinate with you to get this done? Um, and that's really the the big
+
+**Piyush: **I think we can just create a issue here uh so that it
+
+**Joe Deng: **question.
+
+
+### **00:16:15**
+
+**Piyush: **remains on our agenda.
+
+**Tyler Wright: **Yeah,
+
+**Piyush: **So
+
+**Joe Deng: **It sounds like you know exactly what I'm asking for.
+
+**Tyler Wright: **that would be perfect.
+
+**Joe Deng: **So that's
+
+**Tyler Wright: **Yeah, I think we have a small version of this, but Joe, if you could make an issue for this so we can track this. I know Piyush  will get knocked out. And same for the AEO stuff that you're talking about. We can make an issue and then try try to like put all the checklist of all things we kind of want to do. I'm sure we get up to get those things executed.
+
+**Piyush: **So like whatever is I think it will be better. So whatever the idea that we are going through including this LM context saying so we can create a issue. Uh so this is one of the missing feature that the Joe pointed out and it is there in the mintly fi infrastructure and others. So uh it remains on track and we can keep on implementing with a schedule. So I and Dennis can remain on sync.
+
+
+### **00:17:12**
+
+**Joe Deng: **Thank you. That's everything I have.
+
+**Piyush: **Hi fine. Uh I think uh okay I think my screen stopped. Uh I hope it is visible. Okay I think that's pretty much uh today we covered few important stuff like what were the dates that's been done on the Akash website and also some of the opponent changes. So Tyler also pointed out that we have one of the K sponsor hackathon happening tomorrow. So we'll look after uh uh this console and the akash console layer documentations to be pushed out as soon as possible. Some of the issues that are raised by Joe are like making it easier for the elements to read documentations and some additional features. So we'll sync with Joe and others to see how we can implement and how fast we can implement those features into the website. So these are all the major things that we covered today and if you still have any questions or issues or feature requests feel free to go to the network website and create an issue we'll look into it and if it's on good we'll implement. So for now I think that's very much and uh we can conclude the meeting for today. Thank you. Have a good day. Goodbye. Take care.
+
+**Joe Deng: **Thank you, Piyush.
+
+
+### **Transcription ended after 00:18:37**
+