Skip to Content

Changes for page Public Web Site

Last modified by Agnease on 2026/05/30 16:24
From version 12.2
edited by Agnease
on 2026/05/22 10:23
Change comment: There is no comment for this version
To version 12.24
edited by Agnease
on 2026/05/23 18:45
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">Professional XWiki engineering and support</h1>
8 + <h1 id="hero-title">Independent XWiki consulting and engineering</h1>
9 9  
10 10   <p class="lead">
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.
11 + Agnease helps organizations upgrade, maintain, secure and extend production XWiki platforms with practical
12 + engineering support, custom development, integrations and long-term care.
13 13   </p>
14 14  
15 15   <ul class="benefits">
16 - <li>Safe LTS upgrades</li>
17 - <li>Support and recovery</li>
18 - <li>Custom XWiki applications</li>
19 - <li>Integrations and migrations</li>
16 + <li>XWiki LTS upgrades</li>
17 + <li>Maintenance and support</li>
18 + <li>Custom XWiki development</li>
19 + <li>Migrations and integrations</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">When XWiki becomes business-critical, it needs professional care</h2>
42 + <h2 id="platform-title">XWiki support for production knowledge platforms</h2>
43 43   <p class="section-intro">
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.
44 + XWiki often grows from a documentation space into a business-critical knowledge platform.
45 + When it supports intranets, procedures, workflows, audits or integrations, it needs structured technical care
46 + for upgrades, security, permissions and maintainability.
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>Keep XWiki current</h3>
54 + <h3>Upgrade XWiki safely</h3>
55 55   <p>
56 - Plan and execute safe upgrades to supported XWiki versions, with compatibility checks and rollback planning.
56 + Plan and execute XWiki LTS upgrades with compatibility checks, staging validation 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>Production rollout validation</li>
61 + <li>Staging and production 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>Keep XWiki reliable</h3>
72 + <h3>Maintain XWiki reliably</h3>
73 73   <p>
74 - Get long-term technical care for instances that need to stay stable, secure and recoverable.
74 + Keep production XWiki instances stable with troubleshooting, maintenance planning, recovery support and security-aware care.
75 75   </p>
76 76   <ul>
77 77   <li>Troubleshooting and recovery</li>
78 78   <li>Performance and log analysis</li>
79 - <li>Security-aware maintenance</li>
79 + <li>Upgrade and maintenance planning</li>
80 80   </ul>
81 81   <p class="card-link">
82 82   <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a>
... ... @@ -87,14 +87,14 @@
87 87   <div class="pathway-icon">
88 88   <i class="fa fa-cogs" aria-hidden="true"></i>
89 89   </div>
90 - <h3>Adapt XWiki to your business</h3>
90 + <h3>Extend XWiki for your processes</h3>
91 91   <p>
92 - Build workflows, custom applications, dashboards, integrations and automation around your processes.
92 + Build custom XWiki applications, workflows, dashboards and integrations around real business needs.
93 93   </p>
94 94   <ul>
95 95   <li>Custom XWiki applications</li>
96 96   <li>Workflows and approvals</li>
97 - <li>SSO, LDAP, APIs and integrations</li>
97 + <li>APIs, SSO, LDAP and integrations</li>
98 98   </ul>
99 99   <p class="card-link">
100 100   <a href="$xwiki.getURL('services.xwiki-development-integrations')">View development services</a>
... ... @@ -108,29 +108,29 @@
108 108   <div class="container">
109 109   <div class="split-grid">
110 110   <div class="split-copy">
111 - <h2 id="why-title">Why choose Agnease</h2>
111 + <h2 id="why-title">Why work with an XWiki specialist</h2>
112 112   <p>
113 - Agnease brings more than 11 years of hands-on XWiki expertise to organizations that need reliable
114 - knowledge platforms, secure upgrades, custom applications, integrations, migrations and long-term support.
113 + XWiki projects often involve more than pages. Production platforms may include custom code,
114 + extensions, authentication, permissions, workflows, integrations and business-critical content.
115 115   </p>
116 116   <p>
117 - The approach is practical and engineering-focused: understand the current system, reduce risk,
118 - document the work and leave your XWiki easier to maintain.
117 + Agnease brings 11+ years of hands-on XWiki experience to help reduce risk, deliver practical improvements
118 + and leave the platform easier to maintain after the work is complete.
119 119   </p>
120 120   </div>
121 121  
122 122   <ol class="process-list">
123 123   <li>
124 - <strong>Review the current situation</strong>
125 - Version, extensions, infrastructure, authentication, custom code and business-critical features.
124 + <strong>Review the XWiki environment</strong>
125 + Version, extensions, infrastructure, authentication, permissions, custom code and critical features.
126 126   </li>
127 127   <li>
128 - <strong>Define a safe path forward</strong>
129 - Clear scope, expected effort, risks, rollback options and recommended next steps.
128 + <strong>Define the safest next steps</strong>
129 + Scope, risks, dependencies, effort, rollback options and validation requirements.
130 130   </li>
131 131   <li>
132 - <strong>Deliver and document the work</strong>
133 - Practical implementation, validation and documentation for future maintenance.
132 + <strong>Implement, validate and document</strong>
133 + Controlled changes, testing, production validation and notes for future maintenance.
134 134   </li>
135 135   </ol>
136 136   </div>
... ... @@ -139,9 +139,9 @@
139 139  
140 140   <section class="resource-strip homepage-resource-strip" aria-labelledby="resources-title">
141 141   <div class="container">
142 - <h2 id="resources-title">Useful XWiki resources</h2>
142 + <h2 id="resources-title">XWiki resources for safer long-term maintenance</h2>
143 143   <p class="section-intro">
144 - Practical guidance for organizations running XWiki in production.
144 + Practical articles about XWiki upgrades, customization and production platform care.
145 145   </p>
146 146  
147 147   <div class="resource-grid">
... ... @@ -148,17 +148,17 @@
148 148   <article class="resource-card">
149 149   <h4>Why upgrade your XWiki instance?</h4>
150 150   <p>
151 - A business-focused explanation of why regular LTS upgrades reduce security, compatibility and maintenance risk.
151 + Learn why regular XWiki upgrades reduce security exposure, compatibility issues and long-term maintenance risk.
152 152   </p>
153 - <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">Read the resource</a>
153 + <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">Read the article</a>
154 154   </article>
155 155  
156 156   <article class="resource-card">
157 157   <h4>XWiki upgrade services</h4>
158 158   <p>
159 - How Agnease approaches safe XWiki upgrades for real production environments with customizations and integrations.
159 + See how XWiki upgrades can be planned, tested and validated for production instances with customizations and integrations.
160 160   </p>
161 - <a href="$xwiki.getURL('services.xwiki-upgrades')">View the service</a>
161 + <a href="$xwiki.getURL('services.xwiki-upgrades')">View upgrade services</a>
162 162   </article>
163 163   </div>
164 164   </div>
... ... @@ -167,10 +167,10 @@
167 167   <section class="cta-section" aria-labelledby="contact-title">
168 168   <div class="container">
169 169   <div class="cta-panel">
170 - <h2 id="contact-title">Need help with XWiki?</h2>
170 + <h2 id="contact-title">Need XWiki consulting or support?</h2>
171 171   <p>
172 - Send your current XWiki version, the problem you are facing, or the type of project you want to build.
173 - A short description is enough to start the conversation.
172 + Send your current XWiki version, the issue you are facing, or the type of project you want to build.
173 + A short description is enough to define practical next steps.
174 174   </p>
175 175   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
176 176   </div>
XWiki.StyleSheetExtension[0]
code
... ... @@ -842,6 +842,7 @@
842 842   gap: 42px;
843 843   max-width: 1080px;
844 844   margin: 0 auto;
845 + padding-top: 28px;
845 845   align-items: start;
846 846  }
847 847  
... ... @@ -961,6 +961,7 @@
961 961  @media (max-width: 900px) {
962 962   .resource-layout {
963 963   grid-template-columns: 1fr;
965 + padding-top: 22px;
964 964   }
965 965  
966 966   .resource-sidebar {
... ... @@ -1125,6 +1125,13 @@
1125 1125   box-shadow: @shadow-sm;
1126 1126   padding: 22px;
1127 1127  
1130 + .feature-heading {
1131 + display: flex;
1132 + align-items: center;
1133 + gap: 14px;
1134 + margin-bottom: 14px;
1135 + }
1136 +
1128 1128   .feature-icon {
1129 1129   width: 46px;
1130 1130   height: 46px;
... ... @@ -1134,12 +1134,12 @@
1134 1134   display: flex;
1135 1135   align-items: center;
1136 1136   justify-content: center;
1137 - margin-bottom: 14px;
1138 1138   font-size: 18px;
1147 + flex-shrink: 0;
1139 1139   }
1140 1140  
1141 1141   h3 {
1142 - margin: 0 0 8px;
1151 + margin: 0;
1143 1143   color: @text;
1144 1144   font-size: 18px;
1145 1145   line-height: 1.25;
... ... @@ -1240,27 +1240,5 @@
1240 1240  @media (max-width: 767px) {
1241 1241   .resources-index-page {
1242 1242   padding: @section-padding-mobile;
1243 -
1244 - .resources-intro {
1245 - text-align: left;
1246 - margin-bottom: 24px;
1247 - }
1248 -
1249 - .resources-grid {
1250 - grid-template-columns: 1fr;
1251 - gap: 18px;
1252 - }
1253 -
1254 - .resource-card {
1255 - padding: 20px;
1256 - }
1257 -
1258 - .resource-card h2 {
1259 - font-size: 20px;
1260 - }
1261 -
1262 - .resources-next {
1263 - text-align: left;
1264 - }
1265 1265   }
1266 1266  }
XWiki.StyleSheetExtension[1]
code
... ... @@ -1,14 +1,8 @@
1 1  /* ========== Agnease Public Top Menu ========== */
2 -
3 -/* Desktop alignment */
4 -#menuview .navbar-nav {
5 - float: right !important;
6 -}
7 -
8 8  /* Top-level menu items */
9 9  
10 -.agnease-menu-item,
11 -.agnease-menu-link {
4 +#menuview .agnease-menu-item,
5 +#menuview .agnease-menu-link {
12 12   > a,
13 13   > .dropdown-toggle {
14 14   color: @brand;
... ... @@ -17,6 +17,7 @@
17 17   padding-left: 16px;
18 18   padding-right: 16px;
19 19   text-decoration: none;
14 + background: transparent;
20 20   }
21 21  
22 22   > a:hover,
... ... @@ -27,6 +27,7 @@
27 27   color: @brand-strong;
28 28   text-decoration: none;
29 29   outline: none;
25 + background: transparent;
30 30   }
31 31  
32 32   .caret {
... ... @@ -47,7 +47,7 @@
47 47  
48 48  /* Dropdown panel */
49 49  
50 -.agnease-dropdown {
46 +#menuview .agnease-dropdown {
51 51   min-width: 310px;
52 52   padding: 10px 8px;
53 53   border: 1px solid fade(@brand, 18%);
... ... @@ -66,6 +66,7 @@
66 66   font-weight: 600;
67 67   line-height: 1.3;
68 68   text-decoration: none;
65 + background: transparent;
69 69  
70 70   i {
71 71   width: 20px;
... ... @@ -81,6 +81,7 @@
81 81   color: @brand-strong;
82 82   text-decoration: none;
83 83   outline: none;
81 + background: transparent;
84 84  
85 85   i {
86 86   color: @brand-strong;
... ... @@ -90,6 +90,7 @@
90 90  
91 91   > .active > a {
92 92   color: @brand-strong;
91 + background: transparent;
93 93  
94 94   i {
95 95   color: @brand-strong;
... ... @@ -105,23 +105,33 @@
105 105  /* Mobile */
106 106  
107 107  @media (max-width: 767px) {
108 - .site-nav {
107 + #menuview {
109 109   margin-left: 0;
110 - justify-content: center;
111 - flex-wrap: wrap;
109 + width: 100%;
112 112   }
113 113  
114 - .agnease-menu-item,
115 - .agnease-menu-link {
116 - > a,
117 - > .dropdown-toggle {
118 - font-size: 16px;
119 - padding-top: 9px;
120 - padding-bottom: 9px;
121 - }
112 + #menuview .navbar-nav {
113 + float: none;
114 + margin: 0;
115 + width: 100%;
116 + text-align: center;
122 122   }
123 123  
124 - .agnease-dropdown {
119 + #menuview .navbar-nav > li {
120 + float: none;
121 + display: inline-block;
122 + }
123 +
124 + #menuview .navbar-nav > li.agnease-menu-item > a,
125 + #menuview .navbar-nav > li.agnease-menu-link > a,
126 + #menuview .navbar-nav > li.agnease-menu-item > .dropdown-toggle,
127 + #menuview .navbar-nav > li.agnease-menu-link > .dropdown-toggle {
128 + font-size: 16px;
129 + padding: 10px 10px;
130 + text-align: center;
131 + }
132 +
133 + #menuview .agnease-dropdown {
125 125   min-width: 0;
126 126   width: 100%;
127 127   padding: 4px 8px 8px 18px;
... ... @@ -129,6 +129,7 @@
129 129   border-radius: 0;
130 130   box-shadow: none;
131 131   background: transparent;
141 + text-align: left;
132 132  
133 133   > li > a {
134 134   padding: 8px 10px;