Answers.Body: <p>I think the error is to do with the fact that you are using backticks (slanted quote) instead of single/double quote marks.</p>
  <p>Copy/paste the below and it should work for you</p>
  <pre><code>&lt;?php
  
  return [
    'UNIQUE_KEY_NAME' =&gt; 'This should now work',
  ];
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-20T10:05:57.390Z
Answers.Text: OMG! This is such an epic facepalm. I'm so used to using backticks in JavaScript now! This is what happens... I literally never post any support requests, then when I do, they end up being the dumbest thing ever because I'm "having one of those days". Jeez. Thank you so much for honouring my stupidity with a polite reply. ‍♂️
Answers.UserDisplayName: tomkiss
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-17T13:49:56.673Z
Answers.LastActivityDate: 2020-07-17T13:49:56.673Z
Answers.UserDisplayName: Oli
Body: <p>I'm having trouble outputting static translations for the primary site, and only the primary site.</p>
  <p><strong>Translations structure:</strong></p>
  <ul>
  <li>translations
  <ul>
  <li>en-US
  <ul>
  <li>site.php</li>
  </ul>
  </li>
  </ul>
  </li>
  </ul>
  <p><strong>site.php</strong></p>
  <pre><code>&lt;?php
  
  return [
    'UNIQUE_KEY_NAME' =&gt; `This is the string I'd like to appear.`,
  ];
  </code></pre>
  <p><strong>Template</strong></p>
  <pre><code>{{ 'UNIQUE_KEY_NAME' | t }}
  </code></pre>
  <p><strong>Output</strong></p>
  <pre><code>UNIQUE_KEY_NAME
  </code></pre>
  <p>Is there a way to make this pattern work?
  The advantage of storing microcopy and site furniture in a single location is that it is much easier to update and share with copywriters.</p>
  <p>If there is a second site, then it appears the site.php for that language will be respected, but when there is just one site, the primary site, its corresponding site.php translation file appears to be ignored. Is this intended?</p>
  <p>Thanks </p>
  
Tags: <localization>
Title: Using static translations for the primary site / site.php being ignored
ThreadText: # Using static translations for the primary site / site.php being ignored
  
  (Asked by: username_0 on 2020-07-17)
  
  I'm having trouble outputting static translations for the primary site, and only the primary site.
  
  **Translations structure:**
  
  * translations
    + en-US
      - site.php
  
  **site.php**
  
  ```
  <?php
  
  return [
    'UNIQUE_KEY_NAME' => `This is the string I'd like to appear.`,
  ];
  
  ```
  
  **Template**
  
  ```
  {{ 'UNIQUE_KEY_NAME' | t }}
  
  ```
  
  **Output**
  
  ```
  UNIQUE_KEY_NAME
  
  ```
  
  Is there a way to make this pattern work?
  The advantage of storing microcopy and site furniture in a single location is that it is much easier to update and share with copywriters.
  
  If there is a second site, then it appears the site.php for that language will be respected, but when there is just one site, the primary site, its corresponding site.php translation file appears to be ignored. Is this intended?
  
  Thanks
  
  **Tags:** localization
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-07-17. Score: 1 | Accepted answer
  
  I think the error is to do with the fact that you are using backticks (slanted quote) instead of single/double quote marks.
  
  Copy/paste the below and it should work for you
  
  ```
  <?php
  
  return [
    'UNIQUE_KEY_NAME' => 'This should now work',
  ];
  
  ```
  
  > **Comments:**
  > **username_0**: OMG! This is such an epic facepalm. I'm so used to using backticks in JavaScript now! This is what happens... I literally never post any support requests, then when I do, they end up being the dumbest thing ever because I'm "having one of those days". Jeez. Thank you so much for honouring my stupidity with a polite reply. ‍♂️  
  
  ---
  
  