Changes for page Resources

Last modified by Agnease on 2026/05/28 08:53

From version 10.2
edited by Agnease
on 2026/05/22 10:22
Change comment: There is no comment for this version
To version 6.1
edited by Agnease
on 2026/05/22 06:13
Change comment: There is no comment for this version

Summary

Details

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