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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -xwiki-development-integrations
1 +XWiki Development and Integrations
Content
... ... @@ -1,7 +1,6 @@
1 1  {{velocity}}
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 3  {{html clean="false"}}
4 -
5 5   ## PAGE HEADER
6 6   <section class="hero hero-centered service-hero" aria-labelledby="hero-title">
7 7   <div class="container hero-inner">
... ... @@ -9,19 +9,11 @@
9 9   <i class="fa fa-cogs" aria-hidden="true"></i>
10 10   XWiki development and integrations
11 11   </div>
12 -
13 13   <h1 id="hero-title">Custom XWiki applications, workflows and integrations</h1>
14 -
15 15   <p class="lead">
16 - Extend XWiki beyond documentation with custom applications, structured data, workflows, dashboards,
17 - automation and integrations adapted to your organization.
13 + Extend XWiki beyond documentation with custom applications, structured data, workflows,
14 + dashboards, automation and integrations adapted to your organization.
18 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 25   <div class="hero-actions">
26 26   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a project</a>
27 27   <a class="btn btn-secondary" href="#development-process">See the development approach</a>
... ... @@ -30,6 +30,35 @@
30 30   </section>
31 31  
32 32   ## 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 +
33 33   <section aria-labelledby="why-development-title">
34 34   <div class="container">
35 35   <h2 id="why-development-title">When XWiki needs to fit your business</h2>
... ... @@ -41,50 +41,24 @@
41 41   </p>
42 42  
43 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>
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>
58 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 + <p>$entry.content</p>
73 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, internal tools and external platforms.
81 - </p>
82 - <ul>
83 - <li>REST API integrations</li>
84 - <li>SSO, LDAP and identity systems</li>
85 - <li>Automation around existing processes</li>
86 - </ul>
87 - </article>
75 + <ul>
76 + #foreach ($item in $entry.items)
77 + <li>$item</li>
78 + #end
79 + </ul>
80 + </article>
81 + #end
88 88   </div>
89 89   </div>
90 90   </section>
... ... @@ -97,6 +97,8 @@
97 97   <p class="section-intro">
98 98   Custom XWiki development can range from small improvements to full business applications built on top of
99 99   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.
100 100   </p>
101 101  
102 102   <div class="services-grid">
... ... @@ -153,9 +153,10 @@
153 153   <i class="fa fa-plug"></i>
154 154   </div>
155 155   <div class="service-body">
156 - <h4>External integrations</h4>
152 + <h4>External and AI integrations</h4>
157 157   <p>
158 - Integration with REST APIs, authentication systems, internal services, automation tools or third-party platforms.
154 + Integration with REST APIs, authentication systems, internal services, automation tools,
155 + AI assistants or third-party platforms.
159 159   </p>
160 160   </div>
161 161   </article>
... ... @@ -191,7 +191,7 @@
191 191   <p>
192 192   Development can start with a small improvement, a prototype or a full application. The important part is
193 193   to clarify the business process, model the information correctly and choose the right technical level:
194 - configuration, scripting, extension development or external integration.
191 + configuration, scripting, extension development, external integration or AI-assisted knowledge access.
195 195   </p>
196 196   </div>
197 197  
... ... @@ -255,7 +255,7 @@
255 255   <article class="widget">
256 256   <div class="icon" aria-hidden="true">
257 257   <i class="fa fa-sitemap"></i>
258 - <h4>Knowledge structures</h4>
255 + <h4>Knowledge base structures</h4>
259 259   </div>
260 260   <p>
261 261   Templates, metadata, taxonomies, related articles and navigation structures for large knowledge bases.
... ... @@ -264,11 +264,12 @@
264 264  
265 265   <article class="widget">
266 266   <div class="icon" aria-hidden="true">
267 - <i class="fa fa-exchange"></i>
268 - <h4>Connected platforms</h4>
264 + <i class="fa fa-comments-o"></i>
265 + <h4>AI-assisted knowledge access</h4>
269 269   </div>
270 270   <p>
271 - Integrations with authentication, APIs, external tools, notification systems and operational processes.
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.
272 272   </p>
273 273   </article>
274 274   </div>
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,0 +1,1 @@
1 +Custom XWiki development services for applications, workflows, dashboards, macros, automation, APIs, integrations and maintainable platform extensions.
metaTitle
... ... @@ -1,0 +1,1 @@
1 +XWiki Custom Development and Integrations | Agnease