BlueSpice - Recent changes [en]

Manual:Extension/BlueSpiceCountThings

Margit.link-rodrigue — Fri, 15 May 2026 15:27:43 GMT

← Older revision		Revision as of 15:27, 15 May 2026
Line 10:		Line 10:
	\|+		\|+
	!Content Droplet		!Content Droplet
	!Inserts tag		! style="width:150px;" \|Inserts tag
	!Description		!Description
	\|-		\|-
	\|Number of characters		\|Number of characters
	\|<nowiki><countcharacters></nowiki>		\| style="width:150px;" \|<nowiki><countcharacters /></nowiki>
	\|Counts all characters or words on a wiki page		\|Counts all characters or words on a wiki page:

			* ''all (default)'': displays all of the above information in a table
			* ''characters'': number of characters on the current page (based on the wiki code, including spaces)
			* ''words'': number of words on the current page
			* ''characters and words:'' number of words and characters on the current page
			* ''pages:'' number of pages the current article would occupy when printed or exported
	\|-		\|-
	\|Number of files		\|Number of files
	\|<nowiki><countfiles /></nowiki>		\| style="width:150px;" \|<nowiki><countfiles /></nowiki>
	\|Counts all uploaded files		\|Counts all uploaded files
	\|-		\|-
	\|Number of pages		\|Number of pages
	\|<nowiki><countarticles /></nowiki>		\| style="width:150px;" \|<nowiki><countarticles /></nowiki>
	\|Counts all content pages in the wiki		\|Counts all content pages in the wiki
	\|-		\|-
	\|Number of users		\|Number of users
	\|<nowiki><countusers /></nowiki>		\| style="width:150px;" \|<nowiki><countusers /></nowiki>
	\|Counts all registered users		\|Counts all registered users
	\|}		\|}

MediaWiki:Common.css

Margit.link-rodrigue — Fri, 15 May 2026 15:24:18 GMT

← Older revision		Revision as of 15:24, 15 May 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	/* Das folgende CSS wird für alle Benutzeroberflächen geladen. */		/* Das folgende CSS wird für alle Benutzeroberflächen geladen. */
			/modernize wikitable/

			.wikitable {background-color:white!important;}
			.wikitable tr th {background-color:#f2f3f9!important}
			.wikitable th, .wikitable td {border-color: #c4c5ca!important}

	/Custom formatting for centering footer links/		/Custom formatting for centering footer links/

Manual:Extension/BlueSpiceCountThings

Margit.link-rodrigue — Fri, 15 May 2026 15:02:30 GMT

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:CountThings}}'''CountThings''' introduces a set of tags for counting various metadata in the wiki. Available tags are: countarticles, countusers, countfiles, and countcharacters.
+{{DISPLAYTITLE:CountThings}}'''CountThings''' introduces a set of tags for counting various metadata in the wiki. Available tags are: ''countarticles'', ''countusers'', ''countfiles'', and ''countcharacters''.
-==Inserting tags==
+==Usage==
-[[File:ve-magicword.png|link=https://en.wiki.bluespice.com/wiki/File:ve-magicword.png|alt=Insert magic word|thumb|151x151px|Insert magic word]]
+The tags are added as Content Droplets in visual edit mode.
-Tags are added through the "InsertMagic" dialog by clicking on "Insert" in VisualEditor toolbar and then on "Magic word". In the resulting dialog, choose one of the four previously mentioned types of tags and click "Done".<br />
+[[File:Extension BlueSpiceCountThings droplets.png|alt=Content Droplets menu filtered for "Number of" |center|thumb|550x550px|Inserting counted information via Content Droplets]]
-[[File:VE-magicword-countarticles.png|alt=choosing a tag|center|thumb|450x450px|choosing a tag]]
+<br />
 ===Configuring the countcharacters tag===
-While other tags have no configuration options, and just adding them to the page is sufficient, the ''countcharacters'' tag must be configured.
+While other tags have no configuration options, and just adding them to the page is sufficient, the tag ''Number of characters (countcharacters)'' must be configured.
 After inserting this tag or clicking on an existing tag already on the page, a dialog  opens.
@@ Line 17: / Line 41: @@
 While selecting the mode and page, a preview of the output is displayed above the dialog box. If the page title in the table heading shows the page name in red ("redlink"), you have misspelled the page name and the page does not exist.
 {{Translation}}
 [[Category:Editing]]

File:Extension BlueSpiceCountThings droplets.png

Margit.link-rodrigue — Fri, 15 May 2026 14:13:18 GMT

Redaktion uploaded File:Extension BlueSpiceCountThings droplets.png

New page

Manual:Extension/BlueSpiceContextMenu

Margit.link-rodrigue — Fri, 15 May 2026 13:38:06 GMT

← Older revision		Revision as of 13:38, 15 May 2026
(2 intermediate revisions by the same user not shown)
Line 28:		Line 28:


	Settings for the context menu are located in the user preferences (page''Special:Preferences''), under the "Appearance" tab~~. The setting is applied separate for each user~~.		Settings for the context menu are located in the user preferences (page ''Special:Preferences''), under the "Appearance" tab.

	The context menu has two modes:		The context menu has two modes:

	*Click ~~using the~~ right mouse button and pressing CTRL (Normal right mouse button will show default browser menu)		*Click on right mouse button and pressing CTRL (Normal right mouse button will show default browser menu)
	*Click ~~using the~~ right mouse button (Pressing CTRL will show default browser context menu)		*Click on right mouse button (Pressing CTRL will show default browser context menu)

	~~{{Box Links-en\|Topic1=[[Reference:BlueSpiceContextMenu]]}}~~

	{{Translation}}		{{Translation}}
	__FORCETOC__		__FORCETOC__
	[[Category:Editing]]		[[Category:Editing]]

Manual:Extension/PDFCreator

Margit.link-rodrigue — Fri, 15 May 2026 12:36:40 GMT

@@ Line 338: / Line 338: @@
 .pdfcreator-page-content h2 {
      font-size:11pt
+}
 </syntaxhighlight>
@@ Line 344: / Line 367: @@
 The font used for PDF export is DejaVu Sans.
-It is currently not possible to specify a custom font for PDF printing (BlueSpice cloud). On-premise installations may be able to store a customer font and add a configuration on the server.
+It is currently not possible to specify a custom font for PDF printing (BlueSpice cloud). On-premise installations may be able to store a customer font and add a configuration on the server
 == Tips for preparing  content for the PDF export ==

Manual:Extension/Page Forms

Margit.link-rodrigue — Fri, 15 May 2026 07:26:58 GMT

← Older revision		Revision as of 07:26, 15 May 2026
Line 56:		Line 56:

	Note: In some versions of BlueSpice, the display of the drop-down actions in the editor are broken. You can fix them by adding the following to the global stylesheet <code>MediaWiki:Common.css</code>:<syntaxhighlight lang="css">		Note: In some versions of BlueSpice, the display of the drop-down actions in the editor are broken. You can fix them by adding the following to the global stylesheet <code>MediaWiki:Common.css</code>:<syntaxhighlight lang="css">
	~~/fix page forms issue with visualeditor input /~~		table.formtable,
			table.multipleTemplateInstanceTable {
			border-collapse: inherit;
			}

			.oo-ui-toolGroup-tools{
			height:auto!important;
			}

	.oo-ui-popupToolGroup-tools .oo-ui-tool-link {		.oo-ui-popupToolGroup-tools .oo-ui-tool-link {
	~~display~~: ~~block!important~~;		padding: 5px;
	}		}

	.~~formtable~~ .oo-ui-~~toolGroup~~-tools{
	~~height~~:~~auto!important~~;		.ve-area-wrapper .ve-ui-toolbar .oo-ui-listToolGroup-tools .oo-ui-tool-link .oo-ui-tool-title {
			padding-left: 0.5em;
	}		}
			</syntaxhighlight>'''Insert images:'''

			For the "Insert" menu to offer the option to embed images, the menu bar must be displayed at the top of the text field. This is achieved using <code>class=toolbarOnTop</code>:<syntaxhighlight lang="wikitext">
			{{{field\|mytextarea\|values from namespace=File\|input type=textarea\|editor=visualeditor\|class=toolbarOnTop}}}
	</syntaxhighlight>		</syntaxhighlight>
	\|}		\|}

