Skip to Content

Changes for page Resources

Last modified by Alex Cotiuga on 2026/07/21 13:07
From version 10.8
edited by Alex Cotiuga
on 2026/05/26 08:54
Change comment: There is no comment for this version
To version 10.1
edited by Alex Cotiuga
on 2026/05/22 10:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Resources
1 +XWiki Resources and Guides
Content
... ... @@ -1,7 +1,7 @@
1 1  {{velocity}}
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 3  {{html clean="false"}}
4 - ## PAGE HEADER
4 +
5 5   <section class="hero hero-centered" aria-labelledby="hero-title">
6 6   <div class="container hero-inner">
7 7   <div class="hero-kicker">
... ... @@ -8,105 +8,94 @@
8 8   <i class="fa fa-book" aria-hidden="true"></i>
9 9   XWiki resources
10 10   </div>
11 - <h1 id="hero-title">XWiki resources for upgrades, security and maintainability</h1>
11 +
12 + <h1 id="hero-title">Practical XWiki guidance for better long-term maintenance</h1>
13 +
12 12   <p class="lead">
13 - Practical articles for teams that want to keep XWiki secure, upgradeable and easier to maintain over time.
15 + Articles and practical notes about XWiki upgrades, custom development, governance, security,
16 + integrations and maintainable knowledge platforms.
14 14   </p>
15 15   </div>
16 16   </section>
17 - ## RESOURCE CARDS
18 - #set ($resourceItems = [{
19 - 'title': 'What should an XWiki security review include',
20 - 'icon': 'shield',
21 - 'url': 'resources.xwiki-security-review',
22 - 'content': 'A practical overview of what to review in an XWiki instance: version status, access rights, authentication, extensions, custom code, infrastructure, backups and operations.',
23 - 'linkLabel': 'Read article'
24 - },{
25 - 'title': 'Why upgrade your XWiki instance',
26 - 'icon': 'refresh',
27 - 'url': 'resources.why-upgrade-xwiki',
28 - 'content': 'A practical explanation of why regular XWiki upgrades matter for security, stability, extension compatibility and long-term maintenance.',
29 - 'linkLabel': 'Read article'
30 - },{
31 - 'title': 'How to customize XWiki safely',
32 - 'icon': 'code',
33 - 'url': 'resources.xwiki-custom-development',
34 - 'content': 'Guidance for organizing XWiki custom code, scripts, templates and extensions so they remain easier to maintain across upgrades.',
35 - 'linkLabel': 'Read article'
36 - }])
37 - <section id="resources-list" class="services resources-index-page" aria-labelledby="resources-title">
20 +
21 + <section class="resources-index-page">
38 38   <div class="container">
39 - <h2 id="resources-title">Useful XWiki resources</h2>
40 - <p class="section-intro">
41 - Focused guidance for production XWiki platforms, covering upgrade planning, custom development,
42 - maintainability and safer long-term evolution.
43 - </p>
44 - <div class="services-grid resources-grid">
45 - #foreach ($entry in $resourceItems)
46 - <article class="service resource-card">
47 - <div class="service-icon" aria-hidden="true">
48 - <i class="fa fa-$entry.icon"></i>
49 - </div>
50 - <div class="service-body">
51 - <h4>$entry.title</h4>
52 - <p>$entry.content</p>
53 - <p class="card-link">
54 - <a href="$xwiki.getURL($entry.url)">$entry.linkLabel</a>
55 - </p>
56 - </div>
57 - </article>
58 - #end
23 +
24 + <div class="resources-intro">
25 + <p>
26 + XWiki is a flexible platform, but the long-term quality of an instance depends on how it is configured,
27 + customized, upgraded and maintained. These resources are written for teams that want to keep their
28 + XWiki platform stable, useful and easier to evolve over time.
29 + </p>
59 59   </div>
60 - </div>
61 - </section>
62 - ## UPCOMING TOPICS
63 - #set ($upcomingTopicItems = [{
64 - 'title': 'Upgrade planning',
65 - 'content': 'How to prepare XWiki upgrades when custom code, extensions, authentication and workflows are involved.'
66 - },{
67 - 'title': 'Access and security',
68 - 'content': 'Practical notes on permissions, authentication options, MFA, SSO and security-aware administration.'
69 - },{
70 - 'title': 'Maintainable customization',
71 - 'content': 'How to extend XWiki without creating unnecessary upgrade and maintenance problems.'
72 - }])
73 - <section class="split-section" aria-labelledby="upcoming-title">
74 - <div class="container">
75 - <div class="split-grid">
76 - <div class="split-copy">
77 - <h2 id="upcoming-title">More practical XWiki topics coming soon</h2>
78 - <p>
79 - Future resources will cover XWiki access rights, authentication, migrations, security reviews,
80 - structured applications, workflows and practical administration patterns.
81 - </p>
82 - <p>
83 - The goal is to publish useful guidance that helps teams make better decisions before an upgrade,
84 - customization, migration or long-term maintenance engagement.
85 - </p>
86 - </div>
87 - <ol class="process-list">
88 - #foreach ($entry in $upcomingTopicItems)
89 - <li>
90 - <strong>$entry.title</strong>
91 - $entry.content
92 - </li>
93 - #end
94 - </ol>
31 +
32 + <div class="resources-grid">
33 +
34 + <article class="resource-card">
35 + <div class="resource-card-icon">
36 + <i class="fa fa-refresh" aria-hidden="true"></i>
37 + </div>
38 + <div class="resource-card-body">
39 + <div class="resource-card-label">Upgrade guidance</div>
40 + <h2>
41 + <a href="$xwiki.getURL('resources.why-upgrade-xwiki')">
42 + Why upgrading your XWiki instance should be a regular priority
43 + </a>
44 + </h2>
45 + <p>
46 + Understand why postponed upgrades can increase security exposure, compatibility risk and
47 + long-term maintenance cost.
48 + </p>
49 + <a class="resource-card-link" href="$xwiki.getURL('resources.why-upgrade-xwiki')">
50 + Read the article
51 + <i class="fa fa-angle-right" aria-hidden="true"></i>
52 + </a>
53 + </div>
54 + </article>
55 +
56 + <article class="resource-card">
57 + <div class="resource-card-icon">
58 + <i class="fa fa-code" aria-hidden="true"></i>
59 + </div>
60 + <div class="resource-card-body">
61 + <div class="resource-card-label">Custom development</div>
62 + <h2>
63 + <a href="$xwiki.getURL('resources.xwiki-custom-development')">
64 + How to customize XWiki safely without creating upgrade problems
65 + </a>
66 + </h2>
67 + <p>
68 + Learn how to organize custom XWiki code, scripts, templates and extensions so they remain
69 + maintainable across upgrades.
70 + </p>
71 + <a class="resource-card-link" href="$xwiki.getURL('resources.xwiki-custom-development')">
72 + Read the article
73 + <i class="fa fa-angle-right" aria-hidden="true"></i>
74 + </a>
75 + </div>
76 + </article>
77 +
95 95   </div>
96 - </div>
97 - </section>
98 - ## CTA
99 - <section class="cta-section" aria-labelledby="resource-cta-title">
100 - <div class="container">
101 - <div class="cta-panel">
102 - <h2 id="resource-cta-title">Need help with an XWiki project?</h2>
79 +
80 + <div class="resources-next">
81 + <h2>More topics coming soon</h2>
103 103   <p>
83 + Future resources will cover XWiki access rights, authentication, migrations, security reviews,
84 + structured applications, workflows and practical administration patterns.
85 + </p>
86 + </div>
87 +
88 + <div class="resource-cta">
89 + <h3>Need help with an XWiki project?</h3>
90 + <p>
104 104   If your XWiki instance needs an upgrade, custom development, integration work or a technical review,
105 - Agnease can help evaluate the current state and define practical next steps.
92 + we can help you evaluate the current state and define the safest next steps.
106 106   </p>
107 107   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
108 108   </div>
96 +
109 109   </div>
110 110   </section>
99 +
111 111  {{/html}}
112 112  {{/velocity}}