A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
defaultFrontEndConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'defaultFrontEndConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
defaultFrontEndConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'defaultFrontEndConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
favicon: string
favicon:'/favicon.svg', // STANDARD - Hier wird das Standard-Favicon verwendet.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
defaultFrontEndConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'defaultFrontEndConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
htmlDefaultLanguage: string
htmlDefaultLanguage:'en', // STANDARD - Dabei wird die Standardsprache verwendet.
Füge benutzerdefinierte Tags zum <head> deiner Starlight-Website hinzu.
Das kann nützlich sein, um Analysen und andere Skripte und Ressourcen von Drittanbietern hinzuzufügen.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
defaultFrontEndConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'defaultFrontEndConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
htmlDefaultHead: {
tag: string;
attrs: {
src: string;
'data-site': string;
defer: boolean;
};
}[]
htmlDefaultHead:[
// Beispiel: Fathom analytics script tag hinzufügen.
{
tag: string
tag:'script',
attrs: {
src: string;
'data-site': string;
defer: boolean;
}
attrs:{
src: string
src:'https://cdn.usefathom.com/script.js',
'data-site':'MY-FATHOM-ID',
defer: boolean
defer:true,
},
},
],
},
});
Einträge in head werden direkt in HTML-Elemente umgewandelt und durchlaufen nicht die Skript^- oder Style^-Verarbeitung von Astro.
Fügt eine Benutzeroberfläche für schnelle Aktionen in der rechten unteren Ecke der Hauptseite ein, mit der du schnell zur StudioCMS-Verwaltungsoberfläche navigieren kannst.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
defaultFrontEndConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'defaultFrontEndConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
injectQuickActionsMenu: boolean
injectQuickActionsMenu:true, // STANDARD - Dadurch wird das Schnellaktionsmenü eingefügt.