Manual:Extension/Forms/5.1.8

Margit.link-rodrigue — Tue, 12 May 2026 15:36:42 GMT

← Older revision		Revision as of 15:36, 12 May 2026
Line 4:		Line 4:
	To create a checklist as a form, for example, the following steps are necessary:		To create a checklist as a form, for example, the following steps are necessary:

	# '''Create ~~and save~~ the checklist form''' ~~via the ''Special:Form_editor'' special page. The form serves as a template for all checklists that are created with it.~~		# '''Create the checklist form.'''
	# '''Create ~~and save~~ checklist instances''' ~~via the special page ''Special:Create_form_instance''.~~		# '''Create checklist instances.'''

	Optionally, the styling of the form can be adjusted.		Optionally, the styling of the form can be adjusted.
Line 14:		Line 14:
	==Create a checklist form==		==Create a checklist form==

	# '''~~Define~~''' the ~~main properties of the form:~~		# '''Create''' the page ''Checklist Event Hygiene.form''.[[File:Extension Forms create form.png\|center\|thumb\|400x400px\|alt=Create-page dialog\|Creating a new form]]This opens the Form editor.[[File:Extension Forms form editor.png\|alt=elements of the form editor dialog\|center\|thumb\|700x700px\|Form editor]]
	## ''~~'Open''' the ''Special:Form editor'' page~~.
	~~## '''Enter''' a name for the new~~ form~~, e.g. ''EventChecklistHygiene~~''. ~~This name is used as a unique identifier for the database~~. ~~Therefore, do not use any special characters (apart from the hyphen "~~-~~").~~
	~~## '''Enter'''~~ a ~~title, e.g. Event Checklist.~~ This ~~is displayed as~~ the ~~display title instead of the form name if you activate the Display title checkbox~~. [[File:~~Manual:Checklist-~~form ~~properties~~.png\|alt=~~Form properties~~\|center\|thumb\|~~750x750px~~\|Form ~~properties~~]]
	# '''Add''' a form section:		# '''Add''' a form section:
	##'''Select''' the ''Section label'' element under ''Form Elements > Other'' and, holding down the left mouse button, drag it into the interactive form editor field below.		##'''Select''' the ''Section label'' element under ''Form Elements > Other'' (see screenshot annotation 2) and, holding down the left mouse button, drag it into the interactive form editor field below.
	## '''Click''' the ~~section heading radio button~~. The ~~editing dialog~~ opens.		## '''Click''' anywhere in the ''Section label'' line. The field inspector opens.
	## '''Enter''' ~~a field name~~. This is saved as a field ID in the database and should therefore not contain any special characters.		## '''Enter''' the ''Name''. This is saved as a field ID in the database and should therefore not contain any special characters.
	## '''Enter''' the ~~title~~ for the ~~heading~~. This is ~~used~~ as the ~~display title in~~ the ~~form~~.[[File:~~Manual:Checklist-form element-~~section ~~label~~.png\|alt=~~Create section~~ label\|center\|thumb\|~~750x750px~~\|~~Create~~ section ~~label~~]]		## '''Enter''' the ''Title'' for the section label. This is displayed as the visible label for the text field.[[File:Extension Forms add section header.png\|alt=Section label element inspector\|center\|thumb\|700x700px\|Adding the first section header]]
	# '''Create''' the form fields for the Event section. Here we add a text box as an example.		# '''Create''' the form fields for the Event section. Here we add a text box as an example.
	## '''Drag''' the ''Text'' element under the section heading ~~while holding down the left mouse button~~.		## '''Drag''' the ''Text'' element from ''Form elements > Inputs'' under the section heading.
	## '''Click''' the text ~~box radio button~~.		## '''Click''' anywhere in the ''text field'' line. The field inspector opens.
	## '''Enter''' ~~a name~~. This is used as the database ID for this field and should therefore not contain any special characters.		## '''Enter''' the ''Name''. This is used as the database ID for this field and should therefore not contain any special characters.
	## '''Enter''' ~~a label~~. This is displayed as the label for the text field.		## '''Enter''' the ''Label''. This is displayed as the visible label for the text field.
	## '''Add''' more form elements.		## '''Add''' more form elements.
	# '''Click''' ~~Submit at the bottom of the page to save the form~~. The form is now ~~stored~~ in the main namespace as ''EventChecklistHygiene.form''. [[File:Manual:Checklist-view.png\|alt=Saved form\|center\|thumb\|650x650px\|Saved form]]<br />To continue editing the form, switch to the editing mode of the page (1).		# '''Click''' ''Save''. The form is now available in the main namespace as ''EventChecklistHygiene.form''. [[File:Manual:Checklist-view.png\|alt=Saved form\|center\|thumb\|650x650px\|Saved form]]<br />To continue editing the form, switch to the editing mode of the page (1).

	==Create a checklist instance==		==Create a checklist instance==
	To ~~use~~ the form~~, create your first checklist~~.		To create a checklist from the form:

			enter a target page name.

	~~# '''Open''' the page ''Special:Edit_with_form''.~~
	~~# '''Choose''' the form ''EventChecklistHygiene''.~~
	# '''Fill out''' the form fields.		# '''Fill out''' the form fields.
	# '''Click''' ''Submit''.~~[[File:Manual:Checklist-create instance.png\|alt=Create a checklist instance\|center\|thumb\|650x650px\|Create a checklist instance]]~~		# '''Click''' ''Submit''.

	The checklist is now saved in the wiki and can be edited further.		The checklist is now saved in the wiki and can be edited further.

