Changes for page XWiki Migrations

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,7 +1,6 @@
1	1	{{velocity}}
2	2	#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3	3	{{html clean="false"}}
4		-
5	5	## PAGE HEADER
6	6	<section class="hero hero-centered" aria-labelledby="hero-title">
7	7	<div class="container hero-inner">
...	...	@@ -9,14 +9,11 @@
9	9	<i class="fa fa-exchange" aria-hidden="true"></i>
10	10	XWiki migration services
11	11	</div>
12		-
13	13	<h1 id="hero-title">Migrate knowledge into XWiki with structure and continuity</h1>
14		-
15	15	<p class="lead">
16	16	Move content from Confluence, SharePoint, MediaWiki, file-based documentation or legacy systems into XWiki
17	17	while preserving hierarchy, attachments, links, permissions and long-term maintainability.
18	18	</p>
19		-
20	20	<div class="hero-actions">
21	21	<a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a migration</a>
22	22	<a class="btn btn-secondary" href="#migration-process">See the migration approach</a>
...	...	@@ -23,16 +23,15 @@
23	23	</div>
24	24	</div>
25	25	</section>
26		-
27	27	## WHY MIGRATION NEEDS CARE
28	28	#set ($migrationReasonItems = [{
29	29	'title': 'Preserve structure',
30	30	'icon': 'sitemap',
31		- 'content': 'Keep spaces, hierarchies, navigation, page relationships and entry points understandable after the move.',
	26	+ 'content': 'Keep spaces, hierarchies, navigation and page relationships understandable after the move.',
32	32	'items': [
33	33	'Space and page hierarchy mapping',
34	34	'Navigation and landing page planning',
35		- 'Search and findability considerations'
	30	+ 'Related content and category structure'
36	36	]
37	37	},{
38	38	'title': 'Protect continuity',
...	...	@@ -46,24 +46,21 @@
46	46	},{
47	47	'title': 'Improve maintainability',
48	48	'icon': 'database',
49		- 'content': 'Use the migration as an opportunity to clean up content, introduce metadata and redesign what should not be copied as-is.',
	44	+ 'content': 'Use the migration as an opportunity to clean up content, introduce metadata and prepare better structures.',
50	50	'items': [
51	51	'Templates and structured data',
52	52	'Metadata and tagging strategy',
53		- 'Manual cleanup recommendations'
	48	+ 'Content cleanup recommendations'
54	54	]
55	55	}])
56		-
57	57	<section aria-labelledby="why-migration-title">
58	58	<div class="container">
59	59	<h2 id="why-migration-title">A migration is more than moving pages</h2>
60		-
61	61	<p class="section-intro">
62	62	Documentation platforms usually contain years of accumulated knowledge, links, attachments, permissions,
63		- templates, macros and habits. A successful migration should preserve what matters, reduce broken navigation
64		- and improve how the knowledge is organized and maintained in XWiki.
	56	+ templates and habits. A successful migration should preserve what matters while improving how the knowledge
	57	+ is organized and maintained in XWiki.
65	65	</p>
66		-
67	67	<div class="pathways">
68	68	#foreach ($entry in $migrationReasonItems)
69	69	<article class="pathway-card">
...	...	@@ -73,9 +73,7 @@
73	73	</div>
74	74	<h3>$entry.title</h3>
75	75	</div>
76		-
77	77	<p>$entry.content</p>
78		-
79	79	<ul>
80	80	#foreach ($item in $entry.items)
81	81	<li>$item</li>
...	...	@@ -86,7 +86,6 @@
86	86	</div>
87	87	</div>
88	88	</section>
89		-
90	90	## MIGRATION SOURCES
91	91	#set ($migrationSourceItems = [{
92	92	'title': 'Confluence to XWiki',
...	...	@@ -113,17 +113,13 @@
113	113	'icon': 'random',
114	114	'content': 'Consolidation of content from multiple sources into a more coherent XWiki knowledge platform.'
115	115	}])
116		-
117	117	<section class="services" aria-labelledby="migration-sources-title">
118	118	<div class="container">
119	119	<h2 id="migration-sources-title">Common migration sources</h2>
120		-
121	121	<p class="section-intro">
122		- Each source system has different export formats, content models, permissions and limitations.
123		- The migration approach depends on the quality of the source data, the expected XWiki structure
124		- and the amount of conversion, cleanup or redesign needed.
	109	+ Each source system has different export formats, content models and limitations. The migration approach
	110	+ depends on the quality of the source data, the expected XWiki structure and the amount of transformation needed.
125	125	</p>
126		-
127	127	<div class="services-grid">
128	128	#foreach ($entry in $migrationSourceItems)
129	129	<article class="service">
...	...	@@ -130,7 +130,6 @@
130	130	<div class="service-icon" aria-hidden="true">
131	131	<i class="fa fa-$entry.icon"></i>
132	132	</div>
133		-
134	134	<div class="service-body">
135	135	<h4>$entry.title</h4>
136	136	<p>$entry.content</p>
...	...	@@ -140,7 +140,6 @@
140	140	</div>
141	141	</div>
142	142	</section>
143		-
144	144	## MIGRATION PROCESS
145	145	#set ($migrationProcessItems = [{
146	146	'title': 'Assess the source content',
...	...	@@ -150,33 +150,29 @@
150	150	'content': 'Decide spaces, page hierarchy, templates, metadata, permissions, naming rules and navigation strategy.'
151	151	},{
152	152	'title': 'Run a sample migration',
153		- 'content': 'Migrate a representative subset of content to identify formatting, macro, link, attachment and structure issues.'
	136	+ 'content': 'Migrate a representative subset of content to identify conversion issues and validate the approach.'
154	154	},{
155	155	'title': 'Refine conversion and cleanup rules',
156	156	'content': 'Adjust mappings, formatting, link handling, attachments, macros, categories and content cleanup decisions.'
157	157	},{
158	158	'title': 'Execute and validate the migration',
159		- 'content': 'Run the migration, review key content areas, verify attachments, links, redirects and navigation, and document remaining follow-up work.'
	142	+ 'content': 'Run the migration, review key content areas, verify attachments and links, and document remaining follow-up work.'
160	160	}])
161		-
162	162	<section id="migration-process" class="split-section" aria-labelledby="process-title">
163	163	<div class="container">
164	164	<div class="split-grid">
165	165	<div class="split-copy">
166	166	<h2 id="process-title">A practical migration approach</h2>
167		-
168	168	<p>
169	169	A good migration starts with understanding how the source content is used today and how it should work
170	170	in XWiki after the move. The objective is not only to transfer data, but to create a usable knowledge
171	171	platform that people can navigate, search and maintain.
172	172	</p>
173		-
174	174	<p>
175		- Migrations are best handled iteratively: assess the source, run a sample migration, validate links,
176		- attachments, formatting and important spaces, adjust the conversion rules and then proceed with a controlled migration plan.
	155	+ Migrations are best handled iteratively: assess the source, run a sample migration, validate the result,
	156	+ adjust the transformation rules and then proceed with a controlled migration plan.
177	177	</p>
178	178	</div>
179		-
180	180	<ol class="process-list">
181	181	#foreach ($entry in $migrationProcessItems)
182	182	<li>
...	...	@@ -188,7 +188,6 @@
188	188	</div>
189	189	</div>
190	190	</section>
191		-
192	192	## WHAT CAN BE INCLUDED
193	193	#set ($migrationIncludedItems = [{
194	194	'title': 'Content conversion',
...	...	@@ -203,21 +203,17 @@
203	203	'icon': 'lock',
204	204	'content': 'Review and mapping of access rights where the source system contains meaningful permission rules.'
205	205	},{
206		- 'title': 'Cleanup and validation',
207		- 'icon': 'check-square-o',
208		- 'content': 'Post-migration review of important spaces, broken links, attachments, formatting issues and content needing manual cleanup.'
	184	+ 'title': 'Metadata strategy',
	185	+ 'icon': 'tags',
	186	+ 'content': 'Tags, categories, templates, XWiki classes or structured data to improve long-term maintainability.'
209	209	}])
210		-
211	211	<section aria-labelledby="included-title">
212	212	<div class="container">
213	213	<h2 id="included-title">What can be included</h2>
214		-
215	215	<p class="section-intro">
216		- The exact migration scope depends on the source system and the quality of the exported content.
217		- A migration engagement can include technical conversion, information architecture, permission review,
218		- cleanup recommendations and post-migration validation.
	192	+ The exact migration scope depends on the source system and the quality of the exported content. A migration
	193	+ engagement can include both technical conversion and practical information architecture work.
219	219	</p>
220		-
221	221	<div class="widgets">
222	222	#foreach ($entry in $migrationIncludedItems)
223	223	<article class="widget">
...	...	@@ -225,7 +225,6 @@
225	225	<i class="fa fa-$entry.icon"></i>
226	226	<h4>$entry.title</h4>
227	227	</div>
228		-
229	229	<p>$entry.content</p>
230	230	</article>
231	231	#end
...	...	@@ -232,7 +232,54 @@
232	232	</div>
233	233	</div>
234	234	</section>
235		-
	208	+ ## IMPORTANT CONSIDERATIONS
	209	+ #set ($migrationConsiderationItems = [{
	210	+ 'title': 'Macros and special content',
	211	+ 'icon': 'code',
	212	+ 'content': 'Source-specific macros, embeds, widgets or dynamic content may require conversion, replacement or redesign.'
	213	+ },{
	214	+ 'title': 'Links and redirects',
	215	+ 'icon': 'link',
	216	+ 'content': 'Internal links, external references, old URLs and bookmarks should be reviewed to reduce broken navigation.'
	217	+ },{
	218	+ 'title': 'Search and findability',
	219	+ 'icon': 'search',
	220	+ 'content': 'Content organization, titles, metadata and navigation affect how easily users find migrated knowledge.'
	221	+ },{
	222	+ 'title': 'User adoption',
	223	+ 'icon': 'user',
	224	+ 'content': 'A technically successful migration still needs clear navigation, familiar entry points and user guidance.'
	225	+ },{
	226	+ 'title': 'Validation effort',
	227	+ 'icon': 'check-square-o',
	228	+ 'content': 'Important spaces and high-value content should be reviewed after migration to catch conversion issues.'
	229	+ },{
	230	+ 'title': 'Cutover planning',
	231	+ 'icon': 'clock-o',
	232	+ 'content': 'Timing, source freeze, final migration, redirects and communication should be planned before go-live.'
	233	+ }])
	234	+ <section class="services" aria-labelledby="considerations-title">
	235	+ <div class="container">
	236	+ <h2 id="considerations-title">Important migration considerations</h2>
	237	+ <p class="section-intro">
	238	+ Not every element from the source system maps perfectly to XWiki. The migration plan should distinguish
	239	+ between what can be converted automatically, what needs manual cleanup and what should be redesigned.
	240	+ </p>
	241	+ <div class="services-grid">
	242	+ #foreach ($entry in $migrationConsiderationItems)
	243	+ <article class="service">
	244	+ <div class="service-icon" aria-hidden="true">
	245	+ <i class="fa fa-$entry.icon"></i>
	246	+ </div>
	247	+ <div class="service-body">
	248	+ <h4>$entry.title</h4>
	249	+ <p>$entry.content</p>
	250	+ </div>
	251	+ </article>
	252	+ #end
	253	+ </div>
	254	+ </div>
	255	+ </section>
236	236	## RELATED SERVICES
237	237	#set ($relatedMigrationServiceItems = [{
238	238	'title': 'XWiki Development & Integrations',
...	...	@@ -245,15 +245,12 @@
245	245	'content': 'Ongoing technical care for production environments after the migration is completed.',
246	246	'linkLabel': 'View support services'
247	247	}])
248		-
249	249	<section class="resource-strip" aria-labelledby="related-title">
250	250	<div class="container">
251	251	<h2 id="related-title">Related XWiki services</h2>
252		-
253	253	<p class="section-intro">
254		- Migration work often connects with custom development, support and long-term platform maintenance.
	272	+ Migration work often connects with custom development, support and upgrade planning.
255	255	</p>
256		-
257	257	<div class="resource-grid">
258	258	#foreach ($entry in $relatedMigrationServiceItems)
259	259	<article class="resource-card">
...	...	@@ -265,22 +265,47 @@
265	265	</div>
266	266	</div>
267	267	</section>
268		-
	285	+ ## RELATED SERVICES
	286	+ #set ($relatedUpgradeServiceItems = [{
	287	+ 'title': 'XWiki Support & Maintenance',
	288	+ 'url': 'services.xwiki-maintenance-support',
	289	+ 'content': 'Ongoing technical care for production XWiki environments, including troubleshooting, maintenance planning and upgrade readiness.',
	290	+ 'linkLabel': 'View support services'
	291	+ },{
	292	+ 'title': 'XWiki Security Review',
	293	+ 'url': 'services.xwiki-security-review',
	294	+ 'content': 'Security-aware review of XWiki versions, extensions, permissions, authentication and upgrade exposure.',
	295	+ 'linkLabel': 'View security review'
	296	+ }])
	297	+ <section class="resource-strip" aria-labelledby="related-title">
	298	+ <div class="container">
	299	+ <h2 id="related-title">Related XWiki services</h2>
	300	+ <p class="section-intro">
	301	+ Upgrade work often connects with long-term maintenance, security review and production platform stability.
	302	+ </p>
	303	+ <div class="resource-grid">
	304	+ #foreach ($entry in $relatedUpgradeServiceItems)
	305	+ <article class="resource-card">
	306	+ <h4>$entry.title</h4>
	307	+ <p>$entry.content</p>
	308	+ <a href="$xwiki.getURL($entry.url)">$entry.linkLabel</a>
	309	+ </article>
	310	+ #end
	311	+ </div>
	312	+ </div>
	313	+ </section>
269	269	## CTA
270	270	<section class="cta-section" aria-labelledby="cta-title">
271	271	<div class="container">
272	272	<div class="cta-panel">
273	273	<h2 id="cta-title">Planning a migration to XWiki?</h2>
274		-
275	275	<p>
276		- Send a short description of the source system, approximate content volume, export options, expected timing
277		- and the type of XWiki structure you want to achieve. A sample export or representative content area is often enough to start.
	320	+ Send a short description of the source system, approximate content volume, export options and the type of
	321	+ XWiki structure you want to achieve. A sample export or representative content area is often enough to start.
278	278	</p>
279		-
280	280	<a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss a migration</a>
281	281	</div>
282	282	</div>
283	283	</section>
284		-
285	285	{{/html}}
286	286	{{/velocity}}