It's time to move to Umbraco 17

Planning validation for an Umbraco upgrade

It's time to move to Umbraco 17
OXOAK / Content and design

Practical notes

1 min read

Planning validation for an Umbraco upgrade

Record content structure, extensions and deployment requirements, then test an isolated copy. Establish compatibility from documentation and project samples.

Putting content management into practice

A content model defines independently maintained and reusable information. Authoring, preview, approval and publication form a workflow; an API response validates only one part.

Checking the result

Have real editors create, change and restore content using long headings, missing fields and multiple languages. Record development dependencies and release ownership.

Planning validation for an Umbraco upgrade · Working details

Contact OXOAK