File:Extension Forms add section header.1.8 1778599455610.png

Margit.link-rodrigue — Tue, 12 May 2026 15:24:29 GMT

Redaktion uploaded File:Extension Forms add section header.1.8 1778599455610.png

New page

File:Extension Forms form editor.1.8 1778599118119.png

Margit.link-rodrigue — Tue, 12 May 2026 15:18:45 GMT

Redaktion uploaded File:Extension Forms form editor.1.8 1778599118119.png

New page

File:Manual:Manual Extension Forms create form.1.8 1778598764784.png

Margit.link-rodrigue — Tue, 12 May 2026 15:12:55 GMT

Redaktion uploaded File:Manual:Manual Extension Forms create form.1.8 1778598764784.png

New page

Templates download/Profile Gallery

Margit.link-rodrigue — Tue, 12 May 2026 15:00:05 GMT

← Older revision		Revision as of 15:00, 12 May 2026
Line 5:		Line 5:

	</div>		</div>
	The ''Profilegallery'' template displays the profile pictures of users in a department on a page. The department name must be entered on the users’ profile pages. If no profile picture exists, the user avatar is displayed.		The ''Profilegallery'' template displays the profile pictures of users in a department on a page. The department name must be entered on the users’ profile pages. If no profile picture exists, the user avatar is displayed.{{Templateimport\|HW-Profilegallery}}

	~~==Importing the Template==~~
	{{Templateimport\|HW-Profilegallery}}

	==Imported pages==		==Imported pages==

File:HW-Profilegallery.zip

Margit.link-rodrigue — Tue, 12 May 2026 14:59:49 GMT

Redaktion uploaded a new version of File:HW-Profilegallery.zip

New page

Templates download

Margit.link-rodrigue — Tue, 12 May 2026 14:58:54 GMT

← Older revision		Revision as of 14:58, 12 May 2026
(One intermediate revision by the same user not shown)
Line 84:		Line 84:
	<!--start card------------------>		<!--start card------------------>
	<div>		<div>
	==[[Templates download/Process map\|Process ~~map~~]]==		==[[Templates download/Process map\|Process Map]]==
	<div class="box">		<div class="box">
	<div class="screenshot">[[File:HW-process map text-based.png\|800x800px\|alt=Text-based process map\|link=Templates download/Process map]]</div>		<div class="screenshot">[[File:HW-process map text-based.png\|800x800px\|alt=Text-based process map\|link=Templates download/Process map]]</div>
	<div class="text">[[Templates download/Process map\|Text-based process map]] (TD)</div>		<div class="text">[[Templates download/Process map\|Text-based process map]] (TD)</div>
			</div>
			</div>
			<!--start card------------------>
			<div>
			==[[Templates download/Profile Gallery\|Profile Gallery]]==
			<div class="box">
			<div class="screenshot">[[File:HW-Profilegallery.png\|800x800px\|alt=Gallery with 5 profile images\|link=Templates download/Profile Gallery]]</div>
			<div class="text">[[Templates download/Profile Gallery\|Department-based profile pictures]] (SMW,TD)</div>
	</div>		</div>
	</div>		</div>
Line 116:		Line 124:
	<!--start card------------------>		<!--start card------------------>
	<div>		<div>
	==[[Templates download/TOClimit\|TOC ~~limit~~]]==		==[[Templates download/TOClimit\|TOC Limit]]==
	<div class="box">		<div class="box">
	<div class="screenshot">[[File:template-download-TOClimit.png\|alt=TOC limit template\|link=Templates download/TOClimit\|460x460px]]</div>		<div class="screenshot">[[File:template-download-TOClimit.png\|alt=TOC limit template\|link=Templates download/TOClimit\|460x460px]]</div>
