DevOps:Doc/Open CSP/2.0/Class definition customization options - Revision history

81d56153-9868-4094-90a0-df1700ff7090: Text replacement - "{{Doc properties" to "{{Csp class properties"

2025-07-15T09:01:15Z

Text replacement - "{{Doc properties" to "{{Csp class properties"

ws-class-props
← Older revision		Revision as of 11:01, 15 July 2025
Line 1:		Line 1:
	{{~~Doc~~ properties		{{Csp class properties
	\|Subject version=2.0		\|Subject version=2.0
	\|Doc subject=DevOps:Doc/Open CSP		\|Doc subject=DevOps:Doc/Open CSP

Fa773648-6215-4a15-868a-59c60958eda1 at 09:39, 11 April 2024

2024-04-11T09:39:29Z

← Older revision		Revision as of 11:39, 11 April 2024
Line 13:		Line 13:
	* All fields that are filled for a parameter will be passed to the templates so they can be accessed through template parameters there. For example you can use <nowiki>{{{allowedValues\|}}}</nowiki> in a formfieldTemplate. It might be useful to look at the csp-data slot of the class definition to see all of the parameters.		* All fields that are filled for a parameter will be passed to the templates so they can be accessed through template parameters there. For example you can use <nowiki>{{{allowedValues\|}}}</nowiki> in a formfieldTemplate. It might be useful to look at the csp-data slot of the class definition to see all of the parameters.
	* The values of parameters on a content page are also passed to the display/formfield templates as the "value" parameter.		* The values of parameters on a content page are also passed to the display/formfield templates as the "value" parameter.
	* In a display/formfield template you cannot access values of other parameters directly, but you can do this by using <nowiki>{{#invoke:CspFunctions\|~~getParentArgs~~\|$pageData}}</nowiki>, which will return the $pageData parameter that is used in '''Template:Csp default sidebar''' (and contains an [[mediawikiwiki:Extension:ArrayFunctions\|ArrayFunctions]] export with slotdata of the page).		* In a display/formfield template you cannot access values of other parameters directly, but you can do this by using <nowiki>{{#invoke:CspFunctions\|getParentArg\|$pageData}}</nowiki>, which will return the $pageData parameter that is used in '''Template:Csp default sidebar''' (and contains an [[mediawikiwiki:Extension:ArrayFunctions\|ArrayFunctions]] export with slotdata of the page).
	* It is possible to add fields to the json data in the csp-data slot that cannot be filled through the parameters form. For example Open CSP 2.0 does not yet include the option to specify a placeholder for your formfields, but you can add placeholder to the json data and then use <nowiki>{{{placeholder\|}}}</nowiki> in a custom formfieldTemplate.		* It is possible to add fields to the json data in the csp-data slot that cannot be filled through the parameters form. For example Open CSP 2.0 does not yet include the option to specify a placeholder for your formfields, but you can add placeholder to the json data and then use <nowiki>{{{placeholder\|}}}</nowiki> in a custom formfieldTemplate.

Ebc16062-dd09-4928-8cf3-821f492b0c44 at 12:02, 31 October 2023

2023-10-31T12:02:03Z

← Older revision		Revision as of 14:02, 31 October 2023
Line 1:		Line 1:
	In '''Open CSP 2.0''' the default sidebar was added, this allows you to have sidebars without having to create custom sidebar templates for each class definition. There are some customization options built into the default sidebar as well. It is recommended to use these customization options when possible and to only create fully custom sidebar templates when absolutely necessary, as the fully custom sidebar templates require a lot more maintenance work when for example some parserfunctions get deprecated or changed. This document describes the various customization options.		In '''Open CSP 2.0''' the default sidebar was added, this allows you to have sidebars without having to create custom sidebar templates for each class definition. There are some customization options built into the default sidebar as well. It is recommended to use these customization options when possible and to only create fully custom sidebar templates when absolutely necessary, as the fully custom sidebar templates require a lot more maintenance work when for example some parserfunctions get deprecated or changed. This document describes the various customization options. Note that it is also possible to configure class definitions to use custom templates for the sub-header and footer components, however these do not have extensive customization options like the sidebar and are therefore not described further in this document.

	== Parameters and formfield/display templates ==		== Parameters and formfield/display templates ==

Charlot: User:Charlot

2023-10-27T18:19:47Z

User:Charlot

ws-seo
← Older revision	Revision as of 20:19, 27 October 2023
Line 1:	Line 1:
		{{SEO
		\|Title=Open CSP Customizing class definitions
		\|Keywords=OpenCSP,class,definitions,documentation
		\|Description=In Open CSP 2.0 the default sidebar was added, this allows you to have sidebars without having to create custom sidebar templates for each class definition. Here we explain all the customizing options you can do.
		\|Image=OCSP-Documentation.jpg
		\|Image alt=Open CSP Documentation Banner
		\|Section=Documention/Open_CSP
		\|Published time=2023-10-01
		}}

Ebc16062-dd09-4928-8cf3-821f492b0c44: User:Ebc16062-dd09-4928-8cf3-821f492b0c44

2023-10-05T11:03:30Z

User:Ebc16062-dd09-4928-8cf3-821f492b0c44

ws-class-props
← Older revision		Revision as of 13:03, 5 October 2023
Line 4:		Line 4:
	\|Doc synopsis=Customizing default sidebar options		\|Doc synopsis=Customizing default sidebar options
	\|Doc parent=DevOps:Doc/Open CSP/2.0/Class definitions		\|Doc parent=DevOps:Doc/Open CSP/2.0/Class definitions
	\|Doc sort order=10		\|Doc sort order=1
	\|Doc target group=Administrator		\|Doc target group=Administrator
	}}		}}

Ebc16062-dd09-4928-8cf3-821f492b0c44: /* Fully custom sidebar template */

2023-10-05T09:06:32Z

Fully custom sidebar template

← Older revision		Revision as of 11:06, 5 October 2023
Line 47:		Line 47:
	</div><!-- end of .card-header -->		</div><!-- end of .card-header -->
	<div class="card-body">		<div class="card-body">
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=Title		\|Label=Title
	\|Value={{#af_get:{{{$pageData}}}\|csp-base-props\|Base properties\|1\|Title \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-base-props\|Base properties\|1\|Title \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=TextInput		\|Label=TextInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextInput \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=TokenInput		\|Label=TokenInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenInput \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=AskTokenInput		\|Label=AskTokenInput
	\|Value={{#af_join:{{#af_map:{{#af_split:{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|AskTokenInput \|_text}}\|,}}\|@@\|[[{{{@@}}}\|{{#show:{{{@@}}}\|?Title}}]]}}\|<br>}}		\|Value={{#af_join:{{#af_map:{{#af_split:{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|AskTokenInput \|_text}}\|,}}\|@@\|[[{{{@@}}}\|{{#show:{{{@@}}}\|?Title}}]]}}\|<br>}}
Line 63:		Line 63:
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInput \|_text}}
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=DateInputTwo		\|Label=DateInputTwo
	\|Value={{#if:{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInputTwo \|_text}} \|{{#time: j M Y H:i \|{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInputTwo \|_text}} }} }}		\|Value={{#if:{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInputTwo \|_text}} \|{{#time: j M Y H:i \|{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInputTwo \|_text}} }} }}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=TextInputTwo		\|Label=TextInputTwo
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextInputTwo \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextInputTwo \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=CheckboxInput		\|Label=CheckboxInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|CheckboxInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|CheckboxInput \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=TextAreaInput		\|Label=TextAreaInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextAreaInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextAreaInput \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=NumberInput		\|Label=NumberInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|NumberInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|NumberInput \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=SelectInput		\|Label=SelectInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|SelectInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|SelectInput \|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=TokenMultipleInput		\|Label=TokenMultipleInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenMultipleInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenMultipleInput \|_text}}
Line 116:		Line 116:

	// form fields		// form fields
	-->{{~~Sidebar~~ item		-->{{Csp sidebar item
	\|Label=Title		\|Label=Title
	\|Value=<input type="text" name="Title" class="form-control" required="required" value="{{#af_get:{{{$pageData}}}\|csp-base-props\|Base properties\|1\|Title\|_text}}" />		\|Value=<input type="text" name="Title" class="form-control" required="required" value="{{#af_get:{{{$pageData}}}\|csp-base-props\|Base properties\|1\|Title\|_text}}" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=TextInput		\|Label=TextInput
	\|Value=<input type="text" name="TextInput" class="form-control" required="required" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextInput\|_text}}" />		\|Value=<input type="text" name="TextInput" class="form-control" required="required" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextInput\|_text}}" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=TokenInput		\|Label=TokenInput
	\|Value=<_token id="token-{{lc:{{anchorencode:TokenInput}} }}" name="TokenInput[]" class="form-control" allowclear selected="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenInput\|_text}}" options="Ay,Bee,Cee" />		\|Value=<_token id="token-{{lc:{{anchorencode:TokenInput}} }}" name="TokenInput[]" class="form-control" allowclear selected="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenInput\|_text}}" options="Ay,Bee,Cee" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=AskTokenInput		\|Label=AskTokenInput
	\|Value=<_token id="token-{{lc:{{anchorencode:AskTokenInput}} }}" name="AskTokenInput[]" class="form-control" required="required" multiple="multiple" input-length-trigger="1" query="[[Class::+]][[Title::!!!]](limit=999)(returntext=Title)" >		\|Value=<_token id="token-{{lc:{{anchorencode:AskTokenInput}} }}" name="AskTokenInput[]" class="form-control" required="required" multiple="multiple" input-length-trigger="1" query="[[Class::+]][[Title::!!!]](limit=999)(returntext=Title)" >
Line 137:		Line 137:
	\|Name=DateInput		\|Name=DateInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInput\|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInput\|_text}}
	}}{{~~Sidebar~~ item		}}{{Csp sidebar item
	\|Label=DateInputTwo		\|Label=DateInputTwo
	\|Value=<input type="datetime-local" name="DateInputTwo" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInputTwo\|_text}}" />		\|Value=<input type="datetime-local" name="DateInputTwo" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|DateInputTwo\|_text}}" />
	}}		}}
	<div class='alert alert-danger'>No template defined in parameter definitions</div>{{~~Sidebar~~ item		<div class='alert alert-danger'>No template defined in parameter definitions</div>{{Csp sidebar item
	\|Label=<label for="checkbox-{{lc:{{anchorencode:CheckboxInput}} }}" >CheckboxInput</label>		\|Label=<label for="checkbox-{{lc:{{anchorencode:CheckboxInput}} }}" >CheckboxInput</label>
	\|Value=<input type="hidden" name="CheckboxInput" value="" />		\|Value=<input type="hidden" name="CheckboxInput" value="" />
	<input type="checkbox" id="checkbox-{{lc:{{anchorencode:CheckboxInput}} }}" name="CheckboxInput" value="Yes" checked="{{#ifeq:{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|CheckboxInput\|_text}} \|Yes\|checked}}" />		<input type="checkbox" id="checkbox-{{lc:{{anchorencode:CheckboxInput}} }}" name="CheckboxInput" value="Yes" checked="{{#ifeq:{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|CheckboxInput\|_text}} \|Yes\|checked}}" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=TextAreaInput		\|Label=TextAreaInput
	\|Value=<input type="textarea" name="TextAreaInput" class="form-control" >{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextAreaInput\|_text}}</input>		\|Value=<input type="textarea" name="TextAreaInput" class="form-control" >{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TextAreaInput\|_text}}</input>
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=NumberInput		\|Label=NumberInput
	\|Value=<input type="number" name="NumberInput" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|NumberInput\|_text}}" />		\|Value=<input type="number" name="NumberInput" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|NumberInput\|_text}}" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=SelectInput		\|Label=SelectInput
	\|Value=<select name="SelectInput" class="form-control" allowclear selected="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|SelectInput\|_text}}" options="Alpha,Bravo,Charlie" />		\|Value=<select name="SelectInput" class="form-control" allowclear selected="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|SelectInput\|_text}}" options="Alpha,Bravo,Charlie" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=TokenMultipleInput		\|Label=TokenMultipleInput
	\|Value=<_token id="token-{{lc:{{anchorencode:TokenMultipleInput}} }}" name="TokenMultipleInput[]" class="form-control" multiple="multiple" selected="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenMultipleInput\|_text}}" options="Alpha,Bravo,Charlie" />		\|Value=<_token id="token-{{lc:{{anchorencode:TokenMultipleInput}} }}" name="TokenMultipleInput[]" class="form-control" multiple="multiple" selected="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenMultipleInput\|_text}}" options="Alpha,Bravo,Charlie" />
	}}		}}
	{{~~Sidebar~~ item		{{Csp sidebar item
	\|Label=TestNoDisplay		\|Label=TestNoDisplay
	\|Value=<input type="text" name="TestNoDisplay" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TestNoDisplay\|_text}}" />		\|Value=<input type="text" name="TestNoDisplay" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TestNoDisplay\|_text}}" />

Ebc16062-dd09-4928-8cf3-821f492b0c44 at 08:57, 5 October 2023

2023-10-05T08:57:34Z

Ebc16062-dd09-4928-8cf3-821f492b0c44 at 08:24, 5 October 2023

2023-10-05T08:24:19Z

← Older revision		Revision as of 10:24, 5 October 2023
Line 84:		Line 84:
	\|Label=TokenMultipleInput		\|Label=TokenMultipleInput
	\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenMultipleInput \|_text}}		\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TokenMultipleInput \|_text}}
	~~}}{{Sidebar item~~
	~~\|Label=Rob parameter~~
	~~\|Value={{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|Rob parameter \|_text}}~~
	}}<!--		}}<!--

