Page tree
Skip to end of metadata
Go to start of metadata

Please keep updated

  • 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.
    • Developers may—and should—adjust their app-launcher layout as appropriate to distinguish apps during the migration effort (e.g. by creating an "old apps" group).
 PXM statement - click here to expand...

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 now is bold only if it was checked that the name is correct. If you are editing that row, check the actual name of the app as old label and then bold it.
  • Migration state can be assumed from ticket state, but a separate column is there for sorting purposes.
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)

MGNLDAM-800 - Getting issue details... STATUS

MGNLDAM-809 - Getting issue details... STATUS

6.2

MIGRATED


(tick)


BackupBackup





(tick)

Cache tools
  • Cache Tools

cacheTools

DEFINE

MGNLUI-5392 - Getting issue details... STATUS

?

TO DO





Campaign publisher

  • Campaign Publisher






(tick)

CategoriesCategories





(tick)

ConfigurationConfigurationconfiguration

MGNLUI-5755 - Getting issue details... STATUS




(tick)

ContactsContactscontactscontacts-v8

(question)
(tick)

Content Translation

Content Translation





(tick)

CookiesCookies





(tick)



DefinitionsDefinitionsdefinitions-appdefinitions-app

CFGUI-85 - Getting issue details... STATUS

6.1

MIGRATED

REMOVED

(tick)

E-commerceE-commerce





(tick)

FeedsFeedsrssAggregator




(tick)

GroovyGroovy





(tick)

JCR BrowserJCR Browser

MGNLUI-5759 - Getting issue details... STATUS




(tick)

JCR ToolsJCR Tools





(tick)

Log ToolsLog Tools





(tick)

Mail ToolsMail Tools





(tick)

Marketing TagsMarketing Tags





(tick)

MessagesMessages





(tick)

NotificationsNotificationsnotifications

6.0

MIGRATED


(tick)

Pages M5Pagespagespages-app (question) weak distinciton

MGNLPN-472 - Getting issue details... STATUS

6.2

MIGRATED

TO DO

MAGNOLIA-7739 - Getting issue details... STATUS

(tick)

PAGES-194 - Getting issue details... STATUS


PasswordsPasswordspassword-manager




(tick)

Personas

Personas NEW

  • rename to Personas
personaspersonas-app

MGNLPN-469 - Getting issue details... STATUS

6.2

MIGRATED


MGNLPN-445 - Getting issue details... STATUS


Preview as visitor

(Preview as title after opening app)

Preview as visitor NEW

  • rename to Preview
previewpreview-app MGNLPN-470 - Getting issue details... STATUS


6.2

MIGRATED


(tick)

MGNLPN-449 - Getting issue details... STATUS


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

MGNLRES-331 - Getting issue details... STATUS

6.2

MIGRATED

REMOVED

(tick)

CFGUI-83 - Getting issue details... STATUS


SampleSample





(tick)

SecuritySecuritysecurity

MGNLUI-5346 - Getting issue details... STATUS


TO DO


(tick)

Segments

Segments NEW

  • rename to Segments
segmentationsegmentation-app

MGNLUI-5646 - Getting issue details... STATUS

6.2

MIGRATED




SiteSitesite




(tick)

StoriesStoriesstories




(tick)

Sync InstanceSync Instance





(tick)

TagsTagscontent-tagscontent-tags

CONTTAGS-77 - Getting issue details... STATUS

6.2

MIGRATED


(tick)

Tasks

Taskstasks-app

6.0

MIGRATED


(tick)

ToursTourstours




MISSING



Tour CategoriesTour CategoriestourCategories




MISSING



VisitorsVisitors





(tick)

Done:

  • Some two worded apps have all words Capitalized, some only the first one. e.g. Resource Files but Campaign publisher or Preview as visitor Publishing tools, About Magnolia.....
    • DEV-1438 - Getting issue details... STATUS  addressed this.
  • Find out which apps are missing from the list
  • Standardise new/old labels and new app-ids  DEV-1409 - Getting issue details... STATUS
    • Clarified in guidelines at the top
  • Some of the apps are not present in Documentation's List of apps - marked as MISSING
    • Handled in DOCU-1982 - Getting issue details... STATUS  

Reference:


  • No labels

8 Comments

  1. I added REST Client (same name for old and new app)

  2. I'm working on the ticket MGNLPN-472 UX consolidation for migrated Pages app, should I add this ticket to Ticket column of Pages row?

    1. Yup. But no worries, I'm on the page now, so I'll post it there. Thx!

  3. The migrated  Activation Tools and Activation Monitor: shouldn't these be renamed to  "Publishing Tools" and  "Publishing Monitor", respectively? Since we have deprecated the Activation module .. and we also have DOCU-1989 - Remove all content related to the Activation module in 6.2 documentation.

    That would be quite a mess to explain again why we keep calling these apps Activation ... .

    1. Reach out to Ashraf Khamis, he added the name there as part of doc effort.

      1. The problem with the list is that it uses https://documentation.magnolia-cms.com/display/DOCS62/List+of+apps as the starting point of investigation. That's why we have Activation Monitor, Activation Tools AND Publishing Tools on the list because we have dedicated pages for all three. Martin Drápela I'm not sure what the status of Activation Monitor and Activation Tools is like now (I've never worked on them), but feel free to make any necessary changes.

  4. OK. Looked at the pages and,

    1. Activation Tools (and the line in the table above) should be scrapped. Publishing tools IS the app, so rather migrate Publishing Tools to 6 UI (a line is up there).
    2. Migrate and rename Activation monitor > Publishing monitor.
  5. Simon Lutz in light of the last couple of comments ^^ I dared to slightly update the table in two rows:

     I hope you agree, but feel free to adjust.