Line 124:		Line 132:
	<!--start card------------------>		<!--start card------------------>
	<div>		<div>
	==[[Templates download/Trainingpage\|Training ~~page~~]]==		==[[Templates download/Trainingpage\|Training Page]]==
	<div class="box">		<div class="box">
	<div class="screenshot">[[File:HW-Training-en.png\|alt=Training page for internal trainings\|link=Templates download/Trainingpage\|460x460px]]</div>		<div class="screenshot">[[File:HW-Training-en.png\|alt=Training page for internal trainings\|link=Templates download/Trainingpage\|460x460px]]</div>
Line 132:		Line 140:
	<!--start card------------------>		<!--start card------------------>
	<div>		<div>
	==[[Templates download/Transclusion\|Section ~~transclusion~~]]==		==[[Templates download/Transclusion\|Section Transclusion]]==
	<div class="box">		<div class="box">
	<div class="screenshot">[[File:HW-transclusion.png\|alt=Transcluded page section\|link=Templates download/Transclusion\|460x460px]]</div>		<div class="screenshot">[[File:HW-transclusion.png\|alt=Transcluded page section\|link=Templates download/Transclusion\|460x460px]]</div>

Templates download/Profile Gallery

Margit.link-rodrigue — Tue, 12 May 2026 14:55:10 GMT

← Older revision		Revision as of 14:55, 12 May 2026
(One intermediate revision by the same user not shown)
Line 12:		Line 12:
	==Imported pages==		==Imported pages==
	The XML-Import creates the following pages in your wiki:		The XML-Import creates the following pages in your wiki:
	Template:Profilegallery
	Template:Profilegallery/format		* Template:Profilegallery
	Template:Profilegallery/styles.css		* Template:Profilegallery/format
			* Template:Profilegallery/styles.css

	==Displaying profile pictures==		==Displaying profile pictures==

	# '''Insert''' the template on a page using the visual editor.		# '''Insert''' the template on a page using the visual editor.
	# '''Enter''' the name of the department.		# '''Enter''' the name of the department exactly as it is [[Manual:Extension/UserProfile\|defined in the respective users' profiles]].[[File:hw-profilegallery-templatedata.png\|alt=TemplateData dialog for the template with example department \|center\|thumb\|450x450px\|Adding the department name]]
			# '''Click''' ''Apply Changes''.
			The profile pictures are now displayed.

			{{Textbox\|boxtype=important\|header=Note regarding deactivated users:\|text=If a department is listed on the profile page of deactivated users, these users are currently displayed in the gallery as well. If this is not desired, the department name must be removed from the user profiles.\|icon=yes}}

	~~[[File:User profile.png~~\|~~alt~~=~~profile box from the profile page~~\|~~center~~\|~~mini\|550x550px\|Department defined~~ on the profile page]]

	~~The profile pictures~~ are ~~now~~ displayed.~~<br />~~

	==Template parameter==		==Template parameter==
Line 37:		Line 36:
	\|department\|\| text		\|department\|\| text
	\|Name of the department as shown on the profile pages of the wiki		\|Name of the department as shown on the profile pages of the wiki
			\|-
			\|Style
			\|style
			\|large (default), compact
			\|
	\|-		\|-
	\|Alignment		\|Alignment
	\|align		\|align
	\|start, space-around, space-between		\|start, space-around, space-between, center (default)
	\|Alignment of the images in a row		\|Alignment of the images in a row
	([https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/justify-content Flex~~-Eigenschaft~~])		([https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/justify-content Flex property])
	\|}		\|}


	__NOTOC__		__NOTOC__

File:hw-profilegallery-templatedata.png

Margit.link-rodrigue — Tue, 12 May 2026 14:51:58 GMT

Redaktion uploaded File:hw-profilegallery-templatedata.png

New page

File:HW-Profilegallery.png

Margit.link-rodrigue — Tue, 12 May 2026 14:46:46 GMT

Redaktion uploaded File:HW-Profilegallery.png

New page

Manual:Extension/BlueSpiceWikiFarm

Margit.link-rodrigue — Tue, 12 May 2026 10:11:59 GMT

← Older revision		Revision as of 10:11, 12 May 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	{{DISPLAYTITLE:Wiki farm (overview)}}		{{DISPLAYTITLE:Wiki farm (overview)}}{{Featurepage\|featured=true\|featuredesc=Whitepaper: BlueSpice at Enterprise Scale (for use cases at the 10,000 sub-wiki scale).\|featurestart=05/12/2026}}{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=Whitepaper BlueSpice at Enterprise Scale EN.pdf}}
	{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=Whitepaper BlueSpice at Enterprise Scale EN.pdf}}


	'''Wiki farm''' is an architecture for BlueSpice wikis that can be used to centrally manage multiple wikis. Wikis can be created, cloned, deleted, and suspended. An administrative interface is provided for this purpose. The architecture also facilitates the maintenance of the wikis, since all wikis in the farm can be updated simultaneously. This functionality is provided by the extension [[Reference:BlueSpiceWikiFarm\|BlueSpiceWikiFarm.]]		'''Wiki farm''' is an architecture for BlueSpice wikis that can be used to centrally manage multiple wikis. Wikis can be created, cloned, deleted, and suspended. An administrative interface is provided for this purpose. The architecture also facilitates the maintenance of the wikis, since all wikis in the farm can be updated simultaneously. This functionality is provided by the extension [[Reference:BlueSpiceWikiFarm\|BlueSpiceWikiFarm.]]
	__TOC__		__TOC__

	==Farm administration==		==Farm administration==

