dotCMS / dotCMS/core

Default Language based on site instead of Environment

Open
#31,245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Falcon Type : New Functionality
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

No response

User Story

As a user, I want to be able to set a default language per site instead of the entire environment, so I can have content creators for sites in different locations not have to worry about selecting the correct language from the drop down menu.

For example,

  • Content Creator A is Spanish and working on our Spanish web page.
  • Content Creator B is Portuguese and working on our Portuguese web page.

Instead of having to make sure they are selecting the correct language every time they create content, being able to set a default would help circumvent a lot of misplaced content.

Acceptance Criteria

The ability to set a default language based on site, instead of the entire environment.

Proposed Objective

User Experience

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.freshdesk.com/a/tickets/29380

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by tracing how the current environment-wide default language is configured and how the active site is represented, then review support ticket 29380. Done means each site can have its own default language so content creators do not need to select it for every item.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
content, internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.