Skip to Content
Last modified by Alex Cotiugă on 2026/05/12 12:59
From version 1.1
edited by Alex Cotiugă
on 2026/05/12 12:47
Change comment: There is no comment for this version
To version 1.10
edited by Alex Cotiugă
on 2026/05/12 12:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,0 +1,328 @@
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>
80 + Integrate XWiki with authentication systems, APIs, AI tools, internal services and external platforms.
81 + </p>
82 + <ul>
83 + <li>REST API integrations</li>
84 + <li>SSO, LDAP and identity systems</li>
85 + <li>AI-assisted search and knowledge access</li>
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 + This can also include AI-assisted knowledge access, where selected XWiki content is synchronized with external
101 + AI tools for question answering and discovery.
102 + </p>
103 +
104 + <div class="services-grid">
105 + <article class="service">
106 + <div class="service-icon" aria-hidden="true">
107 + <i class="fa fa-window-restore"></i>
108 + </div>
109 + <div class="service-body">
110 + <h4>Custom XWiki applications</h4>
111 + <p>
112 + Business-specific applications using XWiki classes, sheets, templates, UI extensions, scripts and components.
113 + </p>
114 + </div>
115 + </article>
116 +
117 + <article class="service">
118 + <div class="service-icon" aria-hidden="true">
119 + <i class="fa fa-check-square-o"></i>
120 + </div>
121 + <div class="service-body">
122 + <h4>Workflows and approvals</h4>
123 + <p>
124 + Review, approval, publishing, document control and status-based processes adapted to your internal rules.
125 + </p>
126 + </div>
127 + </article>
128 +
129 + <article class="service">
130 + <div class="service-icon" aria-hidden="true">
131 + <i class="fa fa-table"></i>
132 + </div>
133 + <div class="service-body">
134 + <h4>Dashboards and structured views</h4>
135 + <p>
136 + LiveData views, filters, reports, queues and dashboards that make structured XWiki information easier to use.
137 + </p>
138 + </div>
139 + </article>
140 +
141 + <article class="service">
142 + <div class="service-icon" aria-hidden="true">
143 + <i class="fa fa-file-pdf-o"></i>
144 + </div>
145 + <div class="service-body">
146 + <h4>PDF export and document outputs</h4>
147 + <p>
148 + Custom export templates, generated documents, controlled output formats and PDF-related workflow features.
149 + </p>
150 + </div>
151 + </article>
152 +
153 + <article class="service">
154 + <div class="service-icon" aria-hidden="true">
155 + <i class="fa fa-plug"></i>
156 + </div>
157 + <div class="service-body">
158 + <h4>External and AI integrations</h4>
159 + <p>
160 + Integration with REST APIs, authentication systems, internal services, automation tools,
161 + AI assistants or third-party platforms.
162 + </p>
163 + </div>
164 + </article>
165 +
166 + <article class="service">
167 + <div class="service-icon" aria-hidden="true">
168 + <i class="fa fa-code"></i>
169 + </div>
170 + <div class="service-body">
171 + <h4>Macros, components and extensions</h4>
172 + <p>
173 + Custom macros, Java components, Velocity scripts, UI extensions and packaged XWiki extensions.
174 + </p>
175 + </div>
176 + </article>
177 + </div>
178 + </div>
179 + </section>
180 +
181 + ## DEVELOPMENT APPROACH
182 + <section id="development-process" class="split-section" aria-labelledby="process-title">
183 + <div class="container">
184 + <div class="split-grid">
185 + <div class="split-copy">
186 + <h2 id="process-title">A practical development approach</h2>
187 +
188 + <p>
189 + XWiki development works best when the solution fits the platform instead of fighting it. The goal is
190 + to build features that are useful for business users while remaining understandable, maintainable and
191 + compatible with future upgrades.
192 + </p>
193 +
194 + <p>
195 + Development can start with a small improvement, a prototype or a full application. The important part is
196 + to clarify the business process, model the information correctly and choose the right technical level:
197 + configuration, scripting, extension development, external integration or AI-assisted knowledge access.
198 + </p>
199 + </div>
200 +
201 + <ol class="process-list">
202 + <li>
203 + <strong>Understand the business process</strong>
204 + Clarify users, roles, data, statuses, permissions, outputs, notifications and expected decisions.
205 + </li>
206 + <li>
207 + <strong>Design the XWiki model</strong>
208 + Define the right structure using pages, spaces, XClasses, templates, sheets, rights and views.
209 + </li>
210 + <li>
211 + <strong>Choose the implementation level</strong>
212 + Decide whether the feature should be built with configuration, scripting, Java components or a packaged extension.
213 + </li>
214 + <li>
215 + <strong>Build and validate iteratively</strong>
216 + Implement the feature in manageable steps and validate it with real usage scenarios.
217 + </li>
218 + <li>
219 + <strong>Document and prepare for maintenance</strong>
220 + Leave clear notes about configuration, custom code, assumptions and future improvement areas.
221 + </li>
222 + </ol>
223 + </div>
224 + </div>
225 + </section>
226 +
227 + ## EXAMPLE SOLUTIONS
228 + <section aria-labelledby="examples-title">
229 + <div class="container">
230 + <h2 id="examples-title">Example solutions</h2>
231 +
232 + <p class="section-intro">
233 + The same XWiki foundation can support different internal tools, depending on how your organization manages
234 + knowledge, documents, processes and collaboration.
235 + </p>
236 +
237 + <div class="widgets">
238 + <article class="widget">
239 + <div class="icon" aria-hidden="true">
240 + <i class="fa fa-file-text-o"></i>
241 + <h4>SOP and document control</h4>
242 + </div>
243 + <p>
244 + Controlled documents with review, approval, publishing, revision tracking, PDF export and lifecycle management.
245 + </p>
246 + </article>
247 +
248 + <article class="widget">
249 + <div class="icon" aria-hidden="true">
250 + <i class="fa fa-tasks"></i>
251 + <h4>Internal workflow applications</h4>
252 + </div>
253 + <p>
254 + Lightweight business applications for requests, approvals, registers, task queues and process tracking.
255 + </p>
256 + </article>
257 +
258 + <article class="widget">
259 + <div class="icon" aria-hidden="true">
260 + <i class="fa fa-sitemap"></i>
261 + <h4>Knowledge base structures</h4>
262 + </div>
263 + <p>
264 + Templates, metadata, taxonomies, related articles and navigation structures for large knowledge bases.
265 + </p>
266 + </article>
267 +
268 + <article class="widget">
269 + <div class="icon" aria-hidden="true">
270 + <i class="fa fa-comments-o"></i>
271 + <h4>AI-assisted knowledge access</h4>
272 + </div>
273 + <p>
274 + Integrations that feed selected XWiki content into AI knowledge tools, helping users ask questions
275 + and retrieve relevant information while XWiki remains the maintained source of truth.
276 + </p>
277 + </article>
278 + </div>
279 + </div>
280 + </section>
281 +
282 + ## RELATED SERVICES
283 + <section class="resource-strip" aria-labelledby="related-title">
284 + <div class="container">
285 + <h2 id="related-title">Related XWiki services</h2>
286 +
287 + <p class="section-intro">
288 + Development work often connects with support, upgrades, authentication and long-term maintainability.
289 + </p>
290 +
291 + <div class="resource-grid">
292 + <article class="resource-card">
293 + <h4>XWiki Support &amp; Maintenance</h4>
294 + <p>
295 + Ongoing technical care for production environments, including troubleshooting, maintenance planning and recovery support.
296 + </p>
297 + <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a>
298 + </article>
299 +
300 + <article class="resource-card">
301 + <h4>XWiki Upgrade Services</h4>
302 + <p>
303 + Safe LTS upgrades with staging validation, compatibility checks, rollback planning and post-upgrade verification.
304 + </p>
305 + <a href="$xwiki.getURL('services.xwiki-upgrades')">View upgrade services</a>
306 + </article>
307 + </div>
308 + </div>
309 + </section>
310 +
311 + ## CTA
312 + <section class="cta-section" aria-labelledby="cta-title">
313 + <div class="container">
314 + <div class="cta-panel">
315 + <h2 id="cta-title">Need to build something in XWiki?</h2>
316 +
317 + <p>
318 + Send a short description of the process, workflow, integration or application you want to create.
319 + A few details about users, data and expected outcomes are enough to start the conversation.
320 + </p>
321 +
322 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a project</a>
323 + </div>
324 + </div>
325 + </section>
326 +
327 +{{/html}}
328 +{{/velocity}}