Line 116:		Line 113:
	<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TokenMultipleInput" mwslot="csp-class-props" />		<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TokenMultipleInput" mwslot="csp-class-props" />
	<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TestNoDisplay" mwslot="csp-class-props" />		<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TestNoDisplay" mwslot="csp-class-props" />
	~~<_edit target="{{PAGEID}}" template="Csp class properties" formfield="Rob parameter" mwslot="csp-class-props" />~~
	<!-- end of _edits		<!-- end of _edits

Line 169:		Line 165:
	\|Label=TestNoDisplay		\|Label=TestNoDisplay
	\|Value=<input type="text" name="TestNoDisplay" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TestNoDisplay\|_text}}" />		\|Value=<input type="text" name="TestNoDisplay" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|TestNoDisplay\|_text}}" />
	}}
	~~{{Sidebar item~~
	~~\|Label=Rob parameter~~
	~~\|Value=<input type="number" name="Rob parameter" class="form-control" value="{{#af_get:{{{$pageData}}}\|csp-class-props\|Csp class properties\|1\|Rob parameter\|_text}}" />~~
	}}		}}
	<!--		<!--

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295: /* Fully custom sidebar template */

2023-09-29T08:54:48Z

Fully custom sidebar template

← Older revision		Revision as of 10:54, 29 September 2023
Line 38:		Line 38:
	In a fully custom sidebar template you can do anything you want. You will still get the $pageData and $classData parameters passed to this template so you can use those. The following is an example of custom sidebar code that will produce a sidebar similar to the default one, perhaps this will give you some ideas for what's possible:		In a fully custom sidebar template you can do anything you want. You will still get the $pageData and $classData parameters passed to this template so you can use those. The following is an example of custom sidebar code that will produce a sidebar similar to the default one, perhaps this will give you some ideas for what's possible:

	<syntaxhighlight lang="~~wikitext~~">		<syntaxhighlight lang="html">
	<div class="tab-content"><!--		<div class="tab-content"><!--
	--><input type="radio" id="sidebar-view" name="toggle-sidebar" checked="checked" class="d-none sidebar-view" /><!--		--><input type="radio" id="sidebar-view" name="toggle-sidebar" checked="checked" class="d-none sidebar-view" /><!--

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295 at 08:54, 29 September 2023

