Skip to Content
Last modified by Agnease on 2026/05/25 12:55
From version 7.5
edited by Agnease
on 2026/05/25 12:53
Change comment: There is no comment for this version
To version 1.1
edited by Agnease
on 2026/05/12 12:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -XWiki Development and Integrations
1 +xwiki-development-integrations
Content
... ... @@ -1,322 +1,0 @@
1 -{{velocity}}
2 -#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 -{{html clean="false"}}
4 - ## PAGE HEADER
5 - <section class="hero hero-centered service-hero" aria-labelledby="hero-title">
6 - <div class="container hero-inner">
7 - <div class="hero-kicker">
8 - <i class="fa fa-cogs" aria-hidden="true"></i>
9 - XWiki development and integrations
10 - </div>
11 - <h1 id="hero-title">Custom XWiki applications, workflows and integrations</h1>
12 - <p class="lead">
13 - Extend XWiki beyond documentation with custom applications, structured data, workflows,
14 - dashboards, automation and integrations adapted to your organization.
15 - </p>
16 - <div class="hero-actions">
17 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a project</a>
18 - <a class="btn btn-secondary" href="#development-process">See the development approach</a>
19 - </div>
20 - </div>
21 - </section>
22 -
23 - ## WHY CUSTOM DEVELOPMENT
24 - #set ($developmentReasonItems = [{
25 - 'title': 'Structure your information',
26 - 'icon': 'database',
27 - 'content': 'Use XWiki classes, forms, templates and metadata to organize business information in a maintainable way.',
28 - 'items': [
29 - 'Custom data models',
30 - 'Structured forms and templates',
31 - 'Metadata-driven pages and views'
32 - ]
33 - },{
34 - 'title': 'Automate workflows',
35 - 'icon': 'random',
36 - 'content': 'Support approvals, reviews, notifications, status changes and controlled document lifecycles directly in XWiki.',
37 - 'items': [
38 - 'Review and approval workflows',
39 - 'Role-based actions and permissions',
40 - 'Notifications and task queues'
41 - ]
42 - },{
43 - 'title': 'Connect external systems',
44 - 'icon': 'plug',
45 - 'content': 'Integrate XWiki with authentication systems, APIs, AI tools, internal services and external platforms.',
46 - 'items': [
47 - 'REST API integrations',
48 - 'SSO, LDAP and identity systems',
49 - 'AI-assisted search and knowledge access'
50 - ]
51 - }])
52 -
53 - <section aria-labelledby="why-development-title">
54 - <div class="container">
55 - <h2 id="why-development-title">When XWiki needs to fit your business</h2>
56 -
57 - <p class="section-intro">
58 - XWiki is flexible enough to become much more than a documentation system. With the right structure,
59 - custom applications and integrations, it can support internal processes that would otherwise be handled
60 - through spreadsheets, scattered documents, manual approvals or disconnected tools.
61 - </p>
62 -
63 - <div class="pathways">
64 - #foreach ($entry in $developmentReasonItems)
65 - <article class="pathway-card">
66 - <div class="card-heading">
67 - <div class="pathway-icon">
68 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
69 - </div>
70 - <h3>$entry.title</h3>
71 - </div>
72 -
73 - <p>$entry.content</p>
74 -
75 - <ul>
76 - #foreach ($item in $entry.items)
77 - <li>$item</li>
78 - #end
79 - </ul>
80 - </article>
81 - #end
82 - </div>
83 - </div>
84 - </section>
85 -
86 - ## COMMON DEVELOPMENT NEEDS
87 - <section class="services" aria-labelledby="development-needs-title">
88 - <div class="container">
89 - <h2 id="development-needs-title">Common development needs</h2>
90 -
91 - <p class="section-intro">
92 - Custom XWiki development can range from small improvements to full business applications built on top of
93 - the platform. The focus is to keep the implementation useful, maintainable and aligned with XWiki conventions.
94 - This can also include AI-assisted knowledge access, where selected XWiki content is synchronized with external
95 - AI tools for question answering and discovery.
96 - </p>
97 -
98 - <div class="services-grid">
99 - <article class="service">
100 - <div class="service-icon" aria-hidden="true">
101 - <i class="fa fa-window-restore"></i>
102 - </div>
103 - <div class="service-body">
104 - <h4>Custom XWiki applications</h4>
105 - <p>
106 - Business-specific applications using XWiki classes, sheets, templates, UI extensions, scripts and components.
107 - </p>
108 - </div>
109 - </article>
110 -
111 - <article class="service">
112 - <div class="service-icon" aria-hidden="true">
113 - <i class="fa fa-check-square-o"></i>
114 - </div>
115 - <div class="service-body">
116 - <h4>Workflows and approvals</h4>
117 - <p>
118 - Review, approval, publishing, document control and status-based processes adapted to your internal rules.
119 - </p>
120 - </div>
121 - </article>
122 -
123 - <article class="service">
124 - <div class="service-icon" aria-hidden="true">
125 - <i class="fa fa-table"></i>
126 - </div>
127 - <div class="service-body">
128 - <h4>Dashboards and structured views</h4>
129 - <p>
130 - LiveData views, filters, reports, queues and dashboards that make structured XWiki information easier to use.
131 - </p>
132 - </div>
133 - </article>
134 -
135 - <article class="service">
136 - <div class="service-icon" aria-hidden="true">
137 - <i class="fa fa-file-pdf-o"></i>
138 - </div>
139 - <div class="service-body">
140 - <h4>PDF export and document outputs</h4>
141 - <p>
142 - Custom export templates, generated documents, controlled output formats and PDF-related workflow features.
143 - </p>
144 - </div>
145 - </article>
146 -
147 - <article class="service">
148 - <div class="service-icon" aria-hidden="true">
149 - <i class="fa fa-plug"></i>
150 - </div>
151 - <div class="service-body">
152 - <h4>External and AI integrations</h4>
153 - <p>
154 - Integration with REST APIs, authentication systems, internal services, automation tools,
155 - AI assistants or third-party platforms.
156 - </p>
157 - </div>
158 - </article>
159 -
160 - <article class="service">
161 - <div class="service-icon" aria-hidden="true">
162 - <i class="fa fa-code"></i>
163 - </div>
164 - <div class="service-body">
165 - <h4>Macros, components and extensions</h4>
166 - <p>
167 - Custom macros, Java components, Velocity scripts, UI extensions and packaged XWiki extensions.
168 - </p>
169 - </div>
170 - </article>
171 - </div>
172 - </div>
173 - </section>
174 -
175 - ## DEVELOPMENT APPROACH
176 - <section id="development-process" class="split-section" aria-labelledby="process-title">
177 - <div class="container">
178 - <div class="split-grid">
179 - <div class="split-copy">
180 - <h2 id="process-title">A practical development approach</h2>
181 -
182 - <p>
183 - XWiki development works best when the solution fits the platform instead of fighting it. The goal is
184 - to build features that are useful for business users while remaining understandable, maintainable and
185 - compatible with future upgrades.
186 - </p>
187 -
188 - <p>
189 - Development can start with a small improvement, a prototype or a full application. The important part is
190 - to clarify the business process, model the information correctly and choose the right technical level:
191 - configuration, scripting, extension development, external integration or AI-assisted knowledge access.
192 - </p>
193 - </div>
194 -
195 - <ol class="process-list">
196 - <li>
197 - <strong>Understand the business process</strong>
198 - Clarify users, roles, data, statuses, permissions, outputs, notifications and expected decisions.
199 - </li>
200 - <li>
201 - <strong>Design the XWiki model</strong>
202 - Define the right structure using pages, spaces, XClasses, templates, sheets, rights and views.
203 - </li>
204 - <li>
205 - <strong>Choose the implementation level</strong>
206 - Decide whether the feature should be built with configuration, scripting, Java components or a packaged extension.
207 - </li>
208 - <li>
209 - <strong>Build and validate iteratively</strong>
210 - Implement the feature in manageable steps and validate it with real usage scenarios.
211 - </li>
212 - <li>
213 - <strong>Document and prepare for maintenance</strong>
214 - Leave clear notes about configuration, custom code, assumptions and future improvement areas.
215 - </li>
216 - </ol>
217 - </div>
218 - </div>
219 - </section>
220 -
221 - ## EXAMPLE SOLUTIONS
222 - <section aria-labelledby="examples-title">
223 - <div class="container">
224 - <h2 id="examples-title">Example solutions</h2>
225 -
226 - <p class="section-intro">
227 - The same XWiki foundation can support different internal tools, depending on how your organization manages
228 - knowledge, documents, processes and collaboration.
229 - </p>
230 -
231 - <div class="widgets">
232 - <article class="widget">
233 - <div class="icon" aria-hidden="true">
234 - <i class="fa fa-file-text-o"></i>
235 - <h4>SOP and document control</h4>
236 - </div>
237 - <p>
238 - Controlled documents with review, approval, publishing, revision tracking, PDF export and lifecycle management.
239 - </p>
240 - </article>
241 -
242 - <article class="widget">
243 - <div class="icon" aria-hidden="true">
244 - <i class="fa fa-tasks"></i>
245 - <h4>Internal workflow applications</h4>
246 - </div>
247 - <p>
248 - Lightweight business applications for requests, approvals, registers, task queues and process tracking.
249 - </p>
250 - </article>
251 -
252 - <article class="widget">
253 - <div class="icon" aria-hidden="true">
254 - <i class="fa fa-sitemap"></i>
255 - <h4>Knowledge base structures</h4>
256 - </div>
257 - <p>
258 - Templates, metadata, taxonomies, related articles and navigation structures for large knowledge bases.
259 - </p>
260 - </article>
261 -
262 - <article class="widget">
263 - <div class="icon" aria-hidden="true">
264 - <i class="fa fa-comments-o"></i>
265 - <h4>AI-assisted knowledge access</h4>
266 - </div>
267 - <p>
268 - Integrations that feed selected XWiki content into AI knowledge tools, helping users ask questions
269 - and retrieve relevant information while XWiki remains the maintained source of truth.
270 - </p>
271 - </article>
272 - </div>
273 - </div>
274 - </section>
275 -
276 - ## RELATED SERVICES
277 - <section class="resource-strip" aria-labelledby="related-title">
278 - <div class="container">
279 - <h2 id="related-title">Related XWiki services</h2>
280 -
281 - <p class="section-intro">
282 - Development work often connects with support, upgrades, authentication and long-term maintainability.
283 - </p>
284 -
285 - <div class="resource-grid">
286 - <article class="resource-card">
287 - <h4>XWiki Support &amp; Maintenance</h4>
288 - <p>
289 - Ongoing technical care for production environments, including troubleshooting, maintenance planning and recovery support.
290 - </p>
291 - <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a>
292 - </article>
293 -
294 - <article class="resource-card">
295 - <h4>XWiki Upgrade Services</h4>
296 - <p>
297 - Safe LTS upgrades with staging validation, compatibility checks, rollback planning and post-upgrade verification.
298 - </p>
299 - <a href="$xwiki.getURL('services.xwiki-upgrades')">View upgrade services</a>
300 - </article>
301 - </div>
302 - </div>
303 - </section>
304 -
305 - ## CTA
306 - <section class="cta-section" aria-labelledby="cta-title">
307 - <div class="container">
308 - <div class="cta-panel">
309 - <h2 id="cta-title">Need to build something in XWiki?</h2>
310 -
311 - <p>
312 - Send a short description of the process, workflow, integration or application you want to create.
313 - A few details about users, data and expected outcomes are enough to start the conversation.
314 - </p>
315 -
316 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a project</a>
317 - </div>
318 - </div>
319 - </section>
320 -
321 -{{/html}}
322 -{{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,1 +1,0 @@
1 -Custom XWiki development services for applications, workflows, dashboards, macros, automation, APIs, integrations and maintainable platform extensions.
metaTitle
... ... @@ -1,1 +1,0 @@
1 -XWiki Custom Development and Integrations | Agnease