Template:Whitepaper

Margit.link-rodrigue — Tue, 12 May 2026 10:03:33 GMT

← Older revision		Revision as of 10:03, 12 May 2026
Line 7:		Line 7:
	{{{description\|}}}		{{{description\|}}}
	</p>		</p>
	<i class="fas fa-download me-1"></i> [[~~File~~:{{{filename\|}}}\|Download PDF]]		<i class="fas fa-download me-1"></i> [[Media:{{{filename\|}}}\|Download PDF]]
	</div>		</div>
	</div>		</div>

Manual:Extension/BlueSpiceWikiFarm

Margit.link-rodrigue — Tue, 12 May 2026 10:03:13 GMT

← Older revision		Revision as of 10:03, 12 May 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Wiki farm (overview)}}		{{DISPLAYTITLE:Wiki farm (overview)}}
	{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=~~File:~~Whitepaper BlueSpice at Enterprise Scale EN.pdf}}		{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=Whitepaper BlueSpice at Enterprise Scale EN.pdf}}

Template:Whitepaper

Margit.link-rodrigue — Tue, 12 May 2026 10:03:02 GMT

← Older revision		Revision as of 10:03, 12 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	<div style="float:right; width:340px"><div class="d-flex justify-content-end my-4">{{#fas:}}		<div style="float:right; width:340px"><div class="d-flex justify-content-end my-4">{{#fas:}}
	<div class="card shadow-sm border-0" style="max-width: 340px;">		<div class="card shadow-sm border-0" style="max-width: 340px; margin-left:20px">
	<div class="card-header bg-light fw-semibold"><i class="fas fa-file-pdf text-danger me-2"></i>Whitepaper</div>		<div class="card-header bg-light fw-semibold"><i class="fas fa-file-pdf text-danger me-2"></i>Whitepaper</div>
	<div class="card-body">		<div class="card-body">

Manual:Extension/BlueSpiceWikiFarm

Margit.link-rodrigue — Tue, 12 May 2026 10:02:22 GMT

← Older revision		Revision as of 10:02, 12 May 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=File:Whitepaper BlueSpice at Enterprise Scale EN.pdf}}~~{{DISPLAYTITLE:~~Wiki farm ~~(overview)}}~~		{{DISPLAYTITLE:Wiki farm (overview)}}
			{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=File:Whitepaper BlueSpice at Enterprise Scale EN.pdf}}


			'''Wiki farm''' is an architecture for BlueSpice wikis that can be used to centrally manage multiple wikis. Wikis can be created, cloned, deleted, and suspended. An administrative interface is provided for this purpose. The architecture also facilitates the maintenance of the wikis, since all wikis in the farm can be updated simultaneously. This functionality is provided by the extension [[Reference:BlueSpiceWikiFarm\|BlueSpiceWikiFarm.]]
	__TOC__		__TOC__
	~~{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}~~
	'''Wiki farm''' is an architecture for BlueSpice wikis that can be used to centrally manage multiple wikis. Wikis can be created, cloned, deleted, and suspended. An administrative interface is provided for this purpose. The architecture also facilitates the maintenance of the wikis, since all wikis in the farm can be updated simultaneously. This functionality is provided by the extension [[Reference:BlueSpiceWikiFarm\|BlueSpiceWikiFarm.]]

	==Farm administration==		==Farm administration==

Template:Whitepaper

Margit.link-rodrigue — Tue, 12 May 2026 10:00:12 GMT

