-
|
On the themeConfig->metadata object, I'm unsure on how to add the following script tag: <script id="usercentrics-cmp" src="https://app.usercentrics.eu/browser-ui/latest/loader.js" data-settings-id="ID" async></script>My attempt (not sure if this is correct at all): {
tagName: 'script',
async: true,
attributes: {
id: 'usercentrics-cmp',
src: 'https://app.usercentrics.eu/browser-ui/latest/loader.js',
'data-settings-id': 'ID',
}
},What would be the correct way for adding a script tag that also has an id and data attribute? Would this be correct? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
|
We have multiple ways to do that, but what makes you think this one is incorrect? Isn't the tag in the output HTML when you add it this way? |
Beta Was this translation helpful? Give feedback.
-
|
I think I know what the issue is now. |
Beta Was this translation helpful? Give feedback.
-
|
That's the point of proving it: you figure out things on your own by being more careful while creating a https://docusaurus.new repro. I knew what the problem was, but what matters to me is that you adopt the right mindset for reporting issues. You have to double-check the doc, and provide a runnable code example. Otherwise I won't be helpful, because you put the burden on me to interpret your text and create the that repro for you. My time is better spent implementing features and fixing actual bugs rather than helping a single user. |
Beta Was this translation helpful? Give feedback.
-
|
@slorber I tested it more thoroughly and I've found out the following: The method shown here does not automatically add the defined The solution was to create a custom component that makes use of I'll try to get a repro running when I find the time for it. Component.js import React from 'react';
import Head from '@docusaurus/Head';
export default function GlobalHead() {
return (
<Head>
{/* Cookie Consent */}
<script id="usercentrics-cmp" src="https://app.usercentrics.eu/browser-ui/latest/loader.js" data-settings-id="..." async></script>
{/* Web Analytics */}
<script defer data-domain="..." src="https://plausible.io/js/script.js"></script>
</Head>
)
}
...Swizzled Layout component ( import React from 'react';
import Layout from '@theme-original/Layout';
import GlobalHead from '@site/src/components/GlobalHead';
export default function LayoutWrapper(props) {
return (
<>
<GlobalHead />
<Layout {...props} />
</>
);
}Follow-up question: how global is the |
Beta Was this translation helpful? Give feedback.
-
|
If you think there's a bug, show it with a repro. Afaik headTags are not a
|
Beta Was this translation helpful? Give feedback.
-
|
@slorber Will do, thanks! I'll put in a PR in case the docs do in fact got a typo. |
Beta Was this translation helpful? Give feedback.
-
|
Great Apparently, we have an issue for that doc problem already: This doc page is not new, not sure why it only surfaces now |
Beta Was this translation helpful? Give feedback.
If you think there's a bug, show it with a repro.
It's possible there is a bug, but unless a repro is provided it's not proven.
Afaik headTags are not a
themeConfigattribute but asiteConfigattribute. It might just be a docs typo on the SEO docs page.https://docusaurus.io/docs/next/api/docusaurus-config#headTags
themeConfig.metadatashould work<Head>is not deprecated. You can achieve the same result in multiple ways according to your need.<Head>is the most granular and can be applied on a per-page basis