Skip to Content

Changes for page Public Web Site

Last modified by Agnease on 2026/05/30 16:24
From version 12.21
edited by Agnease
on 2026/05/23 18:38
Change comment: There is no comment for this version
To version 12.16
edited by Agnease
on 2026/05/22 10:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,18 +5,18 @@
5 5  
6 6   <section class="hero hero-centered" aria-labelledby="hero-title">
7 7   <div class="container hero-inner">
8 - <h1 id="hero-title">Independent XWiki consulting and engineering</h1>
8 + <h1 id="hero-title">Professional XWiki engineering and support</h1>
9 9  
10 10   <p class="lead">
11 - Agnease helps organizations upgrade, maintain, secure and extend production XWiki platforms with practical
12 - engineering support, custom development, integrations and long-term care.
11 + Agnease helps organizations upgrade, maintain, secure and extend XWiki so production platforms stay stable,
12 + up-to-date and adapted to real business processes.
13 13   </p>
14 14  
15 15   <ul class="benefits">
16 - <li>XWiki LTS upgrades</li>
17 - <li>Maintenance and support</li>
18 - <li>Custom XWiki development</li>
19 - <li>Migrations and integrations</li>
16 + <li>Safe LTS upgrades</li>
17 + <li>Support and recovery</li>
18 + <li>Custom XWiki applications</li>
19 + <li>Integrations and migrations</li>
20 20   </ul>
21 21  
22 22   <div class="hero-actions">
... ... @@ -39,11 +39,11 @@
39 39  
40 40   <section aria-labelledby="platform-title">
41 41   <div class="container">
42 - <h2 id="platform-title">XWiki support for production knowledge platforms</h2>
42 + <h2 id="platform-title">When XWiki becomes business-critical, it needs professional care</h2>
43 43   <p class="section-intro">
44 - XWiki often grows from a documentation space into a business-critical knowledge platform.
45 - When it supports intranets, procedures, workflows, audits or integrations, upgrades, security,
46 - permissions and maintainability need structured technical care.
44 + Many organizations start with XWiki as a documentation platform. Over time, it becomes a knowledge base,
45 + intranet, SOP portal, workflow system, audit trail or integration hub. At that point, upgrades, security,
46 + performance, permissions and maintainability are no longer optional technical details.
47 47   </p>
48 48  
49 49   <div class="pathways">
... ... @@ -51,14 +51,14 @@
51 51   <div class="pathway-icon">
52 52   <i class="fa fa-refresh" aria-hidden="true"></i>
53 53   </div>
54 - <h3>Upgrade XWiki safely</h3>
54 + <h3>Keep XWiki current</h3>
55 55   <p>
56 - Plan and execute XWiki LTS upgrades with compatibility checks, staging validation and rollback planning.
56 + Plan and execute safe upgrades to supported XWiki versions, with compatibility checks and rollback planning.
57 57   </p>
58 58   <ul>
59 59   <li>LTS upgrade planning</li>
60 60   <li>Extension and custom code review</li>
61 - <li>Staging and production validation</li>
61 + <li>Production rollout validation</li>
62 62   </ul>
63 63   <p class="card-link">
64 64   <a href="$xwiki.getURL('services.xwiki-upgrades')">View upgrade services</a>
... ... @@ -69,14 +69,14 @@
69 69   <div class="pathway-icon">
70 70   <i class="fa fa-life-ring" aria-hidden="true"></i>
71 71   </div>
72 - <h3>Maintain XWiki reliably</h3>
72 + <h3>Keep XWiki reliable</h3>
73 73   <p>
74 - Keep production XWiki instances stable with troubleshooting, maintenance planning, recovery support and security-aware care.
74 + Get long-term technical care for instances that need to stay stable, secure and recoverable.
75 75   </p>
76 76   <ul>
77 77   <li>Troubleshooting and recovery</li>
78 78   <li>Performance and log analysis</li>
79 - <li>Upgrade and maintenance planning</li>
79 + <li>Security-aware maintenance</li>
80 80   </ul>
81 81   <p class="card-link">
82 82   <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a>
XWiki.StyleSheetExtension[0]
code
... ... @@ -842,7 +842,6 @@
842 842   gap: 42px;
843 843   max-width: 1080px;
844 844   margin: 0 auto;
845 - padding-top: 28px;
846 846   align-items: start;
847 847  }
848 848  
... ... @@ -962,7 +962,6 @@
962 962  @media (max-width: 900px) {
963 963   .resource-layout {
964 964   grid-template-columns: 1fr;
965 - padding-top: 22px;
966 966   }
967 967  
968 968   .resource-sidebar {
... ... @@ -1127,13 +1127,6 @@
1127 1127   box-shadow: @shadow-sm;
1128 1128   padding: 22px;
1129 1129  
1130 - .feature-heading {
1131 - display: flex;
1132 - align-items: center;
1133 - gap: 14px;
1134 - margin-bottom: 14px;
1135 - }
1136 -
1137 1137   .feature-icon {
1138 1138   width: 46px;
1139 1139   height: 46px;
... ... @@ -1143,12 +1143,12 @@
1143 1143   display: flex;
1144 1144   align-items: center;
1145 1145   justify-content: center;
1137 + margin-bottom: 14px;
1146 1146   font-size: 18px;
1147 - flex-shrink: 0;
1148 1148   }
1149 1149  
1150 1150   h3 {
1151 - margin: 0;
1142 + margin: 0 0 8px;
1152 1152   color: @text;
1153 1153   font-size: 18px;
1154 1154   line-height: 1.25;