← Older revision		Revision as of 10:00, 12 May 2026
Line 1:		Line 1:
	<div class="d-flex justify-content-end my-4">{{#fas:}}		<div style="float:right; width:340px"><div class="d-flex justify-content-end my-4">{{#fas:}}
	<div class="card shadow-sm border-0" style="max-width: 340px;">		<div class="card shadow-sm border-0" style="max-width: 340px;">
	<div class="card-header bg-light fw-semibold"><i class="fas fa-file-pdf text-danger me-2"></i>Whitepaper</div>		<div class="card-header bg-light fw-semibold"><i class="fas fa-file-pdf text-danger me-2"></i>Whitepaper</div>
Line 10:		Line 10:
	</div>		</div>
	</div>		</div>
	</div>		</div></div>
	<noinclude>		<noinclude>
	<templatedata>		<templatedata>

Manual:Extension/BlueSpiceWikiFarm

Margit.link-rodrigue — Tue, 12 May 2026 09:57:11 GMT

← Older revision		Revision as of 09:57, 12 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	{{DISPLAYTITLE:Wiki farm (overview)}}		{{Whitepaper\|title=BlueSpice at Enterprise Scale\|description=Technical briefing for the Lead Architect and the DevOps/Operations team evaluating the operational implications of running BlueSpice Farm at a scale of approximately 10,000 sub-wikis.\|filename=File:Whitepaper BlueSpice at Enterprise Scale EN.pdf}}{{DISPLAYTITLE:Wiki farm (overview)}}
			__TOC__
	{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}		{{Messagebox\|boxtype=note\|Note text=''Wiki farm'' is not a standard feature of BlueSpice pro and needs to be acquired separately.}}
	'''Wiki farm''' is an architecture for BlueSpice wikis that can be used to centrally manage multiple wikis. Wikis can be created, cloned, deleted, and suspended. An administrative interface is provided for this purpose. The architecture also facilitates the maintenance of the wikis, since all wikis in the farm can be updated simultaneously. This functionality is provided by the extension [[Reference:BlueSpiceWikiFarm\|BlueSpiceWikiFarm.]]		'''Wiki farm''' is an architecture for BlueSpice wikis that can be used to centrally manage multiple wikis. Wikis can be created, cloned, deleted, and suspended. An administrative interface is provided for this purpose. The architecture also facilitates the maintenance of the wikis, since all wikis in the farm can be updated simultaneously. This functionality is provided by the extension [[Reference:BlueSpiceWikiFarm\|BlueSpiceWikiFarm.]]

File:Whitepaper BlueSpice at Enterprise Scale EN.pdf

Margit.link-rodrigue — Tue, 12 May 2026 09:55:20 GMT

Redaktion uploaded File:Whitepaper BlueSpice at Enterprise Scale EN.pdf

New page

Manual:Extension/BlueSpiceUserManager

Margit.link-rodrigue — Mon, 11 May 2026 14:39:32 GMT

← Older revision		Revision as of 14:39, 11 May 2026
Line 10:		Line 10:
	#'''Click''' the "+ Add"-button. This opens a dialog.[[File:Manual:Extension BlueSpiceUserManager 1743170419859.png\|center\|thumb\|300x300px\|Create a user account]]		#'''Click''' the "+ Add"-button. This opens a dialog.[[File:Manual:Extension BlueSpiceUserManager 1743170419859.png\|center\|thumb\|300x300px\|Create a user account]]
	#'''Enter''' the user information in the dialog:		#'''Enter''' the user information in the dialog:
	#*''Username:'' must be unique and cannot contain special characters		#*''Username:'' The username must be unique and cannot contain most special characters (including the <code>@</code>-Symbol). It is reasonable to include common special characters such as period (<code>.</code>) or standard hyphens for hyphenated names (<code>-</code>). Avoid en-dashes (<code>–</code>) or m-dashes (<code>—</code>). ''Password and Confirm password:'' The password for the new user.
	#*''Password and Confirm password:'' The password for the new user.		#*''Real name:'' The real name can be a duplicate of an existing user's real name and is optional.
	#*''Real name:'' can be a duplicate of an existing user's real name (optional)		#*''Email:'' The email address of the user (optional).
	#*''Email:'' The email address of the user (optional)		#*''Groups:'' a user can be assigned to multiple groups. If no group is selected, the user belongs to the default group ''user''.
	#*Groups: a user can be assigned to multiple groups. If no group is selected, the user belongs to the default group ''user''.
	#Click '''Save''' to create the user account.		#Click '''Save''' to create the user account.
	{{Messagebox\|boxtype=tip\|icon=\|Note text=If you do not want to provide the new user with a password that is known to you, you can create the user account via the page ''Special:CreateAccount'' instead. It is, however, not possible to assign a user group to the new account during account creation on that page.\|bgcolor=}}		{{Messagebox\|boxtype=tip\|icon=\|Note text=If you do not want to provide the new user with a password that is known to you, you can create the user account via the page ''Special:CreateAccount'' instead. It is, however, not possible to assign a user group to the new account during account creation on that page.\|bgcolor=}}

Reference:BlueSpiceUserManager

Margit.link-rodrigue — Mon, 11 May 2026 14:31:04 GMT

← Older revision		Revision as of 14:31, 11 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	{{BSExtensionInfo		{{BSExtensionInfo
	\|~~desc~~=~~Provides a visual interface for user administration~~		\|removed=No
	\|status=stable		\|status=stable
	\|developer=HalloWelt		\|developer=HalloWelt
	\|type=BlueSpice		\|type=BlueSpice
	\|edition=BlueSpice free, BlueSpice pro, BlueSpice farm, BlueSpice cloud		\|edition=BlueSpice free, BlueSpice pro, BlueSpice farm, BlueSpice cloud
	~~\|active=Yes~~
	\|compatible=BlueSpice		\|compatible=BlueSpice
	\|category=Administration		\|category=Administration
Line 12:		Line 11:
	The extension enables the following actions:		The extension enables the following actions:

	*create a new user		* create a new user
	*assign a user to a group		* assign a user to a group
	*change user data		* change user data
	*change the password		* change the password
	*delete users (multiple selections possible)		* delete users (multiple selections possible)
	*sort, filter, and export the user list		* sort, filter, and export the user list
			{{Textbox\|boxtype=important\|header=Userpage naming restriction:\|text=The at-symbol (@) cannot be used as part of a userpage name.\|icon=yes}}
			\|desc=Provides a visual interface for user administration
			\|active=Yes
	}}		}}
	{{wcagCheck		{{wcagCheck

Manual:Create Pages

Margit.link-rodrigue — Mon, 11 May 2026 14:29:16 GMT

← Older revision		Revision as of 14:29, 11 May 2026
Line 14:		Line 14:

	== Creating subpages ==		== Creating subpages ==
	~~<section end="training" />~~

	To create a subpage for the current page, select the ''New Subpage'' link from the ''New'' button menu.		To create a subpage for the current page, select the ''New Subpage'' link from the ''New'' button menu.
	[[File:Manual:~~creating~~ a ~~page -~~ subpage.png\|alt=~~Creating a subpage~~\|center\|thumb\|~~150x150px\|Creating a subpage~~]]		[[File:Manual:Create a subpage.png\|alt=Open menu of the new button with types of new pages listed\|center\|thumb\|The "new"-button menu]]


	~~The~~ subpage is then created as ''Current Page/Subpage (e.g''., Visual Editor/Tables). If a page has subpages, the path is displayed as breadcrumb navigation at the top of the page.		The subpage is then created as ''Current Page/Subpage (e.g''., Visual Editor/Tables). If a page has subpages, the path is displayed as breadcrumb navigation at the top of the page.
	==Alternative options==		==Alternative options==
	*'''Search field:''' Maybe information about your topic already exists. Before you create a new page, you can use the search to enter terms for your topic and check existing pages. If no suitable page exists, click on the redlink 'Create page ''[page name]''<nowiki/>' in the search results '''er address bar:''' You can also create a page directly from the address bar of your web browser. Simply exchange the current page name with a new one. Then, click enter to create the new page.		*'''Search field:''' Maybe information about your topic already exists. Before you create a new page, you can use the search to enter terms for your topic and check existing pages. If no suitable page exists, click on the redlink 'Create page ''[page name]''<nowiki/>' in the search results '''er address bar:''' You can also create a page directly from the address bar of your web browser. Simply exchange the current page name with a new one. Then, click enter to create the new page.
	*'''Form:''' In BlueSpice pro, the extension [[Reference:Page Forms\|Page Forms]] is available. It allows to create pages using a form.		*'''Form:''' In BlueSpice pro, the extension [[Reference:Page Forms\|Page Forms]] is available. It allows to create pages using a form.

	==~~Tipps~~==		==Tips==

	*'''Redirects:''' Do you have the impression that an article title is searched more often with a different synonym? Then create a new article with this name and [[Manual:~~Using~~ Redirects\|redirect]] the page to another page that contains the actual information.		*'''Redirects:''' Do you have the impression that an article title is searched more often with a different synonym? Then create a new article with this name and [[Manual:Redirects\|redirect]] the page to another page that contains the actual information.

	*'''Title choice:''' In a wiki, titles are very important. In wikis with many entries, authors may make references to pages that they deem important in the context of their entry. The page title should, therfore, clearly communicate its content. Single words are very good, but even short sentences like "why wikis work" can be useful names. In addition, meaningful page titles also help readers find their way around when they search for an entry.		*'''Title choice:''' In a wiki, titles are very important. In wikis with many entries, authors may make references to pages that they deem important in the context of their entry. The page title should, therfore, clearly communicate its content. Single words are very good, but even short sentences like "why wikis work" can be useful names. In addition, meaningful page titles also help readers find their way around when they search for an entry.

	*'''Spelling:''' When linking to an already existing page you should pay attention to ~~their~~ exact spelling. If you ~~e.g.~~ typing a <nowiki>[[hello world]]</nowiki> instead of <nowiki>[[Hello World]]</nowiki> ~~will~~ create a new page ~~as the links are spelled differently~~. Therefore, consider also capitalization and spaces. Only at the ~~beginning~~ of the ~~letter does it make no difference whether you write a small or capital letter.~~		*'''Spelling:''' When linking to an already existing page, you should pay attention to the exact spelling. If you are typing <code><nowiki>[[hello world]]</nowiki></code> instead of <code><nowiki>[[Hello World]]</nowiki></code> in source edit mode, you create a link to a new page. Therefore, consider also capitalization and spaces. Only the first letter of the page name is not case-sensitive.

	*'''Namespaces:''' If you want to create an article in a different namespace, the namespace must appear before article name~~. Example:<code><nowiki>[[namespace:article name]]</nowiki></code>.~~

	*'''Special characters:''' The following characters '''cannot''' be used in titles : <code> { } & ? < > \ </code>and <code>,</code>. For more information, see [[mediawikiwiki:Manual:Page_title\|mediawiki.org/wiki/Manual:Page_title]].

	*'''~~Subpages~~:''' ~~The character~~ <code>/<~~/code~~> ~~is used to create a~~ [[~~subpage~~]].		*'''Namespaces:''' If you want to create an article in a different namespace, the namespace must appear before the article name. Example:<code><nowiki>[[namespace:article name]]</nowiki></code>.

			*'''Special characters:''' The following characters '''cannot''' be used in titles : <code> { } & ? < > \ </code>and <code>,</code>. For more information, see [[mediawikiwiki:Manual:Page_title\|mediawiki.org/wiki/Manual:Page_title]].{{Textbox\|boxtype=important\|header=Userpage names:\|text=The at-symbol (@) cannot be used as part of a userpage name.\|icon=yes}}

	{{Box_Links-en \| Topic1 =[[Manual:Rename_and_move_pages\|~~Rename~~ and ~~move~~ pages]]\| Topic2 =[[Manual:Redirects\|~~Redirects~~]] \| Topic3 =[[Reference:BlueSpicePageTemplates\|Creating and Using Page Templates]] \| Topic4 = }}		*'''Subpages:''' The character <code>/</code> is used to create a [[Manual:Subpage\|subpage]].
			{{Box_Links-en \| Topic1 =[[Manual:Rename_and_move_pages\|Renaming and moving pages]]\| Topic2 =[[Manual:Redirects\|Working with redirects]] \| Topic3 =[[Reference:BlueSpicePageTemplates\|Creating and Using Page Templates]] \| Topic4 = }}

	[[en:{{FULLPAGENAME}}]]		[[en:{{FULLPAGENAME}}]]

Manual:Extension/Forms/5.1.8

Margit.link-rodrigue — Mon, 11 May 2026 09:12:06 GMT

Created page with "The '''Forms''' extension allows formatting a wiki page or a user dialog as a form. It is also used in conjunction with the Workflows extension where it provides input forms for workflow data. ==Introduction== To create a checklist as a form, for example, the following steps are necessary: # '''Create and save the checklist form''' via the ''Special:Form_editor'' special page. The form serves as a template for all checklists that are created wi..."

New page

The '''Forms''' extension allows formatting a wiki page or a user dialog as a form. It is also used in conjunction with the [[Reference:Workflows|Workflows]] extension where it provides input forms for workflow data.

==Introduction==
To create a checklist as a form, for example, the following steps are necessary:

# '''Create and save the checklist form''' via the ''Special:Form_editor'' special page. The form serves as a template for all checklists that are created with it.
# '''Create and save checklist instances''' via the special page ''Special:Create_form_instance''.

Optionally, the styling of the form can be adjusted.

As an example, we are creating a small checklist for an event where food-related hygiene information has to be tracked.
[[File:checklist-event-screenshot.png|alt=Event checklist example|center|thumb|550x550px|Event checklist example]]

==Create a checklist form==

# '''Define''' the main properties of the form:
## '''Open''' the ''Special:Form editor'' page.
## '''Enter''' a name for the new form, e.g. ''EventChecklistHygiene''. This name is used as a unique identifier for the database. Therefore, do not use any special characters (apart from the hyphen "-").
## '''Enter''' a title, e.g. Event Checklist. This is displayed as the display title instead of the form name if you activate the Display title checkbox. [[File:Manual:Checklist-form properties.png|alt=Form properties|center|thumb|750x750px|Form properties]]
# '''Add''' a form section:
##'''Select''' the ''Section label'' element under ''Form Elements > Other'' and, holding down the left mouse button, drag it into the interactive form editor field below.
## '''Click''' the section heading radio button. The editing dialog opens.
## '''Enter''' a field name. This is saved as a field ID in the database and should therefore not contain any special characters.
## '''Enter''' the title for the heading. This is used as the display title in the form.[[File:Manual:Checklist-form element-section label.png|alt=Create section label|center|thumb|750x750px|Create section label]]
# '''Create''' the form fields for the Event section. Here we add a text box as an example.
## '''Drag''' the ''Text'' element under the section heading while holding down the left mouse button.
## '''Click''' the text box radio button.
## '''Enter''' a name. This is used as the database ID for this field and should therefore not contain any special characters.
## '''Enter''' a label. This is displayed as the label for the text field.
## '''Add''' more form elements.
# '''Click''' Submit at the bottom of the page to save the form. The form is now stored in the main namespace as ''EventChecklistHygiene.form''. [[File:Manual:Checklist-view.png|alt=Saved form|center|thumb|650x650px|Saved form]]<br />To continue editing the form, switch to the editing mode of the page (1).

==Create a checklist instance==
To use the form, create your first checklist.

# '''Open''' the page ''Special:Edit_with_form''.
# '''Choose''' the form ''EventChecklistHygiene''.
# '''Fill out''' the form fields.
# '''Click''' ''Submit''.[[File:Manual:Checklist-create instance.png|alt=Create a checklist instance|center|thumb|650x650px|Create a checklist instance]]

The checklist is now saved in the wiki and can be edited further.
==Send email==
The form can also send an Email after being saved:
[[File:Manual:image.png|alt=Email target|center|thumb|650x650px|Email target]]

*'''Target type:''' Email
*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:
<syntaxhighlight lang="text">
$wgFormsTargetEMailRecipients = [

'Marketing' => "marketing@example.com",

'Administration' => 'WikiSysop'

];
</syntaxhighlight>

* '''Subject:''' Existing form fields can be used as variables here. The value is taken from the form.

* '''Content:''' As in the subject, existing form fields can also be used as variables here. The value is taken from the form.

[[mediawikiwiki:Help:Magic_words#Localisation|Localization messages]] in combination with form fields can also be used as subject or email body:<syntaxhighlight lang="text">
{{int:Mailsubject| {{{name}}}|{{{surname}}} }}
</syntaxhighlight>

==Adjust the styling==

===Common.css===
To style individual elements in the form, go to the styling tab in the options dialog. There, you can enter a css class name. The styling is then defined on the ''MediaWiki:Common.css'' page (admin rights are required).

To style the section heading:

#'''Open''' the styling tab in the options menu of the Event heading field.
#'''Add''' a new CSS class and enter a selector name (''CSS Classes'' field), e.g. ''frm-sectionhd''.[[File:Manual:forms-css-class-en.png|alt=Add a css class|center|thumb|650x650px|Add a css class]]
#'''Paste''' the following style declarations into the ''MediaWiki:Common.css'' page, e.g.:<syntaxhighlight lang="css">
border-bottom: 1px solid #a6a6a7; background:#f1f3f9; padding:6px;margin:30px 0;
</syntaxhighlight>[[File:Manual:forms-css-class-view-en.png|alt=Section label with customized styling|center|thumb|650x650px|Section label with customized styling]]

If you do not have permission to view this page, you can enter style information directly for each element in the form via inline styling.

===Inline styling===
Without access to ''MediaWiki:Common.css'', the style information can be entered directly in the form. However, with many recurring style declarations this is not efficient in contrast to the definition of CSS classes in ''MediaWiki:Common.css''.

As an example, let's apply the previous section heading example directly as inline styling. To do this, open the options menu of the ''ech-event'' form element again. Enter the following statement in the ''Styling'' field and save the change:<syntaxhighlight lang="css">
border-bottom: 1px solid #a6a6a7; background:#f1f3f9; padding:6px;margin:30px 0;
</syntaxhighlight>
[[File:Manual:forms-css-inlinestyling-en.png|alt=Inline styling of a form element|center|thumb|650x650px|Inline styling of a form element]]
{{translation}}

Template:Whitepaper

Margit.link-rodrigue — Mon, 11 May 2026 08:20:04 GMT

@@ Line 3: / Line 3: @@
 <div class="card-header bg-light fw-semibold"><i class="fas fa-file-pdf text-danger me-2"></i>Whitepaper</div>
 <div class="card-body">
-<h3 class="card-title fs-6" style="margin:0">GoBD-compliant Documentation</h3>
+<h3 class="card-title fs-6" style="margin:0">{{{title|}}}</h3>
 <p class="card-text small text-muted">
-Learn how to structure and version procedural documentation in a compliant way.
+{{{description|}}}
 </p>
-[[File:whitepaper-gobd.pdf|<i class="fas fas fa-download me-1"></i>Download PDF]]
+<i class="fas fa-download me-1"></i> [[File:{{{filename|}}}|Download PDF]]
 </div>
 </div>
 </div>