2023-09-29T08:54:24Z

← Older revision		Revision as of 10:54, 29 September 2023
Line 38:		Line 38:
	In a fully custom sidebar template you can do anything you want. You will still get the $pageData and $classData parameters passed to this template so you can use those. The following is an example of custom sidebar code that will produce a sidebar similar to the default one, perhaps this will give you some ideas for what's possible:		In a fully custom sidebar template you can do anything you want. You will still get the $pageData and $classData parameters passed to this template so you can use those. The following is an example of custom sidebar code that will produce a sidebar similar to the default one, perhaps this will give you some ideas for what's possible:

	<~~pre~~>		<syntaxhighlight lang="wikitext">
	<div class="tab-content"><!--		<div class="tab-content"><!--
	--><input type="radio" id="sidebar-view" name="toggle-sidebar" checked="checked" class="d-none sidebar-view" /><!--		--><input type="radio" id="sidebar-view" name="toggle-sidebar" checked="checked" class="d-none sidebar-view" /><!--
Line 185:		Line 185:
	\|}}<!-- end of #ifeq @allow sidebar edit == yes -->		\|}}<!-- end of #ifeq @allow sidebar edit == yes -->
	</div>		</div>
	</~~pre~~>		</syntaxhighlight>

← Older revision		Revision as of 10:57, 5 October 2023
Line 1:		Line 1:
	In '''Open CSP 2.0''' the default sidebar was added, this allows you to have sidebars without having to create custom sidebar templates for each class definition. There are some customization options built into the default sidebar as well. It is recommended to use these customization options when possible and to only create fully custom sidebar templates when absolutely necessary, as the fully custom sidebar templates require a lot more maintenance work when for example some parserfunctions get deprecated. This document describes the various customization options.		In '''Open CSP 2.0''' the default sidebar was added, this allows you to have sidebars without having to create custom sidebar templates for each class definition. There are some customization options built into the default sidebar as well. It is recommended to use these customization options when possible and to only create fully custom sidebar templates when absolutely necessary, as the fully custom sidebar templates require a lot more maintenance work when for example some parserfunctions get deprecated or changed. This document describes the various customization options.

	== Parameters and formfield/display templates ==		== Parameters and formfield/display templates ==
Line 5:		Line 5:
	* Note that the parameter configuration is also used for setting properties, but you can use "(none)" as property name value if you don't want to set a property.		* Note that the parameter configuration is also used for setting properties, but you can use "(none)" as property name value if you don't want to set a property.
	* Only the "parameter name" field is required. When you only fill this, you will get default text fields in the sidebars.		* Only the "parameter name" field is required. When you only fill this, you will get default text fields in the sidebars.
	* Choose a displayTemplate to configure how a parameter is ~~diaplayed~~ in the view tab of the default sidebar.		* Choose a displayTemplate to configure how a parameter is displayed in the view tab of the default sidebar.
	* Choose a formfieldTemplate to ~~coinfigure~~ what type of form field is used in the edit tab of the default sidebar.		* Choose a formfieldTemplate to configure what type of form field is used in the edit tab of the default sidebar.
	* DisplayTemplate and formfieldTemplate can both be set to "(none)" to not have a parameter show up in respectively the view and edit tabs of the default sidebar.		* DisplayTemplate and formfieldTemplate can both be set to "(none)" to not have a parameter show up in respectively the view and edit tabs of the default sidebar.

Line 13:		Line 13:
	* All fields that are filled for a parameter will be passed to the templates so they can be accessed through template parameters there. For example you can use <nowiki>{{{allowedValues\|}}}</nowiki> in a formfieldTemplate. It might be useful to look at the csp-data slot of the class definition to see all of the parameters.		* All fields that are filled for a parameter will be passed to the templates so they can be accessed through template parameters there. For example you can use <nowiki>{{{allowedValues\|}}}</nowiki> in a formfieldTemplate. It might be useful to look at the csp-data slot of the class definition to see all of the parameters.
	* The values of parameters on a content page are also passed to the display/formfield templates as the "value" parameter.		* The values of parameters on a content page are also passed to the display/formfield templates as the "value" parameter.
	* In a display/formfield ~~templates~~ you cannot access values of other parameters directly, but you can do this by using <nowiki>{{#invoke:CspFunctions\|getParentArgs\|$pageData}}</nowiki>, which will return the $pageData parameter that is used in '''Template:Csp default sidebar''' (and contains an ArrayFunctions export with slotdata of the page).		* In a display/formfield template you cannot access values of other parameters directly, but you can do this by using <nowiki>{{#invoke:CspFunctions\|getParentArgs\|$pageData}}</nowiki>, which will return the $pageData parameter that is used in '''Template:Csp default sidebar''' (and contains an [[mediawikiwiki:Extension:ArrayFunctions\|ArrayFunctions]] export with slotdata of the page).
	* It is possible to add fields to the json data in the csp-data slot that cannot be filled through the parameters form. For example CSP ~~1.8~~.0 does not yet include the option to specify a placeholder for your formfields, but you can add placeholder to the json data and then use <nowiki>{{{placeholder\|}}}</nowiki> in a custom formfieldTemplate.		* It is possible to add fields to the json data in the csp-data slot that cannot be filled through the parameters form. For example Open CSP 2.0 does not yet include the option to specify a placeholder for your formfields, but you can add placeholder to the json data and then use <nowiki>{{{placeholder\|}}}</nowiki> in a custom formfieldTemplate.

	== Custom sidebar template where you are adding to the default sidebar ==		== Custom sidebar template where you are adding to the default sidebar ==