Skip to content

Conversation

@jainpawan21
Copy link
Member

@jainpawan21 jainpawan21 commented Jul 27, 2025

Summary by CodeRabbit

  • New Features

    • Introduced a new documentation page detailing how to enable and manage multi-language translations for workflow notifications, including setup, usage, and best practices.
  • Documentation

    • Updated the workflow creation guide to include the new "Enable translations" option with a direct link to the translations documentation.
    • Added the new translations documentation page to the "Building Workflows" section for easier navigation.

@linear
Copy link

linear bot commented Jul 27, 2025

@netlify
Copy link

netlify bot commented Jul 27, 2025

Deploy Preview for docs-novu ready!

Name Link
🔨 Latest commit 6a96433
🔍 Latest deploy log https://app.netlify.com/projects/docs-novu/deploys/6888de3d28041a0008c53430
😎 Deploy Preview https://deploy-preview-910--docs-novu.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 27, 2025

Walkthrough

A new documentation page detailing workflow translations has been added and integrated into the documentation navigation. The workflow creation guide was updated to reference the new translation feature, including instructions on enabling translations and linking to the dedicated documentation page.

Changes

File(s) Change Summary
Documentation Navigation
content/docs/platform/meta.json
Added "workflow/translations" page to the documentation navigation under "Building Workflows".
Workflow Creation Guide
content/docs/platform/workflow/build-a-workflow.mdx
Updated workflow creation docs to include the new "Enable translations" option and link to details.
New Translations Documentation
content/docs/platform/workflow/translations.mdx
Added comprehensive new documentation page explaining the workflow translation feature.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docs
    participant WorkflowFeature

    User->>Docs: Reads "Build a Workflow" guide
    Docs-->>User: Shows "Enable translations" option
    User->>Docs: Follows link to "Translations" documentation
    Docs-->>User: Explains translation setup and management
    User->>WorkflowFeature: Configures translations as per documentation
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • Aviatorscode2
  • DianaHackmamba

Poem

In the docs a new page appears,
For workflows in many frontiers.
Now translations are clear,
With guidance right here—
Multilingual joy, as the feature premieres!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bbdb431 and 6a96433.

