Best Practice: Content Setup, that is fit for Website Design updates

(continuing from a conversation on Slack)

What is the recommended initial setup and further path to take for website design updates?
Example:

  • Three separate planned Blog prototypes or preliminary simple versions of a blog, that contains valuable content,

→ shall be refactored into a knowledge base after a year.
These won’t have thousands of posts, but maybe a hundred.

  • Now, the knowledge base will have a different, fresher look, but make use also of the same pieces of content.

I’m trying to decide

  • Will it be best to create new compatible NodeTypes and migrate the existing?
  • How should the posts be moved over to the new knowledge base, in an easy fashion, so they can then be further improved there?
  • Can the blog content be previewed in the context of the knowledge base without actually moving it over there, just for previewing?

My current plan:
All of the above will reside in the same Neos instance, on different sites.
The NodeType definitions will be similar but vary per blog according to the individual blog’s needs.

I wonder,
how easy it is to move masses of

  • blog post nodes
  • and associated categories,
  • dimensions
  • and other attached stuff

around to a new blog location in the node tree, within the same Neos installation but to a new site/domain.

1 Like

My recommendations would be:

  • Use a shared package as base to provide blog nodetypes for all sites
  • Create derived nodetypes in each site if there are differences
  • If the migrations are non trivial and affect node hierarchies create a cli-command for that
1 Like