Skip to content

docs(ar): add Arabic translation for documentation pages#8252

Open
RlxChap2 wants to merge 20 commits into
webpack:mainfrom
RlxChap2:main
Open

docs(ar): add Arabic translation for documentation pages#8252
RlxChap2 wants to merge 20 commits into
webpack:mainfrom
RlxChap2:main

Conversation

@RlxChap2
Copy link
Copy Markdown

Summary

this is in progress PR for the Arabic translation of webpack.js.org documentation, also this PR is opened to make it easier to keep the translation branch up to date with upstream changes and resolve merge conflicts as they appear this Translation work is still ongoing

What kind of change does this PR introduce?

docs

Did you add tests for your changes?

no this is a documentation/translation-only change, also ig we will change the translation in the codes:
example: Print Page we will change it from the code to Arabic and it will be like: طباعة الصفحة

Does this PR introduce a breaking change?

no

If relevant, what needs to be documented once your changes are merged or what have you already documented?

translated documentation is included in this PR More translated pages will be be added

Use of AI

no AI was used for the translation changes

@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
webpack-js-org Ready Ready Preview, Comment May 22, 2026 2:40pm

Request Review

@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla Bot commented May 20, 2026

CLA Missing ID

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

  1. Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
  2. Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
  3. Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
  4. Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
  5. login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

@github-actions
Copy link
Copy Markdown

👋 Hi there! This PR was automatically flagged and closed by our quality checks.

If you believe this was a mistake, please review our contributing guidelines
and leave a comment explaining why this is a mistake.

@github-actions
Copy link
Copy Markdown

👋 Hi there! This PR was automatically flagged and closed by our quality checks.

If you believe this was a mistake, please review our contributing guidelines
and leave a comment explaining why this is a mistake.

@github-actions github-actions Bot closed this May 20, 2026
@alexander-akait
Copy link
Copy Markdown
Member

@RlxChap2 reopen, looks like our check is a little bit aggressive

@github-actions
Copy link
Copy Markdown

👋 Hi there! This PR was automatically flagged and closed by our quality checks.

If you believe this was a mistake, please review our contributing guidelines
and leave a comment explaining why this is a mistake.

@github-actions github-actions Bot closed this May 20, 2026
@alexander-akait
Copy link
Copy Markdown
Member

Also let's rebase

@alexander-akait
Copy link
Copy Markdown
Member

alexander-akait commented May 20, 2026

/cc @avivkeller How to say to our bot don't close after reopen?

@github-actions
Copy link
Copy Markdown

👋 Hi there! This PR was automatically flagged and closed by our quality checks.

If you believe this was a mistake, please review our contributing guidelines
and leave a comment explaining why this is a mistake.

@RlxChap2
Copy link
Copy Markdown
Author

@RlxChap2 reopen, looks like our check is a little bit aggressive

oh i see, so what is the solution rn ?

@RlxChap2
Copy link
Copy Markdown
Author

Also let's rebase

yeah i did a rebase in the another pr #8253

@avivkeller avivkeller reopened this May 20, 2026
@github-actions

This comment has been minimized.

@github-actions github-actions Bot closed this May 20, 2026
@avivkeller avivkeller reopened this May 20, 2026
@avivkeller
Copy link
Copy Markdown
Member

/cc @avivkeller How to say to our bot don't close after reopen?

The ‘exempt’ label, which we can customize to a different name if needed

@alexander-akait
Copy link
Copy Markdown
Member

@RlxChap2 can you rebase?

@avivkeller
Copy link
Copy Markdown
Member

For reference, this PR was blocked because several files did not end in a newline AND a commit exceeded 500 characters. Fixing one of those in future PRs will prevent a block

@RlxChap2
Copy link
Copy Markdown
Author

@RlxChap2 can you rebase?

For reference, this PR was blocked because several files did not end in a newline AND a commit exceeded 500 characters. Fixing one of those in future PRs will prevent a block

yeah sure lemme try to fix those

Translate initial blog and configuration index content to Arabic while preserving MDX structure.

Co-authored-by: ameencfw <ameencfw@users.noreply.github.com>
Co-authored-by: Shimizu Hiroyuki <amtixdev@gmail.com>
Copy link
Copy Markdown
Member

@evenstensberg evenstensberg left a comment

Choose a reason for hiding this comment

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

I think we should branch this out in a unique deploy, like we do here

https://www.webpack-china.org/

@RlxChap2
Copy link
Copy Markdown
Author

I think we should branch this out in a unique deploy, like we do here

https://www.webpack-china.org/

ig that will be fine because we maybe change the layout like i said the this issue #8246

@alexander-akait
Copy link
Copy Markdown
Member

Let's fix lint and e2e test, also I think we need a component to switch languages

@RlxChap2
Copy link
Copy Markdown
Author

RlxChap2 commented May 22, 2026

Let's fix lint and e2e test, also I think we need a component to switch languages

I'll fix the lint and E2E failures first for the language switcher also i can add a simple component for switching between any lang and Arabic in this PR unless you prefer a follow-up PR

@RlxChap2
Copy link
Copy Markdown
Author

RlxChap2 commented May 22, 2026

hello, i tried my best to investigate what is happening and tried to fix the lint but idk why it's not working

it shows to me something like

Error:   388:201  error  Insert `⏎⏎````        prettier/prettier

also i changed the language switcher section to another new components to be easier to put the link and data

@RlxChap2
Copy link
Copy Markdown
Author

RlxChap2 commented May 22, 2026

finally i fixed all of them

is it good rn ? @alexander-akait

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants