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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
dashboardEnabled: boolean
dashboardEnabled:true, // STANDARD - Dadurch wird das Dashboard aktiviert.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
dashboardRouteOverride: string
dashboardRouteOverride:'dashboard', // STANDARD - Damit wird die Dashboard-Route auf /dashboard gesetzt.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
developerConfig: {
demoMode: boolean;
}
developerConfig:{
demoMode: boolean
demoMode:false, // STANDARD - Dadurch wird der Demomodus deaktiviert.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
faviconURL: string
faviconURL:'/favicon.svg', // STANDARD - Damit wird das Favicon für das Dashboard festgelegt.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
inject404Route: boolean
inject404Route:true, // STANDARD - Dadurch wird die Route 404 injiziert.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
versionCheck: boolean
versionCheck:true, // STANDARD - Dies aktiviert Versionskontrolle.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
typeAuthConfig: {
enabled: boolean;
}
AuthConfig:{
enabled: boolean
enabled:true, // STANDARD - Dies aktiviert Authentifizierung.
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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' 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; }'.
typeAuthConfig: {
providers: {
usernameAndPassword: boolean;
usernameAndPasswordConfig: {
allowUserRegistration: boolean;
};
};
}
AuthConfig:{
providers: {
usernameAndPassword: boolean;
usernameAndPasswordConfig: {
allowUserRegistration: boolean;
};
}
providers:{
usernameAndPassword: boolean
usernameAndPassword:true,
usernameAndPasswordConfig: {
allowUserRegistration: boolean;
}
usernameAndPasswordConfig:{
allowUserRegistration: boolean
allowUserRegistration:true, // STANDARD - Dies ermöglicht die Registrierung von Nutzern.