Internationalizing exhibit pages

Open
#124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php

Research direction

Start by reading helpers/ExhibitPageFunctions.php around line 13, the only implementation location identified in the issue. Determine whether exhibit page content is currently handled there and what scope would be required for translation. Done means establishing a clear, working way for exhibit page text to be internationalized.

Written by the indexing model from the issue text.

Description

I've been trying to see if I can internationalize exhibit pages so that some of the text will translate. I believe this is the section that needs work (https://github.com/omeka/plugin-ExhibitBuilder/blob/cc9c90364d8a0f66eeda2322e3d2016396d625fc/helpers/ExhibitPageFunctions.php#L13) but I haven't been able to work it out. Is there a way to internationalize the exhibit page content itself? Thank you for your help.

Dominant language
PHP
Stars
25
Forks
37
Avg merge
5d 19h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from omeka/plugin-ExhibitBuilder

All issues in omeka/plugin-ExhibitBuilder

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.