Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Getting Started with Llama 3 Blog #23

Open
wants to merge 4 commits into
base: release
Choose a base branch
from

Conversation

garrettbyrd
Copy link

@saadrahim I am not AMD internal so please let me know if I need to @ anyone else to satisfy any of the following. I have a service of work agreement to provide this blog, if you need to be in on an email chain. Relevant, it seems like anton's PR went smoothly without any of this.

Objective: Provide the complementary blog for this ROCm Webinar

Signoff section must be completed prior to publishing.

  • Technical reviewer approves publishing:
  • Editorial team approved publishing:
  • Add a thumbnail image for your blog if one is available
  • Text nugget summarizing your article. 2-3 lines to draw the reader's attention. Possibly the opening paragraph can be used.
  • Blog author team signoffs
    • Legal self review traffic lights completed: (edit and replace with @githubid)
    • Licenses file included for content is correct: (edit and replace with @githubid)
    • Changes from technical review and editorial team are acceptable: (edit and replace with @githubid)

@garrettbyrd garrettbyrd requested review from saadrahim and a team as code owners August 23, 2024 20:24
@garrettbyrd
Copy link
Author

@saadrahim Could I get confirmation that this is under review or being processed in some way?

@saadrahim
Copy link
Member

I apologize for missing this request. Please let me know if you are still available for me to arrange a review for the content here.

@garrettbyrd
Copy link
Author

@saadrahim I am still interested in submitting this. I am pretty sure there should be no versioning issues (i.e., most if not all versions are specified), but I can do a run through tomorrow to verify. Of course, the date will also need to be changed.

Copy link
Contributor

@Ehud-Sharlin Ehud-Sharlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the effort on this blog! I'm enclosing the first batch of reviews and suggestions on the post, the 2nd (and final) part of my reviews will follow later this evening. Thanks!

---

# Getting Started with Llama 3 on AMD Instinct and Radeon GPUs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are following a consistent magazine article approach where there is no explicit introduction perse, but rather the blog starts with a brief, wide-scoped introductory text before moving into the blog’s first section. This introductory text, with no title, should include a brief description of the blog, and outline concisely what the reader can expect to learn from the post. When outlining the deliverables please use active voice, something along the lines of: “In this blog you will learn…” (see for example: https://rocm.blogs.amd.com/software-tools-optimization/rocm-containers/README.html)

language: English
myst:
html_meta:
"description lang=en": "Getting Started with Llama 3 on AMD Instinct and Radeon GPUs"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This metadata field has 150 char limit which will appear as a snippet for your post on the ROCm Blogs website, please consider adding more details here

date: 23 August 2024
author: Garrett Byrd, Joe Schoonover
tags: LLM, AI/ML, PyTorch, Installation
category: Applications & models
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The blog is currently missing a thumbnail image which will represent it visually on ROCm Blogs, please consider adding a thumbnail image from your end, or if needed let me know and I'll suggest an image from our stock images

myst:
html_meta:
"description lang=en": "Getting Started with Llama 3 on AMD Instinct and Radeon GPUs"
"keywords": "Llama, Llama 3, PyTorch, LLM, Transformer, Attention, ROCm, large language model, AI/ML, Generative AI, Installation"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few recently introduced metadata fields are missing from the blog, I am copying our complete metadata requirements list, below, please let me know if you have any questions:

blogpost: true
blog_title: "Title of blog"
date: Date of blog
author: Author(s) of blog
thumbnail: 'Image name'
tags: LLM, PyTorch, AI/ML, Fine-Tuning
category: Applications & models
language: English
target_audience: The targeted audience(s) of this blog (DevOps, IT, general developers, users, etc.)
key_value_propositions: What are the main goals of this blog, what kind of value proposition does it have for the user?
myst:
html_meta:
"author": "Author(s) of blog"
"description lang=en": "blog snippet text/abstract 150 Characters MAX"
"keywords": "Tag(s) associated with blog content"
"property=og:locale": "en_US"

We are following a consistent magazine article approach where there is no explicit introduction perse, but rather the blog starts with a brief, wide-scoped introductory text before moving into the blog’s first section. This introductory text, with no title, should include a brief description of the blog, and outline concisely what the reader can expect to learn from it. Please use active voice, something along the lines of: “In this blog you will learn…” (see for example: https://rocm.blogs.amd.com/software-tools-optimization/rocm-containers/README.html)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants