Changes for page Public Web Site
Last modified by Agnease on 2026/05/30 16:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 1 removed)
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 consulting andengineering</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 XWikiplatformswith practical12 - engineering support,customdevelopment,integrationsandlong-termcare.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> XWikiLTS upgrades</li>17 - <li> Maintenanceandsupport</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,28 +39,26 @@ 39 39 40 40 <section aria-labelledby="platform-title"> 41 41 <div class="container"> 42 - <h2 id="platform-title">XWiki su pportforproductionknowledgeplatforms</h2>42 + <h2 id="platform-title">When XWiki becomes business-critical, it needs professional care</h2> 43 43 <p class="section-intro"> 44 - XWikioftengrowsfroma documentationspace intoabusiness-criticalknowledgeplatform.45 - Whenit supports intranets, procedures, workflows, auditsor integrations,itneedsstructuredtechnical care46 - for upgrades,security,permissions and maintainability.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"> 50 50 <article class="pathway-card"> 51 - <div class="card-heading"> 52 - <div class="pathway-icon"> 53 - <i class="fa fa-refresh" aria-hidden="true"></i> 54 - </div> 55 - <h3>Upgrade XWiki safely</h3> 51 + <div class="pathway-icon"> 52 + <i class="fa fa-refresh" aria-hidden="true"></i> 56 56 </div> 54 + <h3>Keep XWiki current</h3> 57 57 <p> 58 - Plan and execute XWikiLTSupgrades with compatibility checks,staging validationandrollback planning.56 + Plan and execute safe upgrades to supported XWiki versions, with compatibility checks and rollback planning. 59 59 </p> 60 60 <ul> 61 61 <li>LTS upgrade planning</li> 62 62 <li>Extension and custom code review</li> 63 - <li> Staging and production validation</li>61 + <li>Production rollout validation</li> 64 64 </ul> 65 65 <p class="card-link"> 66 66 <a href="$xwiki.getURL('services.xwiki-upgrades')">View upgrade services</a> ... ... @@ -68,19 +68,17 @@ 68 68 </article> 69 69 70 70 <article class="pathway-card"> 71 - <div class="card-heading"> 72 - <div class="pathway-icon"> 73 - <i class="fa fa-life-ring" aria-hidden="true"></i> 74 - </div> 75 - <h3>Maintain XWiki reliably</h3> 69 + <div class="pathway-icon"> 70 + <i class="fa fa-life-ring" aria-hidden="true"></i> 76 76 </div> 72 + <h3>Keep XWiki reliable</h3> 77 77 <p> 78 - KeepproductionXWiki instancesstablewithtroubleshooting,maintenanceplanning,recovery supportand security-aware care.74 + Get long-term technical care for instances that need to stay stable, secure and recoverable. 79 79 </p> 80 80 <ul> 81 81 <li>Troubleshooting and recovery</li> 82 82 <li>Performance and log analysis</li> 83 - <li> Upgradeandmaintenanceplanning</li>79 + <li>Security-aware maintenance</li> 84 84 </ul> 85 85 <p class="card-link"> 86 86 <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a> ... ... @@ -88,19 +88,17 @@ 88 88 </article> 89 89 90 90 <article class="pathway-card"> 91 - <div class="card-heading"> 92 - <div class="pathway-icon"> 93 - <i class="fa fa-cogs" aria-hidden="true"></i> 94 - </div> 95 - <h3>Extend XWiki for your processes</h3> 87 + <div class="pathway-icon"> 88 + <i class="fa fa-cogs" aria-hidden="true"></i> 96 96 </div> 90 + <h3>Adapt XWiki to your business</h3> 97 97 <p> 98 - Build custom XWikiapplications,workflows,dashboardsandintegrations around realbusinessneeds.92 + Build workflows, custom applications, dashboards, integrations and automation around your processes. 99 99 </p> 100 100 <ul> 101 101 <li>Custom XWiki applications</li> 102 102 <li>Workflows and approvals</li> 103 - <li> APIs,SSO, LDAP and integrations</li>97 + <li>SSO, LDAP, APIs and integrations</li> 104 104 </ul> 105 105 <p class="card-link"> 106 106 <a href="$xwiki.getURL('services.xwiki-development-integrations')">View development services</a> ... ... @@ -114,29 +114,29 @@ 114 114 <div class="container"> 115 115 <div class="split-grid"> 116 116 <div class="split-copy"> 117 - <h2 id="why-title">Why workwith anXWiki specialist</h2>111 + <h2 id="why-title">Why choose Agnease</h2> 118 118 <p> 119 - XWiki projectsofteninvolvemore thanpages.Production platformsmayinclude customcode,120 - e xtensions, authentication,permissions,workflows,integrations andbusiness-criticalcontent.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. 121 121 </p> 122 122 <p> 123 - Agneasebrings11+ yearsof hands-onXWikiexperience tohelpreducerisk, deliverpractical improvements124 - and leave the platformeasier to maintainafter the work is complete.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. 125 125 </p> 126 126 </div> 127 127 128 128 <ol class="process-list"> 129 129 <li> 130 - <strong>Review the XWikienvironment</strong>131 - Version, extensions, infrastructure, authentication, permissions,custom code and critical features.124 + <strong>Review the current situation</strong> 125 + Version, extensions, infrastructure, authentication, custom code and business-critical features. 132 132 </li> 133 133 <li> 134 - <strong>Define thesafestnextsteps</strong>135 - Scope,risks, dependencies,effort, rollback options andvalidationrequirements.128 + <strong>Define a safe path forward</strong> 129 + Clear scope, expected effort, risks, rollback options and recommended next steps. 136 136 </li> 137 137 <li> 138 - <strong> Implement, validate and document</strong>139 - Controlled changes,testing,productionvalidation andnotesfor future maintenance.132 + <strong>Deliver and document the work</strong> 133 + Practical implementation, validation and documentation for future maintenance. 140 140 </li> 141 141 </ol> 142 142 </div> ... ... @@ -145,9 +145,9 @@ 145 145 146 146 <section class="resource-strip homepage-resource-strip" aria-labelledby="resources-title"> 147 147 <div class="container"> 148 - <h2 id="resources-title">XWiki resources for safer long-term maintenance</h2>142 + <h2 id="resources-title">Useful XWiki resources</h2> 149 149 <p class="section-intro"> 150 - Practical articlesabout XWiki upgrades,customizationandproductionplatform care.144 + Practical guidance for organizations running XWiki in production. 151 151 </p> 152 152 153 153 <div class="resource-grid"> ... ... @@ -154,17 +154,17 @@ 154 154 <article class="resource-card"> 155 155 <h4>Why upgrade your XWiki instance?</h4> 156 156 <p> 157 - Learn why regularXWikiupgrades reduce securityexposure, compatibilityissuesandlong-termmaintenance risk.151 + A business-focused explanation of why regular LTS upgrades reduce security, compatibility and maintenance risk. 158 158 </p> 159 - <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">Read the article</a>153 + <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">Read the resource</a> 160 160 </article> 161 161 162 162 <article class="resource-card"> 163 163 <h4>XWiki upgrade services</h4> 164 164 <p> 165 - SeehowXWiki upgradescanbeplanned, tested and validatedforproduction instances with customizations and integrations.159 + How Agnease approaches safe XWiki upgrades for real production environments with customizations and integrations. 166 166 </p> 167 - <a href="$xwiki.getURL('services.xwiki-upgrades')">View upgrade services</a>161 + <a href="$xwiki.getURL('services.xwiki-upgrades')">View the service</a> 168 168 </article> 169 169 </div> 170 170 </div> ... ... @@ -173,10 +173,10 @@ 173 173 <section class="cta-section" aria-labelledby="contact-title"> 174 174 <div class="container"> 175 175 <div class="cta-panel"> 176 - <h2 id="contact-title">Need XWiki consulting or support?</h2>170 + <h2 id="contact-title">Need help with XWiki?</h2> 177 177 <p> 178 - Send your current XWiki version, the issue you are facing, or the type of project you want to build.179 - A short description is enough to definepracticalnext steps.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. 180 180 </p> 181 181 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 182 182 </div>
- Agnease.Code.SEODetailsClass[0]
-
- metaDescription
-
... ... @@ -1,1 +1,0 @@ 1 -Agnease provides professional XWiki consulting, LTS upgrades, maintenance, custom development, migrations, integrations and security-aware support for production XWiki platforms. - metaTitle
-
... ... @@ -1,1 +1,0 @@ 1 -Professional XWiki Consulting, Upgrades and Development | Agnease
- XWiki.StyleSheetExtension[0]
-
- code
-
... ... @@ -369,13 +369,6 @@ 369 369 flex-direction: column; 370 370 min-height: 100%; 371 371 372 - .card-heading { 373 - display: flex; 374 - align-items: center; 375 - gap: 14px; 376 - margin-bottom: 14px; 377 - } 378 - 379 379 .pathway-icon { 380 380 width: 52px; 381 381 height: 52px; ... ... @@ -385,12 +385,12 @@ 385 385 justify-content: center; 386 386 color: @brand; 387 387 background: fade(@brand, 10%); 381 + margin-bottom: 18px; 388 388 font-size: 19px; 389 - flex-shrink: 0; 390 390 } 391 391 392 392 h3 { 393 - margin: 0; 386 + margin: 0 0 10px; 394 394 color: @text; 395 395 font-size: 22px; 396 396 line-height: 1.25; ... ... @@ -590,6 +590,31 @@ 590 590 } 591 591 } 592 592 586 +.resource-content { 587 + order: 1; 588 +} 589 + 590 +.resource-sidebar { 591 + order: 2; 592 +} 593 + 594 +@media (max-width: 767px) { 595 + .resource-layout { 596 + display: flex; 597 + flex-direction: column; 598 + } 599 + 600 + .resource-sidebar { 601 + order: 0; 602 + position: static; 603 + width: 100%; 604 + } 605 + 606 + .resource-content { 607 + order: 1; 608 + } 609 +} 610 + 593 593 /* ========== Homepage Resource Strip ========== */ 594 594 595 595 .homepage-resource-strip { ... ... @@ -819,18 +819,14 @@ 819 819 } 820 820 821 821 .resource-layout { 822 - display: block; 840 + display: grid; 841 + grid-template-columns: minmax(0, 760px) 280px; 842 + gap: 42px; 823 823 max-width: 1080px; 824 824 margin: 0 auto; 825 - padding-top:28px;845 + align-items: start; 826 826 } 827 827 828 -.resource-layout::after { 829 - content: ""; 830 - display: block; 831 - clear: both; 832 -} 833 - 834 834 .resource-content { 835 835 color: @text; 836 836 font-size: 16px; ... ... @@ -900,10 +900,6 @@ 900 900 } 901 901 902 902 .resource-sidebar { 903 - float: right; 904 - width: 280px; 905 - margin-left: 42px; 906 - margin-bottom: 28px; 907 907 position: sticky; 908 908 top: 96px; 909 909 border: 1px solid @line; ... ... @@ -950,14 +950,10 @@ 950 950 951 951 @media (max-width: 900px) { 952 952 .resource-layout { 953 - padding-top:22px;963 + grid-template-columns: 1fr; 954 954 } 955 955 956 956 .resource-sidebar { 957 - float: none; 958 - width: 100%; 959 - margin-left: 0; 960 - margin-bottom: 24px; 961 961 position: static; 962 962 } 963 963 }