OrchardCMS / OrchardCMS/OrchardCore.Commerce
Product localization (OCC-77)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 231
- Forks
- 94
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 1
Description
We'll need to design product localization. The easy part is products themselves, as products are content items, and content items are localizable by Orchard. There are harder things such as product attribute settings localization, as some of those settings will make their way to the front-end.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Jira issue OCC-77 and the issue's distinction between products as localizable content items and product attribute settings exposed on the front end. Define the localization scope for product attributes and identify how Orchard currently localizes content items. Done should include an agreed approach for both product content and relevant settings, but the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100