> For the complete documentation index, see [llms.txt](https://bryan-guner.gitbook.io/duke/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bryan-guner.gitbook.io/duke/meetings/week-1/week-2/day-3.md).

# Day 3

Checking spanish translations in sitecore.

\[9:55 AM] Haberman, Scot I changed the profile and you should be able to translate anything under the Content node.

Do we have a script for automatically approving translations ... to move the status without automatically publishing?

\[9:55 AM] Haberman, Scot Do NOT do a blanket translate on the high level content node...that is a lot of data. like 2

\[9:57 AM] Pope, Spencer O Holly, Joshua Randel investors page looks good, but there should also be a stockticker on https: //sctest.duke-energy.com/our-company like 1 Our Company - Duke Energy Duke Energy makes life better for millions of people every day by providing electric and gas services in a sustainable way - affordable, reliable and clean.

### Metadata :

\[9:59 AM] 9:59 AM Meeting ended: 1h 15m 32s

{% hint style="info" %}
How do we translate meta data in the cms?
{% endhint %}

{% hint style="info" %}
The translations aren't picking up any words to translate. I guess it's because we're using the text portion of the link field. Is there any way to get it to see that?
{% endhint %}

\[10:14 AM] Holly, Joshua Randel

there are CTA's across the site that would also need that text to be picked up and translated

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bryan-guner.gitbook.io/duke/meetings/week-1/week-2/day-3.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.