Changes for page Resources

Last modified by Alex Cotiuga on 2026/07/21 13:07

From version 12.2
edited by Alex Cotiuga
on 2026/07/21 13:06
Change comment: There is no comment for this version
To version 10.10
edited by Alex Cotiuga
on 2026/05/26 09:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,5 +3,3 @@
1 -{{include reference="PublicWebSite.MacrosAndVariables" /}}
2 -
3 3  {{velocity}}
4 4  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
5 5  {{html clean="false"}}
... ... @@ -14,10 +14,6 @@
14 14   <p class="lead">
15 15   Practical articles for teams that want to keep XWiki secure, upgradeable and easier to maintain over time.
16 16   </p>
17 - <div class="hero-actions">
18 - <a class="btn btn-primary" href="$freeXWikiReviewCallURL">$freeXWikiReviewCallLabel</a>
19 - <a class="btn btn-secondary" href="$xwiki.getURL('services.WebHome')">View XWiki services</a>
20 - </div>
21 21   </div>
22 22   </section>
23 23   ## RESOURCE CARDS
... ... @@ -39,18 +39,6 @@
39 39   'url': 'resources.xwiki-custom-development',
40 40   'content': 'Guidance for organizing XWiki custom code, scripts, templates and extensions so they remain easier to maintain across upgrades.',
41 41   'linkLabel': 'Read article'
42 - },{
43 - 'title': 'From Google Workspace to XWiki',
44 - 'icon': 'exchange',
45 - 'url': 'resources.from-google-workspace-to-xwiki',
46 - 'content': 'A practical transition guide explaining what can move from Google Workspace to XWiki, what should remain in office collaboration tools, and which open-source alternatives can complete the stack.',
47 - 'linkLabel': 'Read guide'
48 - },{
49 - 'title': 'HSE Knowledge Management with XWiki',
50 - 'icon': 'shield',
51 - 'url': 'resources.hse-knowledge-management-xwiki',
52 - 'content': 'See how XWiki can support controlled HSE documentation, risk registers, corrective actions, approval workflows, dashboards and audit-ready exports.',
53 - 'linkLabel': 'Read the HSE guide'
54 54   }])
55 55   <section id="resources-list" class="services resources-index-page" aria-labelledby="resources-title">
56 56   <div class="container">
... ... @@ -79,14 +79,14 @@
79 79   </section>
80 80   ## UPCOMING TOPICS
81 81   #set ($upcomingTopicItems = [{
82 - 'title': 'Access rights governance',
83 - 'content': 'How to keep XWiki groups, inherited permissions, restricted areas and page-level exceptions understandable over time.'
64 + 'title': 'Upgrade planning',
65 + 'content': 'How to prepare XWiki upgrades when custom code, extensions, authentication and workflows are involved.'
84 84   },{
85 - 'title': 'Authentication and access control',
86 - 'content': 'Why SSO, LDAP, OIDC, SAML and MFA should be reviewed together with XWiki groups, rights and fallback access.'
67 + 'title': 'Access and security',
68 + 'content': 'Practical notes on permissions, authentication options, MFA, SSO and security-aware administration.'
87 87   },{
88 - 'title': 'Backup and restore validation',
89 - 'content': 'Why backups are only useful when restore expectations, included data and recovery steps are clearly understood.'
70 + 'title': 'Maintainable customization',
71 + 'content': 'How to extend XWiki without creating unnecessary upgrade and maintenance problems.'
90 90   }])
91 91   <section class="split-section" aria-labelledby="upcoming-title">
92 92   <div class="container">
... ... @@ -94,8 +94,8 @@
94 94   <div class="split-copy">
95 95   <h2 id="upcoming-title">More practical XWiki topics coming soon</h2>
96 96   <p>
97 - This section will expand the XWiki security review series with focused topics such as access rights,
98 - authentication, script and programming rights, backup validation, extension review and operational practices.
79 + Future resources will cover XWiki access rights, authentication, migrations, security reviews,
80 + structured applications, workflows and practical administration patterns.
99 99   </p>
100 100   <p>
101 101   The goal is to publish useful guidance that helps teams make better decisions before an upgrade,