• if you came looking for something and not found it here, please fill it afterwards
  • if you work on an app migration
    • update the app's row and
    • make sure reality is reflected in columns and
    • make sure introduced changes in columns are reflected in the migrated app.

Guidelines

First from the UX perspective:

Apps and app-launcher

  1. Migrated apps must have the same canonical, unsuffixed labels as before.
  2. Migrated apps must be in their original group (e.g. Edit, Manage, Target).
  3. If bundled, old apps must be hidden from the app-launcher by default.

  4. Migrated and old apps are labelled the same („Pages” and „Pages”), see full reasoning below. As an exception, you may need to introduce some capitalization changes. Refer to M6 label column when migrating.

Here’s our conclusion re: Labeling old and new apps in app launcher

We need to differentiate btw 2 user groups:

  • Group 1: Developers migrating to 6.2 > they prefer to have old and new apps at the same time, so they can test, compare, do the migration work etc. / it is also most likely an interim situation
  • Group 2: Editors > they prefer to have only one app otherwise they will be confused which one to use.

Group 1 is a small and exceptional user group compared to Group 2. Therefore (in favor for group 2) we agreed not to label old and new apps as a default, they are named the same („Pages” and „Pages”).

But in the migration guidelines we should:

  • Provide clear guidelines to migrate the full content (e.g. all pages in one go) and from then only use the new app
  • Point out the case for developers and also provide them supporting guidelines such as
  • create new app group „M5 apps” and move old apps into there
  • rename/decorate the app label as they wish
  • configure a role based setup
  • etc.

Columns

  1. Column headers must preserve their original caption.
  2. Columns must preserve their original width or expand-ratio

App "names" (IDs)

From this technical perspective, we acknowledge app IDs are tricky to change for already migrated apps, and therefore realigning them is not a critical goal for migrations.
For newly ported apps, we should consider suffixing old app names with -m5 , and using the previous, unsuffixed name for the new one (as per consensus on the Jira ticket).

This should be especially easier on "less central" apps than Pages, Assets, etc.

Legend:

M5 label nowM6 labelold app-idnew app-idTicketMigration planned forMigration stateOld version removed from bundlePresent in List of appsRelated ticketsNotes
About MagnoliaAbout Magnoliaabout




(tick)

Activation Monitor

Activation Monitor

rename to Publishing monitor







(tick)
Activation ToolsActivation Tools





(tick)

AnalyticsAnalyticsanalytics






Assets

Assets

assetsdam (incongruent w/ future app label and possibly w/ future app label standard)

6.2


(tick)


BackupBackup





(tick)

Cache tools
  • Cache Tools

cacheTools

?





Campaign publisher

  • Campaign Publisher






(tick)

CategoriesCategories





(tick)

ConfigurationConfigurationconfiguration




(tick)

ContactsContactscontactscontacts-v8

(question)
(tick)

Content Translation

Content Translation





(tick)

CookiesCookies





(tick)



DefinitionsDefinitionsdefinitions-appdefinitions-app

6.1

(tick)

E-commerceE-commerce





(tick)

FeedsFeedsrssAggregator




(tick)

GroovyGroovy





(tick)

JCR BrowserJCR Browser




(tick)

JCR ToolsJCR Tools





(tick)

Log ToolsLog Tools





(tick)

Mail ToolsMail Tools





(tick)

Marketing TagsMarketing Tags





(tick)

MessagesMessages





(tick)

NotificationsNotificationsnotifications

6.0


(tick)

Pages M5Pagespagespages-app (question) weak distinciton

6.2

(tick)


PasswordsPasswordspassword-manager




(tick)

Personas

Personas NEW

  • rename to Personas
personaspersonas-app

6.2



Preview as visitor

(Preview as title after opening app)

Preview as visitor NEW

  • rename to Preview
previewpreview-app


6.2


(tick)


Processed Resources

Processed Resources





(tick)

Publishing ToolsPublishing Tools





(tick)
DOCS update required: https://documentation.magnolia-cms.com/display/DOCS62/Publishing+Tools+app
Repository tools
  • Repository Tools






(tick)

REST ClientREST Client





(tick)

REST Client app 
(will appear in 6.2)



Resource FilesResource Filesresourcesresources

6.2

(tick)


SampleSample





(tick)

SecuritySecuritysecurity



(tick)

Segments

Segments NEW

  • rename to Segments
segmentationsegmentation-app

6.2




SiteSitesite




(tick)

StoriesStoriesstories




(tick)

Sync InstanceSync Instance





(tick)

TagsTagscontent-tagscontent-tags

6.2


(tick)

Tasks

Taskstasks-app

6.0


(tick)

ToursTourstours






Tour CategoriesTour CategoriestourCategories






VisitorsVisitors





(tick)

Done:

Reference: