Changes for page Resources

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

From version 3.3
edited by Agnease
on 2026/05/22 06:00
Change comment: There is no comment for this version
To version 1.1
edited by Agnease
on 2026/05/01 11:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -XWiki Resources | Upgrade, Security and Custom Development Guides
1 +resources
Content
... ... @@ -1,103 +1,0 @@
1 -{{velocity}}
2 -#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 -{{html clean="false"}}
4 -
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>
12 - </div>
13 -
14 - <h1 id="hero-title">Practical XWiki guidance for better long-term maintenance</h1>
15 -
16 - <p class="resource-summary">
17 - Articles and practical notes about XWiki upgrades, custom development, governance, security,
18 - integrations and maintainable knowledge platforms.
19 - </p>
20 - </div>
21 - </section>
22 -
23 - <section class="resources-index-page">
24 - <div class="container">
25 -
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>
32 - </div>
33 -
34 - <div class="resources-grid">
35 -
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>
57 -
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>
79 -
80 - </div>
81 -
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>
89 -
90 - <div class="resource-cta">
91 - <h3>Need help with an XWiki project?</h3>
92 - <p>
93 - If your XWiki instance needs an upgrade, custom development, integration work or a technical review,
94 - we can help you evaluate the current state and define the safest next steps.
95 - </p>
96 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
97 - </div>
98 -
99 - </div>
100 - </section>
101 -
102 -{{/html}}
103 -{{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,1 +1,0 @@
1 -Practical XWiki resources from Agnease covering upgrades, security, custom development, maintainability, workflows and long-term platform care.