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

Update 2-codespace-lifecycle.md #73

Open
wants to merge 1 commit into
base: github-codespaces
Choose a base branch
from

Conversation

camihmerhar
Copy link
Collaborator

I moved the header for the Codespaces vs dev editor up a bit more and broke up the paragraph a bit since it seemed dense.

Another piece of feedback I would recommend that Aaron preaches is driving the why. I would add and merge this paragraph I found from the following blog to the opening paragraph of the learning unit , https://github.blog/2023-05-10-revolutionize-your-open-source-workflows-the-top-3-reasons-why-github-codespaces-is-a-must-have-for-maintainers/

"GitHub Codespaces is a revolutionary cloud-based development environment that makes it easier than ever to create, manage, and collaborate on code in the cloud. You can spin up a pre-configured development environment in no time, complete with all the tools and dependencies you need to get started on your project. If you’re new to GitHub Codespaces, you can learn how to get started here.

This streamlined process eliminates the need for manual configuration tasks, freeing up valuable time for you and your contributors. And with GitHub Codespaces, contributors can easily access their IDE from anywhere with an internet connection. This means they can work on your project from any device, at any time, without worrying about compatibility issues."

Also I would recommend creating a new learning unit to encompass everything after the table. This unit seems a bit long.

I moved the header for the Codespaces vs dev editor up a bit more and broke up the paragraph a bit since it seemed dense. 

Another piece of feedback I would recommend that Aaron preaches is driving the why. I would add and merge this paragraph I found from the following blog to the opening paragraph of the learning unit , https://github.blog/2023-05-10-revolutionize-your-open-source-workflows-the-top-3-reasons-why-github-codespaces-is-a-must-have-for-maintainers/ 

"GitHub Codespaces is a revolutionary cloud-based development environment that makes it easier than ever to create, manage, and collaborate on code in the cloud. You can spin up a pre-configured development environment in no time, complete with all the tools and dependencies you need to get started on your project. If you’re new to GitHub Codespaces, you can learn how to get started here.

This streamlined process eliminates the need for manual configuration tasks, freeing up valuable time for you and your contributors. And with GitHub Codespaces, contributors can easily access their IDE from anywhere with an internet connection. This means they can work on your project from any device, at any time, without worrying about compatibility issues."

Also I would recommend creating a new learning unit to encompass everything after the table. This unit seems a bit long.
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.

1 participant