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; }'.
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; }'.
htmlDefaultHead: {
tag: string;
attrs: {
src: string;
'data-site': string;
defer: boolean;
};
}[]
htmlDefaultHead:[
// 예시: Fathom 분석 도구 스크립트 태그를 추가합니다.
{
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,
},
},
],
},
});
head 항목은 HTML 요소로 직접 변환되며, Astro의 스크립트^ 또는 스타일^ 처리를 거치지 않습니다.
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, // 기본값 - 빠른 작업 메뉴를 삽입합니다.
