Skip to Content

Wiki source code of xwiki-development-integrations

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