Article to create your First Dev Container Project

[vikashsprem]

/claim #64
/closed #64

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.

[algora-pbc]

💵 To receive payouts, sign up on Algora, link your Github account and connect with Stripe.

[vikashsprem]

@nkkko Please review the PR.

[ntekim]

Is this still open or closed? I mean a PR was submitted but I still see the open tag.

[mojafa]

@vikashsprem thank you for your patience.

Here are the changes you should make:

• Please fill out the author section and add image assets. you could refer to the CONTRIBUTING.md

• See below, your artilce lacks consistent title and subtitle headings.

![Uploading Screenshot 2024-11-29 at 07.30.19.png…]()

[mojafa]

@vikashsprem Could you please also add screenshots of how the Open the Project in Daytona works. I see you've shared commands, please show terminal results of that. Please expand on this section

[vikashsprem]

Thank you @mojafa for letting me. I will resolve and let you know.

[mojafa]

@vikashsprem any updates?

[vikashsprem]

Hey @mojafa, I have made suggested changes, Plz review.

[mojafa]

Please take time and address the requested changes.

See below, your artilce lacks consistent title and subtitle headings.

Please share screenshots of how these commands work

i dont think we have this command daytona create test -r <repo> --skip-ide

[vikashsprem]

**1 pending reviewer **

Hey @mojafa, I have fixed the title and subtitle headings consistency and added a shot to create the workspace, below step 3 have a reference so that you can verify the command. I might be looking at the previous commit (Check out the latest commit I made in which I addressed all the suggestions). Thanks

Daytonaio workspace create ref: https://www.daytona.io/docs/usage/workspaces/

[vikashsprem]

Please take time and address the requested changes.

See below, your artilce lacks consistent title and subtitle headings.

**Please share screenshots of how these commands work**

i dont think we have this command daytona create test -r <repo> --skip-ide

There is no Step 3a: in the latest changes. You might be missing the latest change. Please, look into it.

[mojafa]

Looking into it

[mojafa]

I'm still seeing the same stuff.

[mojafa]

See below.

Please also share some screenshots of how the codes/commands work.

[vikashsprem]

Hey @mojafa, Now I have fixed the command. Plz look into it, Let me know if there is any issue?

[mojafa]

@vikashsprem thanks for the update.

Here's my feedback:

1. in your devcontainer,json file, you have this: set the remote user to developer ,but have the configs commented out. May be you could expand on each command or config in the devcontainer.json file for people to understand.

2. I don't know why you have a rebuild in Container after the workspace opens. Logically, you could add that after the user makes changes step. Like after step 4

3. Also i haven;t seen any mention of the folder .devcontainer where your devcontainer.json will be

[mojafa]

we're almost good to go