-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Localization 2021 #2169
Comments
Happy to join as an editor |
Hi! I would love to be a reviewer. |
|
@excellenseo @shantsis there are still a few days left before the M0 deadline but unfortunately it doesn't look like this chapter will have critical mass to be viable this year. Closing it for now but if there is sudden interest we could reopen it and try to make it work. I'd still encourage you to contribute to any other chapters that may have overlap with localization, perhaps Markup, CSS, JavaScript, or Accessibility would be good places to incorporate some of this content. Thank you for your interest in this chapter. Maybe next year! |
Localization 2021
If you're interested in contributing to the Localization chapter of the 2021 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.
Content team
Expand for more information about each role
Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors.
For an overview of how the roles work together at each phase of the project, see the Chapter Lifecycle doc.
Milestone checklist
0. Form the content team
1. Plan content
2. Gather data
3. Validate results
4. Draft content
5. Publication
Chapter resources
Refer to these 2021 Localization resources throughout the content creation process:
📄 Google Docs for outlining and drafting content
🔍 SQL files for committing the queries used during analysis
📊 Google Sheets for saving the results of queries
📝 Markdown file for publishing content and managing public metadata
The text was updated successfully, but these errors were encountered: