CSP Wiki - User contributions [en]

Open CSP Steering committee

2025-09-23T13:55:50Z

81d56153-9868-4094-90a0-df1700ff7090:

== Agenda of the steering committee meetings ==

* Welcome and Recap
* Project Status and Updates
* Technical Roadmap
* Marketing activities
* Risk Management
* Open Discussion
* Action Items and Next Meeting
== Members ==
{| class="wikitable"
|+
!Name
!Role/focus
!Organization
{{Steering committee member
|Name=Ad Strack van Schijndel
|Role=Chairperson
|Organization=Juggel
}}{{Steering committee member
|Name=Charlot Cobben
|Role=Maintainer
|Organization=Wikibase Solutions
}}{{Steering committee member
|Name=Marijn van Wezel
|Role=Maintainer
|Organization=Independent
}}{{Steering committee member
|Name=Cindy Cicalese
|Role=Linking pin MediaWiki
|Organization=Wikimedia Foundation
}}{{Steering committee member
|Name=Jeffrey Wang
|Role=Linking pin Canasta
|Organization=MyWikis
}}{{Steering committee member
|Name=Rich Evans
|Role=Ambassador
|Organization=NASA GRC
}}{{Steering committee member
|Name=Bryan Hildebrand
|Role=Ambassador
|Organization=Tegnosis Knowledge Management
}}{{Steering committee member
|Name=Viktor Schelling
|Role=tba
|Organization=Independent
}}
|}
== Meetings ==
<div class="container"><div class="row"><div class="col"><div class="timeline-steps aos-init aos-animate" data-aos="fade-up">{{#invoke:Timeline|show}}</div></div></div></div>
{{#ifingroup:user|
{{#ask: [[Class::Meeting report]]
|?Date
|?Attendees
|format=table
}}}}

{{#ifingroup:user|
=== Create new meeting report ===
{{Create meeting form
|Meeting type=Steering committee
}}}}
{{#ifingroup:moderator,sysop |

=== Edit Agenda meetings ===

<form>
<_edit target="{{PAGEID:{{FULLPAGENAME}}}}" format="json" template="jsonk|milestones" formfield="timeline-instance" mwslot="ws-data" />
<_instance name="timeline-instance" format="json" default-content="{{#slotdata:ws-data|{{FULLPAGENAME}} |milestones}}">
<div>
<div class="timeline-edit"><label for="date">Date</label><input type="date" name="date" placeholder="date" /></div>
<div class="timeline-edit"><label for="title">Title</label><input type="text" name="title" placeholder="title" /></div>
<div class="timeline-edit"><label for="link">Link</label><input type="text" name="link" placeholder="url" /></div>
</div>
</_instance>
<input type="submit" value="save" />
</form>

}}

Open CSP Steering committee

2025-09-23T13:54:37Z

81d56153-9868-4094-90a0-df1700ff7090:

== Agenda of the steering committee meetings ==

* Welcome and Recap
* Project Status and Updates
* Technical Roadmap
* Marketing activities
* Risk Management
* Open Discussion
* Action Items and Next Meeting
== Members ==
{| class="wikitable"
|+
!Name
!Role/focus
!Organization
{{Steering committee member
|Name=Ad Strack van Schijndel
|Role=Chairperson
|Organization=Juggel
}}{{Steering committee member
|Name=Charlot Cobben
|Role=Maintainer
|Organization=Wikibase Solutions
}}{{Steering committee member
|Name=Marijn van Wezel
|Role=Maintainer
|Organization=Independent
}}{{Steering committee member
|Name=Cindy Cicalese
|Role=Linking pin MediaWiki
|Organization=Wikimedia Foundation
}}{{Steering committee member
|Name=Jeffrey Wang
|Role=Linking pin Canasta
|Organization=MyWikis
}}{{Steering committee member
|Name=Rich Evans
|Role=Ambassador
|Organization=NASA GRC
}}{{Steering committee member
|Name=Bryan Hildebrand
|Role=Ambassador
|Organization=Tegnosis Knowledge Management
}}{{Steering committee member
|Name=Viktor Schelling
|Role=tba
|Organization=Independent
}}
|}
== Meetings ==
<div class="container"><div class="row"><div class="col"><div class="timeline-steps aos-init aos-animate" data-aos="fade-up">{{#invoke:Timeline|show}}</div></div></div></div>
{{#ifingroup:user|
{{#ask: [[Class::Meeting report]]
|?Date
|?Attendees
|format=table
}}}}

{{#ifingroup:user|
=== Create new meeting report ===
{{Create meeting form
|Meeting type=Steering committee
}}}}

{{#ifingroup:moderator,sysop |

=== Edit Agenda meetings ===

<form>
<_edit target="{{PAGEID:{{FULLPAGENAME}}}}" format="json" template="jsonk|milestones" formfield="timeline-instance" mwslot="ws-data" />
<_instance name="timeline-instance" format="json" default-content="{{#slotdata:ws-data|{{FULLPAGENAME}} |milestones}}">
<div>
<div class="timeline-edit"><label for="date">Date</label><input type="date" name="date" placeholder="date" /></div>
<div class="timeline-edit"><label for="title">Title</label><input type="text" name="title" placeholder="title" /></div>
<div class="timeline-edit"><label for="link">Link</label><input type="text" name="link" placeholder="url" /></div>
</div>
</_instance>
<input type="submit" value="save" />
</form>

}}

Template:Sidebar item

2025-09-23T13:28:52Z

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

<noinclude>
This is the "Sidebar item" template. It should be called in the following format:

<pre>
{{Sidebar item
|Label= (text)
|Value= (text)
}}
</pre>

== Test ==
{{Sidebar item
|Label=Test label
|Value=Test value
}}

</noinclude><includeonly><div class="sidebar-item">{{#if:{{{Label|}}}|<div class="sidebar-item-label">{{{Label|}}}</div>}}{{#if:{{{Value|}}}|<div class="sidebar-item-value">{{{Value|}}}</div>}}</div></includeonly>

Template:Slots OpenCSP

2025-09-23T13:28:49Z

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

<noinclude>
<pre>
{{Slots}}
</pre>

uses url parameters:
* page (contains the pagename for which slots should be shown)

</noinclude><includeonly>{{#af_foreach:{{#af_list:{{#af_object:page={{#urldecode:{{#urlget:page}} }} }} }}||$var|{{#if:{{#af_get:{{{$var}}}|page}} |Slots of {{#ifeq:{{NAMESPACENUMBER:{{#af_get:{{{$var}}}|page}} }}|6
|[[:{{#af_get:{{{$var}}}|page}}]]
|[[{{#af_get:{{{$var}}}|page}}]]
}}

ws-base-props
{{#tag:pre |{{#slot:ws-base-props |{{#af_get:{{{$var}}}|page}} }} }}

<_form action="addToWiki" mwreturn="{{fullurl:{{FULLPAGENAME}}|page={{urlencode:{{#af_get:{{{$var}}}|page}} }} }}" >
<_create mwwrite="{{#af_get:{{{$var}}}|page}}" mwtemplate="wsnone" mwslot="ws-base-props" formfield="Content" />

<_input type="textarea" rows="10" name="Content">{{#invoke:CspFunctions|getSlotContent|page={{#af_get:{{{$var}}}|page}}|slot=ws-base-props|nowiki}}</_input>

<_input type="submit" value="Save" />
</_form>

ws-class-props
{{#tag:pre |{{#slot:ws-class-props |{{#af_get:{{{$var}}}|page}} }} }}

<_form action="addToWiki" mwreturn="{{fullurl:{{FULLPAGENAME}}|page={{urlencode:{{#af_get:{{{$var}}}|page}} }} }}" >
<_create mwwrite="{{#af_get:{{{$var}}}|page}}" mwtemplate="wsnone" mwslot="ws-class-props" formfield="Content" />

<_input type="textarea" rows="10" name="Content">{{#invoke:CspFunctions|getSlotContent|page={{#af_get:{{{$var}}}|page}}|slot=ws-class-props|nowiki}}</_input>

<_input type="submit" value="Save" />
</_form>

ws-seo
{{#tag:pre |{{#slot:ws-seo |{{#af_get:{{{$var}}}|page}} }} }}

<_form action="addToWiki" mwreturn="{{fullurl:{{FULLPAGENAME}}|page={{urlencode:{{#af_get:{{{$var}}}|page}} }} }}" >
<_create mwwrite="{{#af_get:{{{$var}}}|page}}" mwtemplate="wsnone" mwslot="ws-seo" formfield="Content" />

<_input type="textarea" rows="10" name="Content">{{#invoke:CspFunctions|getSlotContent|page={{#af_get:{{{$var}}}|page}}|slot=ws-seo|nowiki}}</_input>

<_input type="submit" value="Save" />
</_form>

ws-data
{{#tag:pre |{{#slot:ws-data |{{#af_get:{{{$var}}}|page}} }} }}

<_form action="addToWiki" mwreturn="{{fullurl:{{FULLPAGENAME}}|page={{urlencode:{{#af_get:{{{$var}}}|page}} }} }}" >
<_create mwwrite="{{#af_get:{{{$var}}}|page}}" mwtemplate="wsnone" mwslot="ws-data" formfield="Content" />

<_input type="textarea" rows="10" name="Content">{{#invoke:CspFunctions|getSlotContent|page={{#af_get:{{{$var}}}|page}}|slot=ws-data|nowiki}}</_input>

<_input type="submit" value="Save" />
</_form>
|Please pass a url parameter 'page' to this page to display the slots for that page.

eg. <code>/Wiki:Slots?page=Main Page</code>}}}}</includeonly>

Template:Dropdown link

2025-09-23T13:27:04Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

<noinclude>
<pre>{{Dropdown link
|Page=
|Text=
}}
</pre>

OR

<pre>{{Dropdown link
|Href=
|Text=
}}
</pre>

;Alternative
<pre><li>{{#widget:Link|type=a|href={{#ifeq:{{FULLPAGENAME}}|{{{Page|}}}|#|{{fullurl:{{{Page|}}}}}}}|text={{{Text|}}}}}</li></pre>

</noinclude><includeonly><li class="{{#ifeq:{{NAMESPACE}}|Special|{{{Page|}}}|{{#ifeq:{{FULLPAGENAME}}|{{{Page|}}}|navbar-text navbar-presentpage|}}}}">{{#if:{{{Page|}}} | {{#Widget:Link|type=a|href={{fullurl:{{{Page|}}} }}|text={{{Text|}}}|class=dropdown-item }} }}{{#if:{{{Href|}}} | {{#widget:Link|type=a|href={{{Href|}}}|text={{{Text|}}}|class=dropdown-item }} }}</li></includeonly>

User:Ad Strack van Schijndel/Test slot bestaande pagina

2025-09-18T11:41:47Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

Template:SEO

2025-09-18T11:38:54Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

<noinclude>

This is the '''SEO''' template. It should be called in the following format:

{{Alert|Type=danger|Please use the CMS sidebar to fill in the seo settings instead of trying to do it manually}}

static properties:
* locale = en_US
* site name = OpenCSP
* Title always gets 'OpenCSP - ' prefix
* robots & googlebot are set to 'index, follow'

<pre>
{{SEO
|Title= (text)
|Title mode= (optional: replace/append/prepend)
|Title separator= (text)
|Keywords= (text)
|Description= (text)

|Robots = (text)
|Googlebot= (text)

|Type= (text)
|Image= (text)
|Image alt= (text)
|Image width= (number)
|Image height= (number)
|Locale= (text)
|Site name= (text)

|Author= (text)
|Section= {text)
|Published time= (date)
}}
</pre>

</noinclude><includeonly>{{#seo:
|title={{#if: {{{Title|}}} |{{{Title|}}} |{{PAGENAME}} }}
|title_mode={{#if:{{{Title mode|}}} |{{{Title mode|}}} |replace}}
|title_separator={{#if: {{{Title separator|}}} |{{{Title separator|}}} |- }}
|keywords={{{Keywords|}}}
|description={{{Description|}}}

|robots={{#if: {{{Robots|}}} |{{{Robots|}}} |index, follow}}
|googlebot={{#if: {{{Googlebot|}}} |{{{Googlebot|}}} |index, follow}}

|type={{{Type|}}}
|image={{{Image|}}}
|image_alt={{{Image alt|}}}
|image_width={{{Image width|}}}
|image_height={{{Image height|}}}
|locale={{#if: {{{Locale|}}} |{{{Locale|}}} |en_US}}
|site_name={{#if: {{{Site name|}}} |{{{Site name|}}} |OpenCSP}}

|author={{{Author|}}}
|section={{{Section|}}}
|published_time={{{Published time|}}}
}}</includeonly>

Wiki:Setting/qanda-tags

2025-09-18T11:38:08Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

Installation,Compatibility,Community,Enterprise,Feature,Flexibility,Security,Confluence,Content Services Platform

Search-documentation

2025-09-18T11:37:45Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

===Search documentation===
__NOTOC__{{#WikiSearchConfig:
|default operator=and
|base query=[[Class::Doc]]
|aggregation size=50
|Title
|Doc subject
|Doc synopsis
|Doc parent
|Subject version
|Doc target group
|Tag
|?Doc subject
|?Doc target group
|?Doc parent
|?Doc synopsis
|?Subject version
}}
<div class="main-search">
{{#WikiSearchFrontend:size=10
|facets=4
|sort=Modification date
|sort options=Modification date
|ordertype=Modification date
|order=desc
|title=_DTITLE
|layout=template
|template=Show_docs_search_result
|@Doc subject
|@Subject version
|@Doc target group
#label=Target group
|@Tag
#display=pill
|?Doc subject
|?Doc synopsis
|?Subject version
|?Doc target group
|?Doc parent
|?Title
|?$title
|?$snippet
|?$namespacename
|?$page
|?$Modification date#display=date#label=Updated#type=date}}
</div>

Questions-and-answers

2025-09-18T11:37:24Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

__NOTOC__
<div class="main-search">{{#WikiSearchConfig:
|base query=[[Class::QandA]]
|aggregation size=100
|Tag
|?Tag
}}
<div class="control-search soa-search">
{{#WikiSearchFrontend:
|size=100
|title=_DTITLE
|?$title
#display=link
|?Tag
#display=pill
|@Tag
}}
</div>

Article/about-open-csp

2025-09-18T11:36:59Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

With Open CSP organizations can create a MediaWiki based Information and Productivity platform for their employees, partners, members and customers.

Open CSP is:

* a vision on open source MediaWiki based Information and Productivity platforms
* an open source software and content bundle for MediaWiki
* an integrated solution for Information and Productivity platforms

== The Open CSP vision ==

== The open source software and content ==

== The integrated solution ==
Open CSP provides an integrated solution of high quality. The Open CSP have been carefully selected and developed to work together and create a high quality, flexible framework.

Open CSP provides out-of-the-box features that give you a flying start. On top of that, there is a growing number of Open CSP compatible modules. Its flexibility and productivity for custom solutions enables you to create a platform that seamlessly supports your knowledge and operational processes.

Wikibase Solutions is experienced in developing, delivering and hosting advanced solutions based on Open CSP. Our solutions provide the features you want, and just as important: we develop and delivery it your way.

Some things that our enterprise customers find important:

* '''Scrum development approach with two-week sprints'''
* '''Development, Testing and QA before deploying to production'''
* '''Integration with IAM solutions such as Microsoft AD or Okta'''
* '''ISO 27001 compliant internal processes'''

There is no doubt that the MediaWiki platform is awesome and provides many features that are of great benefit for large organizations. The result is a platform that is reliable, secure, flexible and scalable - and it is open source.

Open CSP adds some important building blocks to MediaWiki.

* '''Semantic MediaWiki''' with '''Elasticsearch''' adds scalable database features. It turns the platform into a flexible database system
* '''Faceted search''', enabled by Elasticsearch. State of the art, out-of-the-box search features
* Powerful and flexible '''forms'''
* Organize content in '''spaces'''
* Authentication via '''Azure Active Directory'''
* '''Exchange of content''' between platforms
* Integration with an open source '''Neo4J graph database'''
* Enterprise ready '''permissions framework''' (under construction)

=== Open CSP workspace ===
A workspace based on Open CSP guarantees optimal integration of content, records and documents.

Its flexibility enables user feedback leading to meaningful changes in a short time. This increases the support base of the platform. The result is a positive vicious circle of improved use and further development.

Step by step the Open CSP workspace supports more and more daily processes of your teams and co-workers.

Wikibase Solutions is constantly innovating and improving the Open CSP framework. Currently the focus is on integration of MediaWiki with Neo4J. Neo4J is a state of the art open source graph database. Neo4J can in the future be used next to, or as a replacement of, Semantic MediaWiki. There are two big opportunities when using Neo4J:

* '''Graph database implementation''' Since Neo4J is a graph database the integration with Neo4J is more natural and less complex. This is a good basis for further enhancements.

* '''Wiki as an interface''' Currently Semantic MediaWiki has the same scope as the wiki. Data in the wiki is stored as properties, hence there is no integrated world outside the wiki. With Neo4J, in addition to the wiki-data being stored in Neo4J, the wiki can act as a UI to Neo4J. This enables the wiki to be part of an advanced knowledge graph.

Wikibase Solutions is in the process of implementing integration scenarios. Please contact us if you are interested in the subject.

DevOps:Page/5

2025-09-18T11:25:55Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

Please read the [[DevOps:Policy/4|Documentation policy]] before you start creating documentation. Documentation pages are meant to be used exclusively for what is described in the policy.
__NOTOC__{{#WikiSearchConfig:
|base query=[[Class::Doc]]
|aggregation size=50
|Title
|Doc subject
|Subject version
|Doc target group
|Tag
}}
<div class="main-search">
{{#WikiSearchFrontend:size=10
|facets=4
|title=_DTITLE
|clear=term
|@Modification date
#display=date
#label=Updated
#type=date
|@Doc subject
|@Subject version
|@Doc target group
#label=Target group
|@Tag
#display=pill
|?Doc subject
|?Subject version
|?Tag
}}
</div>

DevOps:Page/4

2025-09-18T11:22:38Z

81d56153-9868-4094-90a0-df1700ff7090: User:81d56153-9868-4094-90a0-df1700ff7090

{{Create doc page form
|Class options=Doc
|Subject={{#urldecode: {{#urlget: subject}} }}
|Preload page={{#urldecode: {{#urlget: page}} }}
|Version={{#urldecode: {{#urlget: version}} }}
}}

QandA/does-open-csp-have-an-api

2025-07-15T09:07:22Z

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

== MediaWiki has an API ==

== Open CSP features provide APIs ==

QandA/can-open-csp-be-used-with-page-forms

2025-07-15T09:07:22Z

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

This question has two answers, depending on why you ask this question.

==Yes, technically it can==
It is perfectly ok to install Page Forms in an Open CSP wiki and use it in the way you are used to. There may be valid reasons to do this and you won't be obstructed in doing that.

==You cannot take advantage of important Open CSP features==
Due to limitations in Page Forms you will not be able to use Page Forms in an Open CSP wiki in the way that is intended with Open CSP.

===Page Forms doesn't support multiple slots===
Page Forms acts on the main slot of a page, the slot that you can edit with 'edit source'. However, with Page Forms you typically edit the structured data of a page, metadata or properties and in an Open CSP this structured dat is stored in a different slot than the 'main' slot. Page forms doesn't allow to choose the slot to write to or read from.

QandA/is-open-csp-scalable

2025-07-15T09:07:21Z

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

== Yes, Open CSP is scalable ==
Open CSP is scalable because it builds in an efficient way on MediaWiki and Elasticsearch.

== MediaWiki is scalable ==
MediaWiki has been designed with scalability in mind for high-usage, high-profile sites.

== Elasticsearch is scalable ==
Elasticsearch is built to be always available and to scale with your needs. It does this by being distributed by nature. You can add servers (nodes) to a cluster to increase capacity and Elasticsearch automatically distributes your data and query load across all of the available nodes.

QandA/can-open-csp-be-used-with-cargo

2025-07-15T09:07:21Z

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

This question has two answers, depending on why you ask this question.

== Yes, technically it can ==
It is perfectly ok to install Cargo in an Open CSP wiki and use it in the way you are used to. There may be valid reasons to do this and you won't be obstructed in doing that.

== You cannot take advantage of important Open CSP features ==
Due to limitations in Cargo you will not be able to use Cargo in an Open CSP wiki in the way that is intended with Open CSP.

=== Cargo doesn't support multiple slots ===
Cargo parser functions only work in the main slot. That is the standard way of working with Cargo. But if you put the wikitext that stores or queries data from Cargo tables in other slots than the main slot, Cargo doesn't process them.

=== Cargo doesn't use Elasticsearch ===
Cargo stores data in the Cargo tables and does the querying on those tables. On of the benefits of Open CSP is that the data is also stored in Elasticsearch so that the [[Mediawikiwiki:Extension:WikiSearch|WikiSearch extension]] can be used.

[https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki] is included in Open CSP and the Elasticstore option is used. This way anything that is stored on a page is available for search automatically.

QandA/where-does-name-open-csp-come-from

2025-07-15T09:07:20Z

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

== Ambition to be in a Magic Quadrant ==
When you start to think about a platform like we did, you have to define some dots on the horizon.

One of those dots was to once be mentioned - preferebly in the top right corner - of one of Gartner's magic quadrants. The question that arises is which quadrant that then should be.

== Gartner's definition of Content Services Platform matched with our ideas ==
The Content Services Platform Gartner envisions seems to match our ideas.

== An open source Content Services Platform ==
The name Open CSP has been assembled from what we believe it should be: an open source Content Services Platform.

QandA/is-open-csp-suitable-for-large-companies

2025-07-15T09:07:20Z

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

QandA/how-can-i-install-open-csp

2025-07-15T09:07:20Z

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

Installation of Open CSP is quite easy. Have a look at the documentation of Open CSP and start with [[DevOps:Doc/Open CSP/1.0/Requirements|the requirements]].

QandA/what-are-the-key-features-of-open-csp

2025-07-15T09:07:19Z

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

== Classify and organize content ==
You get the tools you need to classify and organize all the content that is important for your company.

== Manage and author content ==
High quality content requires perfect support for those who are responsible for their part of the content. Open CSP provides the building blocks to realize this.

== Search ==
Open CSP search capabilities are state of the art.

== Add functionality ==
Open CSP is an excellent basis for adding functionality to your enterprise platform.

== Extensibility ==
Open CSP extensibility ensures a Content Services Platform that fits perfectly the needs of your organization.

== No license fees ==
Open CSP has no license fees.

QandA/what-is-role-of-wikibase-solutions-with-the-open-csp

2025-07-15T09:07:19Z

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

== Wikibase Solutions has been leading the initiative ==
On the [https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2020 Semantic MediaWiki conference in 2020] Ad Strack van Schijndel did a presentation on the subject. That can be regarded as the start of the initiative.

Since then [https://www.wikibase-solutions.com/ Wikibase Solutions] has been promoting the Open CSP and developing extensions.

== Wikibase Solutions is maintainer of the software ==
Open CSP is open source software that anybody can contribute to. The role of Wikibase Solutions is the maintainer of the software. This means that they review proposed changes, communicate about it and merge them in the software. The maintainer is responsible for the quality of the software.

== Wikibase Solutions provides services for your Content Services Platform ==
Wikibase Solutions provides services that enable you to realize the full potential of a Content Services Platform in your organization.

QandA/why-is-working-with-slots-so-important

2025-07-15T09:07:19Z

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

== Structured data can be managed separately ==
A major feature of MediaWiki is the [[mediawikiwiki:Multi-Content_Revisions|Multi Content Revisions (MCR)]] feature. MCR provides a way to store content in multiple slots on a page. This means that structured data can be managed separately.

== The benefits of separating structured data from user content ==
The ability to manage structured data separate from the free content of the page has many advantages for developers and users.

* For developers the wiki is easier to develop and maintain
* For users the wiki offers better features and is more standardized
* For the owner of the wiki it means a better Information and Productivity platform at lower cost.

QandA/is-open-csp-a-good-alternative-for-confluence

2025-07-15T09:07:19Z

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

== An Open CSP wiki can be an excellent alternative for Confluence ==
With Open CSP your lay the foundation for what can be the perfect collaboration and knowledge platform for your company.

== An Open CSP wiki is clearer and more intuitive ==
Less can be more, also for a collaboration and knowledge platform. Clarity is important for good use of the platform.

== An Open CSP wiki is better manageable than Confluence ==
With the tools an Open CSP wiki offers it is easier to keep the platform clear and intuitive. Managing and maintaining the platform is important and must be made easy.

== Search capabilities are excellent ==
Baked in Open CSP you get search capabilities that are extremely flexible and powerful. Very different from the search capabilities Confluence has to offer.

== Flexibility and extensibility are limitless ==
Open CSP provides incredible capabilities for moulding the platform to your needs and ambitions. This will not make your platform less clear and intuitive. On the contrary, these capabilities enable you to integrate the platform in your business and other systems and increase clarity and intuitiveness.

QandA/what-is-a-content-services-platform

2025-07-15T09:07:19Z

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

== Definition according to Gartner ==
[https://www.gartner.com/en/information-technology/glossary/content-services-platform-csp According to Gartner] a Content Services Platform (CSP) is ''a set of services and microservices, embodied as an integrated product suite and applications that share common APIs and repositories. A CSP exploits diverse content types and serves multiple constituencies and numerous use cases across an organization.''

== A CSP is an integrated set of services and microservices ==
Two things are important:

* the platform must have the flexibility to easily add new services
* it must be easy to integrate the new services with existing ones

== A CSP exploits diverse content types ==
In an organization many content types are used to store, share and process information. We think that a CSP should be able to deal with documents, XML, JSON, SQL databases and graph databases.

== A CSP serves multiple constituencies ==
For larger organizations it is important that a CSP can separate between groups of people. Not only for security purposes, but also to provide people with the context in the CSP that they belong to and that they understand.

== A CSP serves numerous use cases ==
Two things are important here:

* The CSP provides strong services and features
* The CSP can be easily adapted and enhanced to perfectly match the processes and needs of the organizaton

Professional-services-for-open-csp

2025-07-15T09:06:29Z

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

==Professional services for Open CSP==

Here's a list of companies that can provide professional services dealing with Open CSP
<hr>
===Wikibase Solutions===
https://wikibase-solutions.com

Wikibase Solutions is the leading business solutions provider on the Open CSP platform. Streamlining information and sharing knowledge, we empower ambitious organizations with wikis, such as open source wikis, company wiki software and business wikis.

'''Contact information'''

T: +1 (949) 409 65 36 or +31 (0) 162 229 686

E: info@wikibase-solutions.com

Socials :
* Facebook : https://www.facebook.com/wikibasesolutions/
* Twitter : https://twitter.com/wikibasenl
* LinkedIn : https://www.linkedin.com/company/wikibase-solutions/
<hr>

MR Steering committee 2024-11-21

2025-07-15T09:04:38Z

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

=== Agenda ===

* MudCon reCap
* Open CSP
* WikiApiairy
* Open CSP on Canasta

=== Discussed ===

* Knowledge bases are still a very hot topic as seen from the conference. Open CSP can play a major role here. Also Rich (via Element) announced the use of Open CSP as of next year. Great news!
* We all agreed MudCon was very well organized
* WikiApiAiry: Cindy will be busy the coming weeks, but will try to get WikiApiary on Open CSP on Canasta once Lars updates the image repo.
* When Lars has updated the image repo: We will send the instructions in element for Cindy and Bryan to test. Charlot will create a how-to video with a short introduction to get started with Open CSP.

MR Steering committee 2024-10-17

2025-07-15T09:04:37Z

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

===Agenda===

*Status Canasta and open CSP
*Demo Open CSP on Canasta by Lars
*MediaWiki User and Developer Conference

===Discussed===

*Demo Open-CSP 2.0 running on Canasta-DockerCompose.
*Open CSP talks and other talks for MediaWiki User and Developer Conference
*WikiApiary future

===off topic===
[[File:Amiga Guru Meditation.gif|frameless]]

MR Steering committee 2024-09-05

2025-07-15T09:04:37Z

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

===Agenda===

*Status Canasta and open CSP

===Discussed===

*Open-CSP 2.0 now running and functioning properly on Canasta-DockerCompose.
*Latest changes to the web container in order to make this work not yet incorporated into a Dockerfile for an override image
*Therefore PoC, but not quite ready for publishing to the community
*All modifications to make it work on Canasta are now known and logged
*Few more hours needed to amend the previous custom image

MR Steering committee 2024-06-13

2025-07-15T09:04:37Z

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

MR Steering committee 2023-09-13

2025-07-15T09:04:37Z

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

=== Notes ===
Ad had to leave after 5 mins due to a birthday

Cindy and Jeffrey left after 30 mins due to other meetings

=== Agenda ===

# Status Open CSP 2.0
## Status Documentation
## Status internal rewrite and changes to beta version
## Status install script
## Status web installer
## Status compatibility check current MediaWiki installment and consequences
# What others can contribute
# Planning for October release

=== Discussed ===
(1.2) Liselot started off by telling us the new and improved user experience features; mw 1.39 compatible; and compatibility with future Parsoid releases. In theory people can upgrade from Open CSP beta to Open CSP 2.0, but it is not supported by default.

(1.1) Charlot talked more about documentation and also Liselot will be adding more technical documentation the coming two weeks. Ad might be able to contribute to this as well

(1.3) Wout, from Wikibase Solutions, is currently writing the install script

(1.4, 1.5) An extension WSImageVersion is to be forked and renamed to OpenCSP. It will hold the current Open CSP version, a special page with compatibility check and a special page to run the install as an admin from a Special Page instead of a terminal.

(2, 3) Charlot will have a look at creating a promotional video and a more technical or demonstration of use video. These can be used for socials and for Cindy to talk the importance of splitting content from meta data and other subjects. SMWCon is mentioned.

(2) Bryan will, once Open CSP 2 is released, contribute to the documentation and his findings.

(2) Bryan wants to use ArrayFunctions and suggested some sort of Sandbox. Action for Marijn.

MR Steering committee 2024-05-30

2025-07-15T09:04:36Z

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

=== Agenda ===

* status canasta and open CSP

* Knowledge Base marketing

* Open CSP website
* planning

=== Discussed ===

* Open CSP and Canasta. Since both Jeffrey and Cindy were not in this meeting, Charlot will contact them in a separate meeting.
* Open CSP as a Knowledge base It is a huge benefit that Open CSP is a full blown Knowledge base right out-of-the-box and we should discuss means of promoting this. Attendees agreed, but also mentioned other items that have not been well promoted. Rich prompted that it is great Open CSP is open source, but this also comes with the fact that administrators usually have more work maintaining and upgrading extensions etc. Overall Open CSP lowers the cost-of-ownership, which is a huge benefit. As a result, Lars will right-up the pro's in regards to maintaining an Open CSP based website. ( Red: [[DevOps:Doc/Open CSP/2.0/Maintenance|https://www.open-csp.org/DevOps:Doc/Open_CSP/2.0/Maintenance]] )
* Viktor offered some inside on work at his company in regards to expanding the WikiSearch extension to be able to show results from not only Elastic Search, but other sources as well. This could be potentially very interesting as WikiSearch is part of Open CSP.
* Ad, not having much experience with actual setting up servers and actually being able to run Open CSP 2.0, had a one-on-one with Bryan to setup a VM with Open CSP 2 to play around with it and have a look at the differences compared to the first release of Open CSP
* Ad and Bryan also suggested a sandbox like website for Open CSP 2. There are several options.. turn open-csp.org into a Open CSP 2 installed website ( it is currently based on a different version ); and/or create a ( by invite or request only ) sandbox like Open CSP 2 website where interested people can test and try-out Open CSP 2. By request of invite only, can also demonstrate the fact that Open CSP 2 has built-in user group restrictions if needed.
* Next meeting to be set in 2 weeks.

MR Steering committee 2023-10-06

2025-07-15T09:04:36Z

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

===Notes===
Marijn had internet problems, so he did not really attend. This meeting lasted for approx 1,5 hrs.

===Agenda===

#Status Open CSP 2.0
##Status Documentation
##Status internal rewrite and changes to beta version
##Status install script
##Status web installer
##Status compatibility check current MediaWiki instalment and consequences
#What others can contribute
#Planning for October release

===Discussed===
(1.2) Liselot wrote documentation about Class Definitions and its architecture.

(1.1) Charlot added an about Open CSP page. Ad is going to have a look at it as an extra pair of eyes.

(1.3) Wout, from Wikibase Solutions, is currently still writing the install script

(1.4, 1.5) An extension WSImageVersion is to be forked and renamed to OpenCSP. It will hold the current Open CSP version, a special page with compatibility check and a special page to run the install as an admin from a Special Page instead of a terminal. Still work in progress and will be done after release.

(2, 3) Charlot will have a look at creating a promotional video and a more technical or demonstration of use video. These can be used for socials and for Cindy to talk the importance of splitting content from meta data and other subjects. SMWCon is mentioned. Still work in progress and will be done after release.

(2) Bryan will, once Open CSP 2 is released, contribute to the documentation and his findings. We hope to release Open CSP 2.0 coming week

(2) Bryan wants to use ArrayFunctions and suggested some sort of Sandbox. Action for Marijn. Since Marijn was not there, this is still open.

=== Other things discussed ===

* Support for Elastic Search 8
* Status Semantic MediaWiki
* SMWCon Winter 2023

DevOps:Doc/Open CSP/2.0/Extensions

2025-07-15T09:01:44Z

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

== Extensions are installed with Composer ==
Open CSP uses composer for installation of extension.

=== Extensions and skin used ===

<table class="table table-hover">
<tr>
<th scope="col">Name</th>
<th scope="col">Version / Branch</th>
</tr>
<tr>
<td>AdminLinks</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>Bootstrap</td>
<td>4.5.0</td>
</tr>
<tr>
<td>ChameleonSkin</td>
<td>^4.2</td>
</tr>
<tr>
<td>DisplayTitle</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>MyVariables</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>ReplaceText</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>SemanticExtraSpecialProperties</td>
<td>3.0.4</td>
</tr>
<tr>
<td>SemanticMediaWiki</td>
<td>^4.1.1</td>
</tr>
<tr>
<td>SemanticResultFormats</td>
<td>4.0.2</td>
</tr>
<tr>
<td>SemanticScribunto</td>
<td>2.2.0</td>
</tr>
<tr>
<td>UrlGetParameters</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>UserFunctions</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>Widgets</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>Elasticsearch</td>
<td>^6.8</td>
</tr>
<tr>
<td>FlexForm</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>PageSync</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>WSSlots</td>
<td>^4.0</td>
</tr>
<tr>
<td>WSSPaces</td>
<td>^2.2</td>
</tr>
<tr>
<td>WikiSearch</td>
<td>dev-REL1_39</td>
</tr>
<tr>
<td>ArrayFunctions</td>
<td>v1.4.2</td>
</tr>
<tr>
<td>CSPResources</td>
<td>v2.0.0</td>
</tr>
<tr>
<td>WikiSearchFront</td>
<td>v2.0.4</td>
</tr>

</table>

DevOps:Doc/FlexForm/1.0/edit/example

2025-07-15T09:01:44Z

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

DevOps:Doc/PageSync/2.1/submit a share file

2025-07-15T09:01:43Z

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

If you think you have an '''PageSync ShareFile''' that is interesting for others and you would like to have it show up in the list on the PageSync Special page, then read on.

===How to add to the PageSync Sharefile repo===

When creating the share file, all necessary form fields must have been filled using the English language.

You can fork https://github.com/Open-CSP/PageSync-SharedFiles.

Add your own PageSync Share File in the correct category. Currently we have "General", "Extensions", 'Company", "Open-CSP".

Inside the category you create a folder with a valid and logical name. See this as the subcategory. Good change there already is subcategory for e.g. a popular extension.

Then you can use that. Example "Extensions/FlexForm". In this folder you can upload your PageSyncShare File. Use the original Filename that PageSync produced!

Then add your information to the index.json in the root of the Repository. This information is displayed on the PageSync Shared Files list.

That's it.

DevOps:Doc/FlexForm/1.0/fieldset

2025-07-15T09:01:42Z

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

===Name===
fieldset
===Type===
fieldset
===Synopsis===
How to group certain inputfields together
===Description===
A _fieldset can visually group certain form elements together. In other word you can group questions related to each other.

A _fieldset is useally used in combination with _legend, but not necessary.
===Parameters===
_fieldset

Can hold all styling HTML5 arguments. It also has a form tag that refers to the form's id when a fieldset is not nested within a form.

You can also disable a fieldset, essentially disabling all _input fields inside a _fieldset.
===Example===
<syntaxhighlight lang="html">
<_form action="get">
<_fieldset>
<_legend>Simple fieldset</_legend>
<_input type="radio" id="radio" /><_label for="radio">Spirit of radio</_label>
</_fieldset>
</_form>
</syntaxhighlight>
<_form action="get">
<_fieldset>
<_legend>Simple fieldset</_legend>
<_input type="radio" id="radio" />
<_label for="radio">Spirit of radio</_label>
</_fieldset>
</_form>

===Note===
===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset

DevOps:Doc/PageSync/1.5/Share pages

2025-07-15T09:01:41Z

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

With PageSync you can also select pages or files and create a '''PageSync Share File''' from them.

A '''PageSync share file''' can be used on another Wiki with PageSync installed and have those pages or files be installed there.

The big difference with the Backup option is that you can choose what pages or files will be included based on tags. Also restoring a backup on another Wiki will add the contents to PageSync to monitor them as well. Restoring a '''PageSync Share''' option only adds the pages or files to a wiki once. Therefore a '''PageSync share file''' could be used to install a set of templates, widgets, pages and files to add functionality to your wiki.

If you navigate to the PageSync Special page and click on the SHARE tab you will see an overview of the shared files you have created if you already have any.

This page allows for you to download a PageSync Share file or delete it from your server. There are also two button to create a new PageSync Share file or install a PageSync Share file.

[[File:Screenshot PageSync Share page.png|alt=Screenshot PageSync Share page|none|thumb|600x600px|PageSync Share page]]

<hr>
==== Install a PageSync Shared File ====
[[File:Screenshot PageSync Install PageSync Share file screen.png|alt=Install PageSync Share file screen|thumb|600x600px|Install PageSync Share file screen]]

Installing a set of pages through a '''PageSync Share file''' is done by sharing the URL where the ZIP file can be downloaded.

On this screen you can type the download URL. This can be e.g. a github link.

When you enter the URL and click the download and preview button, PageSync will check if the file is valid and will take you to the next page where you can view details information on the '''PageSync Share File'''.

[[File:Screenshot PageSync preview ShareFile install.png|alt=Information on the PageSync Share file you are about to install.|left|thumb|600x600px|Information on the PageSync Share file you are about to install.]]

The Preview page will show you all the information available before installing the '''PageSync Share File'''. You also need to agree with the description within the File information.

Once you click the '''INSTALL FILES''' button, PageSync will install all the pages and files that are in the ZIP file.

<hr>
==== Create a PageSync Share File ====
[[File:Screenshot PageSync create PageSync Share File.png|alt=Screenshot PageSync create PageSync Share File|thumb|600x600px|PageSync create PageSync Share File]]

If you click the create the button create a share ZIP file, you will get a new screen where you select pages or files based on their tags.

You have three options there..

* Pages must have all chosen tags
* Pages must have at least one chosen tag
* Ignore tags and select all synced pages

[[File:Screenshot PageSync create share file overview.png|alt=Screenshot PageSync create share file overview|left|thumb|600x600px|PageSync create share file overview]]

After clicking the '''Select and preview pages'''-button you will get an overview of the selected pages and files.

You will also '''need''' to add a Description/Disclaimer to the to be created Share File.

Project, Company and Name are optional. PageSync will always add your name and the name of the Wiki where you are creating the '''PageSync Share file''' from.

This information will be shown when someone wants to install you PageSync Share File.

Once you click on the '''Create share file'''-button, you will go back to the main PageSync Share page with an overview of your '''PageSync Share Files'''.

DevOps:Doc/FlexForm/1.1/Installation of FlexForm

2025-07-15T09:01:36Z

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

== Installation ==
Grab in instance from https://github.com/WikibaseSolutions/FlexForm.

Create a "'''FlexForm'''" folder in your Wiki extensions folder and extract the files there.

==== Setup ====
You can tweak '''FlexForm''' to an extent in your Localsettings.php<syntaxhighlight lang="php">
$wgFlexFormConfig['secure'] = true; //( default is true ). Will render form that make no sense when inspected in the browser

$wgFlexFormConfig['sec_key'] = ""; // A salt key for encryption. Used together with "secure" option. Must be set when using multiple instances of a wiki

$wgFlexFormConfig['auto_save_interval'] = 30000; // Interval time in ms, defaults to 3 minutes (180000 ms). Form is submitted on each interval regardless of changes.

$wgFlexFormConfig['auto_save_after_change'] = 3000; // Time in ms, defaults to 3 seconds (3000 ms). Form is submitted after the specified time, timer starts when there is a change in the form. Timer resets if there is another change before the time has passed.

$wgFlexFormConfig['auto_save_btn_on'] = 'Autosave on'; // text on the autosave button to toggle on

$wgFlexFormConfig['auto_save_btn_off'] = 'Autosave off'; // text on the autosave button to toggle off

$wgFlexFormConfig['FlexFormDefaultTheme'] = "plain"; // Currently the only form

$wgFlexFormConfig['rc_site_key'] = ""; // reCaptcha site key

$wgFlexFormConfig['rc_secret_key'] = ""; // reCaptcha secret key

$wgFlexFormConfig['file_temp_path'] = ""; // Where to store images temporarily that need to be format converted

$wgFlexFormConfig['can_create_user'] = ""; // Defaults to false. Set to yes if FlexForm is allowed to create new users

$wgFlexFormConfig['filter_input_tags'] = false; // Defaults to false. Will filter all parser arguments to plain text, except value parameters. Will also disallow onClick and onFocus parameter. This feature will most likely be removed in future updates.

$wgFlexFormConfig['CreateAndEditForms']['allowedGroups'] = ["sysop","moderator"]; // Defaults to sysop. Only a user in the allowedGroups is able to edit pages with a FlexForm in the source.

$wgFlexFormConfig['CreateAndEditForms']['hideEdit'] = true; // Defaults to true. If a user is not in the allowedGroups then hide edit and editsource menu items for any page containing a FlexForm form.

$wgFlexFormConfig['create-seo-titles'] = true; // Defaults to false. Will turn titles given to wscreate into url friendly slugs. Creating only latin character and converting spaces and special characters.

</syntaxhighlight>

==== Finally ====
Add the following line at the end of your LocalSettings.php to enable the extension :<syntaxhighlight lang="php">
wfLoadExtension( 'FlexForm' );
</syntaxhighlight>

It is also a good idea to turn off parsing cache when using dynamic forms like FlexForm.
<syntaxhighlight lang="php">
$wgParserCacheType = CACHE_NONE;
</syntaxhighlight>

==== Notification/Messages ====
'''FlexForm''' has a notification system build in. This is used to show possible errors or success / custom messages.
To enable this.. add to your header page :<syntaxhighlight lang="php">
<_form showmessages />
</syntaxhighlight>

DevOps:Doc/FlexForm/1.0/Installation of FlexForm

2025-07-15T09:01:32Z

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

DevOps:Doc/Open CSP/2.0/Class definition architecture

2025-07-15T09:01:21Z

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

Open CSP stores metadata of pages in slots. Pages are displayed with various components (for which the Chameleon skin is used), which can look differently based on the configuration found in class definition pages.

== Metadata stored in slots ==
Before slots were used, there were two common ways to deal with structured data:

* A) Have templates with structured data in between the content (free text) of a page.
* B) Have one template that wraps the entire page content, with some parameters for structured data and also a parameter for free text

The advantage of using slots is that you can separate the metadata from the content and also separate the storing of the data from displaying it. This reduces the risk of making mistakes when editing, while allowing you to have forms for editing structured data and to use VisualEditor to edit the main content.

Note: data is stored in SMW properties as well, but class definitions do not rely on this. SMW is used for example for [[Search]] and [[Pages]]. It would technically be possible to modify the Open CSP framework to work with a different data storage extension, if you would make your own alternatives for the pages that use SMW queries or WikiSearch.

The following slots are used by Open CSP:

=== csp-base-props ===
In this slot '''Template:Base properties''' is used to store data dat is common to all pages, such as the Class and Title:<syntaxhighlight lang="html">
{{Base properties
|Class=
|Title=
}}
</syntaxhighlight>

=== csp-class-props ===
In this slot '''Template:Csp class properties''' is used to store data that is specific to each class, based on the class definition:<syntaxhighlight lang="html">
{{Csp class properties
|Parameter1=Value1
|Parameter2=Value2
|...
}}
</syntaxhighlight>

=== csp-data ===
This is a json slot which the framework only uses for class definition pages, but could be used for storing any json data on content pages as well (if you make your own templates/forms for this).

=== Example slots of a content page ===
Let's say we have a page about a person, this could have the following slots:

csp-base-props:<syntaxhighlight lang="html">
{{Base properties
|Class=Person
|Title=Example person
}}
</syntaxhighlight>csp-class-props:<syntaxhighlight lang="html">
{{Csp class properties
|First name=John
|Last name=Smith
|Date of birth=1986-03-16
}}
</syntaxhighlight>

=== Example slots of a class definition page ===
To continue the previous example, a "Person" class definition page would have pagename '''Wiki:Class definition/Person''' and could have the following slots:

csp-base-props:<syntaxhighlight lang="html">
{{Base properties
|Class=Class definition
|Title=Person
}}
</syntaxhighlight>csp-class-props:<syntaxhighlight lang="html">
{{Csp class properties
|Defines class=Person
|Pagetitle format=title
|Layout areas='sub-header sidebar' 'main sidebar'
|Layout columns=3fr 1fr
|Layout rows=auto 1fr
}}
</syntaxhighlight>csp-data:<syntaxhighlight lang="html">
{
"CspParameterDefinitions": [
{
"name": "First name",
},
{
"name": "Last name",
},
{
"name": "Date of birth",
"formfieldTemplate": "Csp formfield/date",
"displayTemplate": "Csp parameter display/date",
}
]
}
</syntaxhighlight>

== Components ==
Open CSP uses the Chameleon skin to be able to display pages with customizable components. The following components are used:

* '''Header:''' always visible at the top of a page
* '''Main''': this component displays the content that is stored in the main slot of a page, i.e. the text that is written by users
* '''Sub-header''': by default shown below the header with '''Template:Csp default subheader''', can be customized through class definitions
* '''Sidebar''': by default shown on right side with '''Template:Csp default sidebar''', can be customized through class definitions, metadata is displayed in this component
* '''Footer''': by default not displayed, can be customized through class definitions

<br>Open CSP uses system messages inside these components. These system message contain some logic with various parser functions and Lua functions, in order to display a component based on the slot data of page as well as the slot data of the corresponding class definition page. This logic works as follows:

* A component contains a system message that invokes a Lua function, for example <code><nowiki>{{#invoke:CspComponents|parseComponentIfApplicable|sidebar}}</nowiki></code>. This Lua function does the following:
* Retrieve slotdata from current page
* Get "Class" parameter from slotdata (return if it does not exist)
* Get class definition pagename corresponding to the class
* Get slotdata from class definition page (return if it does not exist)
* If the component is not found in the "Layout areas" parameter of the class definition page, return
* Parse component template (for example '''Template:Csp default sidebar''', unless a different template is found in the class definition data)
* Pass all of the slotdata from the current page as well as the class definition slotdata to this template, in the form of an ArrayFunctions export

== The "Wiki" namespace ==
Open CSP uses the Wiki namespace. Technically this is the standard Project namespace, which has been labeled "Wiki". This namespace is intended for technical pages for development or configuration of the wiki. It is not intended for users that only write or read content on the wiki. For example class definitions and the "Slots" page are in this namespace. The class definition architecture currently relies on the class definition pages having a specific pagetitle format, so you should not move these pages to different namespaces or modify their titles. If you want to restrict access to this namespace, that is possible by using an extension like Lockdown.

DevOps:Doc/FlexForm/1.0/input/datetime-local

2025-07-15T09:01:19Z

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

===Name===
datetime-local
===Type===
_input
===Synopsis===
How to render a date and time input field
===Description===
_input elements of type datetime-local create input controls that let the user easily enter both a date and a time, including the year, month, and day as well as the time in hours and minutes.

The format of the date and time value used by this input type is YYYY-MM-DDThh:mm.
===Parameters===
type="datetime-local"

All other valid parameters for an input field are valid. Additionally you can use min, max and step.
===Example===
<syntaxhighlight lang="html">
<_label for="meeting-time">Choose a time for your appointment:</_label>
<_input type="datetime-local" id="meeting-time"
name="meeting-time" value="2022-03-01T10:00"
min="2022-03-01T10:00" max="2022-03-01T18:00" />
</syntaxhighlight>
<_label for="meeting-time">Choose a time for your appointment:</_label>
<_input type="datetime-local" id="meeting-time"
name="meeting-time" value="2022-03-01T10:00"
min="2022-03-01T10:00" max="2022-03-01T18:00" />
===Note===
The displayed date and time formats differ from the actual value; the displayed date and time are formatted according to the user's locale as reported by their operating system, whereas the date/time value is always formatted YYYY-MM-DDThh:mm.

For more information on this input type, see the link below.
===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local

DevOps:Doc/PageSync

2025-07-15T09:01:19Z

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

[[File:PageSync logo.png|frameless]]

== '''Empowering Wiki Content Synchronization''' ==
'''PageSync''' is a powerful and versatile MediaWiki extension designed to simplify the management and synchronization of wiki content. Developed to meet the evolving needs of wiki administrators, PageSync streamlines the handling of wiki pages, templates, forms, and media files, offering an array of features that empower users to take control of their wiki projects with precision and ease.

==='''The Need for Wiki Content Synchronization'''===
MediaWiki, the engine behind renowned platforms like Wikipedia, is a dynamic and collaborative environment where content evolves continuously. Wikis serve as knowledge repositories, documentation hubs, and collaborative workspaces, making it imperative to maintain content consistency across various stages of development, from initial drafts to production-ready pages.

'''PageSync''' addresses the challenges that administrators and wiki contributors encounter when managing wiki content, especially in scenarios involving multiple environments, version control, and collaborative projects. It introduces a suite of functionalities that enhance content management, backup and restore capabilities, and the selective synchronization of pages and files.

=== '''Key Features of PageSync''' ===

===='''1. Synchronize with Precision'''====
PageSync offers fine-grained control over content synchronization. Wiki administrators and sysops can selectively choose which pages and files to sync based on tags. This level of control ensures that only the most relevant and critical content is included in synchronization processes, reducing clutter and improving workflow efficiency.

===='''2. Backup and Restore'''====
Content is invaluable, and PageSync recognizes the importance of data security. The extension facilitates the creation of snapshots of wiki content, allowing for periodic backups. In the event of accidental data loss or the need to revert to a previous state, PageSync's restore capabilities offer a lifeline to restore content to specific snapshots.

===='''3. PageSync Share: Collaborative Content Sharing'''====
PageSync Share is a unique feature that enables users to package selected sets of pages, files, and descriptions into PageSync Share Files. These files can then be easily shared and installed on other MediaWiki installations with PageSync installed. Share Files allow for the controlled transfer of structured content, enhancing collaborative efforts between wikis.

===='''4. Real-Time Search'''====
PageSync simplifies content retrieval with its built-in real-time search feature. Users can quickly locate synced pages using this feature, improving efficiency and speeding up content management tasks.

===='''5. Semantic Query Integration'''====
PageSync integrates seamlessly with Semantic MediaWiki, offering advanced content selection options through Semantic Query capabilities. This integration enhances content synchronization and selection by allowing for the quick addition of pages based on specific query criteria.

===='''6. Maintenance Script for Flexible Installation'''====
PageSync provides a robust Maintenance script that enhances flexibility in content installation. Users can install PageSync Share Files from various sources, including the PageSync Share Repository and compatible sources on GitHub, using this script. It simplifies the process of acquiring and deploying Share Files, making it accessible to users regardless of their technical expertise.

==='''Getting Started with PageSync'''===
Installing PageSync is straightforward, and its user-friendly interface makes managing and syncing content accessible to both novice and experienced wiki administrators. Whether you're looking to maintain content consistency across multiple environments or enhance collaboration in your wiki projects, PageSync provides the tools and features you need to succeed.

Explore the possibilities of PageSync and unlock a new level of content management for your wiki projects. Download PageSync today and experience the power of effortless wiki content synchronization, backup and restore capabilities, and advanced content selection through Semantic Query integration.

Join a growing community of wiki administrators who rely on PageSync to streamline their content management workflows, ensure data integrity, and make content sharing a breeze.

== Need some help? ==

Need some help ?

Try the PageSync Discord channel at https://discord.gg/T8VTjtXGnV

or

Join the PageSync and FlexForm element channel : https://matrix.to/#/#wsform:matrix.org

DevOps:Doc/FlexForm/1.0/input/secure

2025-07-15T09:01:16Z

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

===Name===
secure
===Type===
_input
===Synopsis===
How to render a hidden input field that is secure
===Description===
_input elements of type secure are similar to type hidden. The difference is that a secure field is not readable by a user and a form will fail if it gets altered using Browsers developer tools
===Parameters===
type="secure"

All other valid parameters for an input field are valid
===Example===
<syntaxhighlight lang="html">
<_input type="secure" name="token" value="123231321" />
</syntaxhighlight>
This will render something similar to
<syntaxhighlight lang="html">
<input name="2425fb14579653aef53179a2849e4593ES5rgMk=" value="7cade404c7d02c02a3087e4fd6954caby0QljHbAPys0" type="hidden">
</syntaxhighlight>
===Note===
When using action="get" a secure field will not be returned in the url
===Links===

DevOps:Doc/PageSync/1.5/Using PageSync

2025-07-15T09:01:16Z

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

See also the Special page section below.

Basically, if you are a sysop, any page that can be synced will have a slider in the top menu. Click on it and it will turn blue indicating it is synced ( a notification will also be shown ). If the slider is already blue when you visit a page, it simply means the page is already synced and is being monitored for changes. Click the slider again for the page to be excluded from syncing.

== User rights ==
sysop/admins are allowed to set a page to be synced. All other users have no such ability.

== Special Page ==
By default the special page shows a list of all Wiki pages set for syncing.

* From the Special page you can also create, restore and delete ZIP backups. To be able to use '''ZIP Backups''', make sure ZIPArchive is installed on your PHP setup.
* The special page also allows for you to do a '''Semantic MediaWiki Query''' to quickly add certain pages to '''PageSync'''. This feature only works if you have '''''SemanticMediaWiki''''' extension installed.
* As of version 2.6.5 the special page allows for you to bulk select pages in a '''NameSpace''' and use filter options to quickly find and add pages to '''PageSync'''.
* Creating '''PageSync Share files''' is also done from the Special page.
* The Special Page also shows all currently synced pages.
* New in v2.5 are more administrative functions to bulk delete tags; bulk remove pages from '''PageSync''' by tags; bulk remove pages from '''PageSync''' by using a SMW Query.
* Finally you can also delete all synced pages from the Special page. This will not delete any pages in the Wiki, only the ones stored on the server by '''PageSync'''.

The entry page for the '''PageSync''' Special page will show you a list of all the pages and files that '''PageSync''' is monitoring.

Every listing allows for you to remove the page from '''PageSync''' by clicking it '''SYNC''' slider

The '''Edit button''' allows for adding tags and a description to a page. This is useful if you want to create a '''PageSync''' Share file.

[[File:Screenshot PageSync entry page.png|alt=The entry Special page for PageSync|center|thumb|600x600px|The entry Special page for PageSync]]

== Search ==
As off version 2.5 you have a search bar to quickly and realtime search for Synced pages by Title.
[[File:PageSync main page search bar.png|left|thumb|800x800px]]

DevOps:Doc/Open CSP/2.0/Class definition customization options

2025-07-15T09:01:15Z

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

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 ==
* Edit parameters on a class definition page, to configure what will show up on your sidebar.
* 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.
* Choose a displayTemplate to configure how a parameter is displayed in the view 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.

== Custom formfield/display templates ==
* It is possible to add custom template names in the displayTemplate and formfieldTemplate fields.
* 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.
* 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.

== Custom sidebar template where you are adding to the default sidebar ==
In many cases you won't necessarily want to replace the default sidebar, but you may want to add another card above or below it with additional functionality. It is possible to use the default sidebar within a custom sidebar template. For example like the following code snippet:<syntaxhighlight lang="wikitext">
{{Csp default sidebar
|$pageData={{{$pageData|}}}
|$classData={{{$classData|}}}
}}

{{Csp sidebar tabs
|id=another-card
|canEdit=yes
|closeButton=
|title=Another card
|subTitle=Below the default sidebar
|view=<div class="card-body">viewtab content</div>
|edit=<div class="card-body">edittab content</div>
}}
</syntaxhighlight>

== Fully custom sidebar template ==
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="html">
<div class="tab-content"><input type="radio" id="sidebar-view" name="toggle-sidebar" checked="checked" class="d-none sidebar-view" /><div class="card sidebar-view-tab">
<div class="card-header">{{#ifeq:{{#ifingroup:user |{{#if:{{#urlget:veaction}}{{#urlget:action}}||yes}} }}|yes |<span style="float:right"><label for="sidebar-edit" class="btn btn-secondary">Edit</label></span>}}
<b class="d-block">{{#af_get:{{{$pageData}}}|csp-base-props|Base properties|1|Class|_text}}</b>
{{#af_get:{{{$pageData}}}|csp-base-props|Base properties|1|Title|_text}}
</div>
<div class="card-body">
{{Csp sidebar item
|Label=Title
|Value={{#af_get:{{{$pageData}}}|csp-base-props|Base properties|1|Title |_text}}
}}{{Csp sidebar item
|Label=TextInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TextInput |_text}}
}}{{Csp sidebar item
|Label=TokenInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TokenInput |_text}}
}}{{Csp sidebar item
|Label=AskTokenInput
|Value={{#af_join:{{#af_map:{{#af_split:{{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|AskTokenInput |_text}}|,}}|@@|[[{{{@@}}}|{{#show:{{{@@}}}|?Title}}]]}}|<br>}}
}}{{Test date display
|Name=DateInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|DateInput |_text}}
}}
{{Csp sidebar item
|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}} }} }}
}}{{Csp sidebar item
|Label=TextInputTwo
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TextInputTwo |_text}}
}}{{Csp sidebar item
|Label=CheckboxInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|CheckboxInput |_text}}
}}{{Csp sidebar item
|Label=TextAreaInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TextAreaInput |_text}}
}}{{Csp sidebar item
|Label=NumberInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|NumberInput |_text}}
}}{{Csp sidebar item
|Label=SelectInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|SelectInput |_text}}
}}{{Csp sidebar item
|Label=TokenMultipleInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TokenMultipleInput |_text}}
}}</div>
</div>{{#ifeq:{{#ifingroup:user |{{#if:{{#urlget:veaction}}{{#urlget:action}}||yes}} }}|yes |<input type="radio" id="sidebar-edit" name="toggle-sidebar" class="d-none sidebar-edit" /><div class="card sidebar-edit-tab"><div class="card-header"><span style="float:right"><label for="sidebar-view" class="btn btn-secondary" >Close</label></span>
<b class="d-block">{{#af_get:{{{$pageData}}}|csp-base-props|Base properties|1|Class|_text}}</b>
{{#af_get:{{{$pageData}}}|csp-base-props|Base properties|1|Title|_text}}
</div>
<div class="card-body">
<form><_edit target="{{PAGEID}}" template="Base properties" formfield="Title" mwslot="csp-base-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TextInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TokenInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="AskTokenInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="DateInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="DateInputTwo" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TextInputTwo" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="CheckboxInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="TextAreaInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="NumberInput" mwslot="csp-class-props" />
<_edit target="{{PAGEID}}" template="Csp class properties" formfield="SelectInput" 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" />
{{Csp sidebar item
|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}}" />
}}
{{Csp sidebar item
|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}}" />
}}
{{Csp sidebar item
|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" />
}}
{{Csp sidebar item
|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)" >
{{#af_join:{{#af_map:{{#af_split:{{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|AskTokenInput|_text}} }} |$value|<option value="{{{$value}}}" selected="selected">{{#show:{{{$value}}}|?Title}}</option>}}|\n}}
</_token>
}}
{{Test date formfield
|Name=DateInput
|Value={{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|DateInput|_text}}
}}{{Csp sidebar item
|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}}" />
}}
<div class='alert alert-danger'>No template defined in parameter definitions</div>{{Csp sidebar item
|Label=<label for="checkbox-{{lc:{{anchorencode:CheckboxInput}} }}" >CheckboxInput</label>
|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}}" />
}}
{{Csp sidebar item
|Label=TextAreaInput
|Value=<input type="textarea" name="TextAreaInput" class="form-control" >{{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TextAreaInput|_text}}</input>
}}
{{Csp sidebar item
|Label=NumberInput
|Value=<input type="number" name="NumberInput" class="form-control" value="{{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|NumberInput|_text}}" />
}}
{{Csp sidebar item
|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" />
}}
{{Csp sidebar item
|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" />
}}
{{Csp sidebar item
|Label=TestNoDisplay
|Value=<input type="text" name="TestNoDisplay" class="form-control" value="{{#af_get:{{{$pageData}}}|csp-class-props|Csp class properties|1|TestNoDisplay|_text}}" />
}}
<div class="text-right">
<label for="sidebar-view" class="btn btn-secondary">Close</label>
<input type="submit" value="Save" class="btn btn-primary" />
</div>
</form>
</div>
</div>
|}}
</div>
</syntaxhighlight>

DevOps:Doc/Open CSP/1.0/Requirements

2025-07-15T09:01:14Z

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

The Open CSP framework will be installed on a current MediaWiki installation. That MediaWiki installation should meet these requirements:
* PHP version >=8.0 <9
* Composer version >=2
* Mediawiki version 1.39
* ElasticSearch version 6.8

DevOps:Doc/Open CSP/2.0/Class definitions

2025-07-15T09:01:14Z

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

In Open CSP you can add structured data to content pages by using class definitions. A class definition is a configuration for a specific type of page.

For example you might have a "Person" class definition. On the class definition page you can configure that a person has parameters such as a first name, last name and date of birth.

When a user creates a person page, they will have the option to fill these fields (or you could also configure them to be mandatory).

The data is by default displayed in a sidebar on the right side of a page, but this layout can also be configured through the class definition.

Managing class definitions is typically done by administrators, while users can create content pages with the defined classes.

Data is stored in slots, so that users can edit the main content of a page in the same way as you would edit any wiki page, without having templates and other non content related items.

DevOps:Doc/FlexForm/1.0/input/date

2025-07-15T09:01:12Z

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

===Name===
date
===Type===
_input
===Synopsis===
How to render a date input field
===Description===
_input elements of type="date" create input fields that let the user enter a date, either with a textbox that validates the input or a special date picker interface.

The resulting value includes the year, month, and day, but not the time.

The date is formatted according to ISO8601, described in Format of a valid date string in Date and time formats used in HTML.
===Parameters===
type="date"

All other valid parameters for an input field are valid. Additionally you can use min, max and step.
===Example===
<syntaxhighlight lang="html">
<_input type="date" name="date" value="2022-03-01" min="2022-01-01" max="2022-12-31" />
</syntaxhighlight>
<_input type="date" name="date" value="2022-03-01" min="2022-01-01" max="2022-12-31" />
===Note===
When an incorrect date is entered, the browser will fall back to a text-input field. Read the link below how to handle these situations.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date

DevOps:Doc/Open CSP/2.0/About Open CSP

2025-07-15T09:01:12Z

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

<h1 class="display-3">About Open CSP</h1>

==== Introduction ====
Open CSP, short for "Open Content Services Platform," is a versatile and innovative open-source software solution designed to transform the way organizations manage, collaborate on, and access digital content and knowledge. This platform is built upon the robust foundation of the MediaWiki platform, enriched with powerful extensions, and tailored to meet the diverse needs of content management, structured data collection, and dynamic forms creation. By leveraging open-source technology, Open CSP ensures no vendor lock-in, providing organizations with full control and flexibility while maintaining a low cost of ownership.

=== Key Highlights of Open CSP ===

* '''Open Source Freedom''': Open CSP is open-source, ensuring that organizations are free from vendor lock-in. This openness allows for complete control over the software and data, fostering an environment of flexibility and innovation.
* '''Low Maintenance and Cost-Effective''': Open CSP is versionized, meaning administrators only need to install or update to new versions to automatically integrate the latest extensions, templates, and maintenance work. This streamlined update process significantly reduces administrative workload and keeps the total cost of ownership extremely low.
* '''Structured Data Mastery''': Leveraging the power of Semantic MediaWiki, Open CSP empowers organizations to manage structured and semantic data effectively, creating meaningful connections between information.
* '''Dynamic Forms''': With the integrated FlexForm extension, users can effortlessly create customized forms for data collection, surveys, and more, enhancing data-driven workflows and interactions. FlexForm also includes a built-in Word to Wiki converter, simplifying content migration from Microsoft Word and other word processing applications, further expanding its utility for users.
* '''Efficient Search''': Open CSP features robust search capabilities, enabling users to quickly locate and access relevant content and information within the platform.
* '''Tailored Customization''': Open CSP provides extensive customization options, allowing users to personalize the platform to suit their unique needs, whether it's for traditional wikis, structured data initiatives, or specialized knowledge sharing.
* '''Community Engagement''': The platform fosters community engagement and collaboration, making it easier for teams to work together and share knowledge effectively.

=== Use Cases ===
Open CSP is suitable for a wide range of use cases, including:

* '''Traditional Wikis''': Create and manage wikis with user-friendly editing and content organization features.
* '''Knowledge Bases''': Build comprehensive knowledge bases for easy access to critical information.
* '''Data Collection''': Utilize dynamic forms for structured data collection, surveys, and feedback.
* '''Collaborative Workspaces''': Foster collaboration and teamwork within your organization.

=== Enterprise Use Cases ===

# '''Project Collaboration and Documentation''': Open CSP can serve as a centralized platform for project teams to collaborate, share documents, track project progress, and maintain documentation. Teams can create project-specific wikis and dynamic forms to streamline project management.
# '''Corporate Intranet''': Open CSP can function as an intranet portal, providing employees with a centralized hub for accessing company policies, procedures, employee directories, and internal news. The platform's dynamic forms can be used for employee surveys, feedback collection, and IT service requests.
# '''Knowledge Base for Customer Support''': Enterprises can build a robust knowledge base using Open CSP to support customer service teams. Articles, FAQs, troubleshooting guides, and product documentation can be organized and easily accessible to assist customer support representatives in resolving customer inquiries efficiently.
# '''Human Resources and Training''': Open CSP can be employed by HR departments to manage employee training materials, onboarding processes, and policy documentation. Dynamic forms can facilitate training program enrollment and feedback collection.
# '''Compliance and Regulatory Documentation''': Enterprises operating in regulated industries can use Open CSP to maintain compliance documentation, track regulatory changes, and ensure employees have access to up-to-date compliance materials.
# '''Quality Assurance and Process Management''': Open CSP can support quality assurance efforts by providing a platform for documenting and managing quality processes, audit records, and continuous improvement initiatives. Dynamic forms can facilitate incident reporting and corrective action workflows.
# '''Sales and Marketing Collateral''': Sales and marketing teams can use Open CSP to store and manage sales collateral, marketing materials, product catalogs, and campaign assets. The platform can enhance collaboration between sales and marketing departments.
# '''Multi-Departmental Collaboration''': Large enterprises with multiple departments can benefit from Open CSP's ability to create department-specific wikis and forms. This encourages interdepartmental collaboration while maintaining separate spaces for each team's content.
# '''Custom Enterprise Apps''': Open CSP's flexibility allows organizations to develop custom enterprise applications by integrating forms and structured data with business processes. This can include custom dashboards, reporting tools, and workflow automation.
# '''Intellectual Property Management''': Companies with intellectual property assets can use Open CSP to manage patents, trademarks, copyrights, and licensing agreements. The platform can help centralize IP-related documents and ensure compliance.
# '''Supplier and Vendor Management''': Open CSP can be employed to maintain supplier and vendor documentation, contracts, procurement processes, and vendor performance records. This supports efficient supplier relationship management.

=== Conclusion ===
Open CSP is the go-to solution for organizations seeking an adaptable, open-source platform for content and data management, knowledge sharing, and structured information collection. Its flexible nature, semantic capabilities, dynamic forms, and content import capabilities make it an ideal choice for businesses, educational institutions, nonprofits, and others looking to harness the power of wikis and structured data in a unified, user-friendly environment. By eliminating vendor lock-in and reducing maintenance efforts, Open CSP ensures a low cost of ownership while providing powerful tools to meet diverse organizational needs.