Add gpu utilization guide

[giraffekey]

GPU Utilization Guide

/claim #8
/closes #8

Writer's Checklist

Writing Structure

• Use short sentences and paragraphs, and include bucket brigades.
• Include more than two descriptive H2 headings to organize content.
• Capitalize headings according to the AP Stylebook (use this tool)
• Include an introduction with at least two paragraphs before the first H2 section.
• Use appropriate formatting (bold, italic, underline), notes, quotes, TLDRs, and key points.
• Incorporate code elements and Markdown format where appropriate.
• Ensure at least one visual element per “screen” of the article (screenshots, diagrams, tables, graphs, lists, sidenotes, blockquotes).

Fact-Checking

• Verify all facts and data points included in the article.

Asset Management

• Save images in the /assets folder.
• Follow naming conventions: YYYYMMDD_title_of_the_article_IMG_NAME_NO.png.
• (Optional) Create a GitHub repo for the code referenced in the article and share it.
• (Optional) Include a link to this Loom video in the PR comments.

Interlinking

• Use CTRL+F to search for relevant keywords in:
  • Daytona Dotfiles Sitemap
  • Daytona Definitions Sitemap
• Interlink keywords using the appropriate URLs.

Glossary/Definitions

• Create new definition in /defitnitions folder.

Review and Edit

• Ensure articles address the needs of the target audience and their search intent.
• Read the article out loud to catch any awkward phrasing.
• Run the draft through Grammarly or a similar grammar tool.
• Double-check adherence to the style guide and repository guidelines.
• Use the name of the article for the title of the PR.

[mojafa]

@giraffekey
Could you please screenshots of the mentioned commands and code runs?

equally do you have a repo where you have this code? I'm trying to replicate evry step.

also this is meant to be an article...see here: #8

[mojafa]

Also no mention of Daytona or how to setup using Daytona...

[giraffekey]

Repo:
https://github.com/giraffekey/gpu-container-example

Video:

demo.mp4

[mojafa]

I think you forgiot to add the images.

[mojafa]

@giraffekey I'd really appreciate it if you could draw an architecture for how your project works. To be honest, it's just codes and commands at the moment. Also, I see you added the bit for your repo and used daytona create for that. But im wonderingwher eit comes in. This article should cover enough for new bies to know how they're all tied together

[mojafa]

@giraffekey I'd really appreciate it if you could draw an architecture for how your project works. To be honest, it's just codes and commands at the moment. Also, I see you added the bit for your repo and used daytona create for that. But im wonderingwher eit comes in. This article should cover enough for new bies to know how they're all tied together

[mojafa]

We're almost there.

I'd suggest get rid of the docker image asset and actually share an architecture diagram of how your project connects, then add some screenshots of your code runs and terminal results.

[mojafa]

check my comments, you're almost there to be honest

[mojafa]

@giraffekey or tell users to create a new workspace form your repo_url, then guide them through the steps...