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

Daytona DigitalOcean Provider #118

Merged
merged 7 commits into from
Nov 20, 2024
Merged

Conversation

Kiran1689
Copy link
Contributor

@Kiran1689 Kiran1689 commented Nov 14, 2024

fixes #80
/claim #80

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

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.

Signed-off-by: Kiran1689 <[email protected]>
Signed-off-by: Kiran1689 <[email protected]>
Signed-off-by: Kiran1689 <[email protected]>
@Kiran1689
Copy link
Contributor Author

Kiran1689 commented Nov 14, 2024

@mojafa @nkkko
This is the new PR for Daytona DigitalOcean Provider

@Kiran1689
Copy link
Contributor Author

@mojafa Can you please review this?

@mojafa
Copy link
Collaborator

mojafa commented Nov 14, 2024

On it!

@Kiran1689
Copy link
Contributor Author

@mojafa Any changes or improvements needed ?

@mojafa
Copy link
Collaborator

mojafa commented Nov 17, 2024

@Kiran1689 This PR issue should be an article, not a guide.
See here: [https://github.com//issues/80]

I'm creating a Digital Ocean account to test it but all looks well.

Signed-off-by: Kiran1689 <[email protected]>
Signed-off-by: Kiran1689 <[email protected]>
Signed-off-by: Kiran1689 <[email protected]>
Signed-off-by: Kiran1689 <[email protected]>
@Kiran1689
Copy link
Contributor Author

Updated @mojafa

Copy link
Collaborator

@mojafa mojafa left a comment

Choose a reason for hiding this comment

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

@nkkko Article meets requirements.

@Kiran1689
Copy link
Contributor Author

@nkkko 👀

@Kiran1689
Copy link
Contributor Author

@nkkko Can you please look into this?

@nkkko nkkko merged commit 9c20c3a into daytonaio:main Nov 20, 2024
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Daytona DigitalOcean Provider
3 participants