📒 Files selected for processing (2)
  • content/docs/platform/meta.json (1 hunks)
  • content/docs/platform/workflow/translations.mdx (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • content/docs/platform/workflow/translations.mdx
  • content/docs/platform/meta.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Redirect rules - docs-novu
  • GitHub Check: Header rules - docs-novu
  • GitHub Check: Pages changed - docs-novu
  • GitHub Check: Build and Lint
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch MRK-962

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
content/docs/platform/workflow/translations.mdx (4)

33-36: Use the correct ISO code for Japanese locale

jp_JP is not a valid BCP 47/ISO locale. The correct code is ja_JP.

- - Add target locales you wish to support (e.g., `fr_FR`, `es_ES`, `jp_JP`, etc.).
+ - Add target locales you wish to support (e.g., `fr_FR`, `es_ES`, `ja_JP`, etc.).

59-60: Capitalize “JSON” for consistency

- Translation json files can be updated using JSON editor on the translation page.
+ Translation JSON files can be updated using the JSON editor on the translation page.

96-99: Grammar & clarity in translation-key explanation

-In Email or In-App editors, use `{{t.key}}` to insert a translatable string. if key is already added in the locale, it will be in the suggestions list.
+In Email or In-App editors, use `{{t.key}}` to insert a translatable string. If the key already exists for the locale, it appears in the suggestions list.

125-126: Typo: “react out” → “reach out”

-This feature is currently in work in progress. If you are looking to use translation in email layouts, react out to us at [email protected]
+This feature is currently a work in progress. If you need translation support in email layouts, reach out to us at [email protected]
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 712aa76 and 32ca981.

⛔ Files ignored due to path filters (4)
  • public/images/platform/workflow/translations/translations-default-and-target-locale.gif is excluded by !**/*.gif
  • public/images/platform/workflow/translations/translations-page.png is excluded by !**/*.png
  • public/images/platform/workflow/translations/translations_locale_content_edit.gif is excluded by !**/*.gif
  • public/images/platform/workflow/translations/translations_variable_use_in_step_editor.gif is excluded by !**/*.gif
📒 Files selected for processing (3)
  • content/docs/platform/meta.json (1 hunks)
  • content/docs/platform/workflow/build-a-workflow.mdx (1 hunks)
  • content/docs/platform/workflow/translations.mdx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Redirect rules - docs-novu
  • GitHub Check: Header rules - docs-novu
  • GitHub Check: Pages changed - docs-novu
  • GitHub Check: Build and Lint
🔇 Additional comments (2)
content/docs/platform/workflow/build-a-workflow.mdx (1)

18-18: Addition looks correct – no action needed

The new “Enable translations” bullet is clearly phrased, correctly indented, and the relative link resolves to the new documentation page.

content/docs/platform/meta.json (1)

24-27: Navigation entry inserted in the right place

workflow/translations is positioned logically between “build-a-workflow” and “template-editor”, matching the docs flow.

Copy link
Contributor

@DianaHackmamba DianaHackmamba left a comment

Choose a reason for hiding this comment

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

I did not complete the review. @Aviatorscode2, review the self editing checklist and edit this topic, then re-request a review.

Inconsistent headings, missing periods, passive voice, and use of e.g. and etc. are all items on the checklist that you should fix before requesting an edit from me.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (2)
content/docs/platform/workflow/translations.mdx (2)

7-7: Remove stacked H2 heading “Workflow translations”

The page title in the front-matter already renders as an H1; leaving this H2 directly below creates a stacked-heading anti-pattern.
[past review comment → same concern]


31-41: Use ordered steps instead of bullets for workflow-creation actions

Turning on a toggle, setting a default locale, then adding target locales is a sequence. Numbered steps improve clarity and match Google style.

🧹 Nitpick comments (5)
content/docs/platform/workflow/translations.mdx (5)

23-23: Fix link formatting & wording

Missing space before the link and “Novu dashboard” should be preceded by “the”.

-You can manage translations on the[translation page](https://dashboard.novu.co/translations) on Novu dashboard.
+You can manage translations on the [translation page](https://dashboard.novu.co/translations) in the Novu dashboard.

80-80: Eliminate redundant phrase “outside of”

Google style recommends simply “outside”.

-...translations in a JSON file outside of the Novu dashboard...
+...translations in a JSON file outside the Novu dashboard...

95-95: Tweak emphasis formatting

*Outdated, needs update* mixes italics with comma; consider:

-*Outdated, needs update*
+*Outdated – needs update*

99-99: Grammar: possessive form of “default locale”

-...contains the default locale' translations keys...
+...contains the default locale’s translation keys...

117-129: Mention support for nested translation keys

Customers can use keys like {{t.title.button.submit}}; adding a brief note here prevents confusion.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 29610f9 and bbdb431.

⛔ Files ignored due to path filters (1)
  • public/images/platform/workflow/translations/translations_master_json_file.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • content/docs/platform/workflow/translations.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/docs/platform/workflow/translations.mdx

[style] ~80-~80: This phrase is redundant. Consider using “outside”.
Context: ...eate/update translations in a JSON file outside of the Novu dashboard, you can do so by ex...

(OUTSIDE_OF)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Redirect rules - docs-novu
  • GitHub Check: Header rules - docs-novu
  • GitHub Check: Pages changed - docs-novu
  • GitHub Check: Build and Lint

Copy link
Contributor

@Aviatorscode2 Aviatorscode2 left a comment

Choose a reason for hiding this comment

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

The structure/developer journey of the page is broken. I went through the feature step by step and this is the structure the content was supposed to take:

  • Set up translations
  • Enable translation in a workflow
  • Using transition in In-app and Email step editor
    • Translation JSON
    • Import translations
  • Manage translations
    • Configure translations settings
    • Import
    • Export
    • Delete and disable translations

Not sure we can fix this today since the docs needs to be live, but I am happy to hear suggestions @DianaHackmamba @jainpawan21

Copy link
Contributor

@Aviatorscode2 Aviatorscode2 left a comment

Choose a reason for hiding this comment

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

I believe this is to go for now. We can set out time later (When I start working on the Building workflow section to work on it again)

@jainpawan21 jainpawan21 merged commit faa2c9d into main Jul 29, 2025
7 checks passed
@jainpawan21 jainpawan21 deleted the MRK-962 branch July 29, 2025 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants