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

Quick Start #372

Closed
11 tasks done
Tracked by #330
resir014 opened this issue Apr 28, 2023 · 5 comments · Fixed by #500 or #561
Closed
11 tasks done
Tracked by #330

Quick Start #372

resir014 opened this issue Apr 28, 2023 · 5 comments · Fixed by #500 or #561
Assignees

Comments

@resir014
Copy link
Member

resir014 commented Apr 28, 2023

Page: https://id.react.dev/learn

Assignee: @mhaidarhanif

PR: #500

Progress

  • Creating and nesting components
  • Writing markup with JSX
  • Adding styles
  • Displaying data
  • Conditional rendering
  • Rendering lists
  • Responding to events
  • Updating the screen
  • Using Hooks
  • Sharing data between components
  • Next Steps
@resir014 resir014 changed the title Quick Start (@infrasync) Quick Start Apr 28, 2023
@mhaidarhanif mhaidarhanif mentioned this issue Apr 29, 2023
11 tasks
@mhaidarhanif mhaidarhanif linked a pull request Apr 29, 2023 that will close this issue
11 tasks
@mhaidarhanif
Copy link
Collaborator

mhaidarhanif commented Apr 29, 2023

Reopen as the Quick Start (https://id.react.dev/learn) /learn wasn't translated yet.

This is the PR: #500

(tbh I've been waiting for so long to get a beautiful number 😂)

@mhaidarhanif mhaidarhanif reopened this Apr 29, 2023
@mhaidarhanif mhaidarhanif self-assigned this Apr 29, 2023
@infrasync
Copy link

is my assignee tasked is canceled @mhaidarhanif @resir014 ? 🤔

@resir014
Copy link
Member Author

resir014 commented May 1, 2023

@infrasync We realised some pages had some assignees mixed up while reworking our workflow so you might be caught up in it, sorry about that!

Last I checked, you have another page assigned to you. So feel free to start from there

@mhaidarhanif
Copy link
Collaborator

mhaidarhanif commented May 1, 2023

@infrasync @resir014 Also because we've waited for a few days and there wasn't any Draft PR / PR for this page yet. Therefore we've taken over and the translation itself is already done here: #500

Since 3~ days ago, we've improved the workflow to prioritize who can work on the pages as soon as possible with a real PR. So it's a fair better chance for all contributors. The goal is to complete the translation progress sooner.

But it's okay to take any available page that's not yet in progress, there are several other open issues/pages here: https://github.com/reactjs/id.react.dev/issues

@r17x r17x closed this as completed in #500 May 11, 2023
@infrasync
Copy link

infrasync commented May 11, 2023

@infrasync @resir014 Also because we've waited for a few days and there wasn't any Draft PR / PR for this page yet. Therefore we've taken over and the translation itself is already in progress and almost done here: #500

Since 3~ days ago, we've improved the workflow to prioritize who can work on the pages as soon as possible with a real PR. So it's a fair better chance for all contributors. The goal is to complete the translation progress sooner.

But it's okay to take any available page that's not yet in progress, there are several other open issues/pages here: https://github.com/reactjs/id.react.dev/issues

It's ok for me, but I would suggest giving information related to what is expected for contributors such as completion plans, especially timelines, because it seems that in the issue description it is not available 🤔. And for accountability, if you switch assignees on an issue, please inform the previous assignee, because like me, who just wants to contribute, it feels like I'm not considered to contribute.

But because there are still several issues available, I still want to contribute, thanks ✨

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 a pull request may close this issue.

3 participants