Supported Symbol of MD (Marque Déposée) All Major Browsers:
ᴹᴰ

1. Why Use ᴹᴰ Instead of MD?

It’s important to use ᴹᴰ, rather than the letters “M” or “D” superscripted because of Search Engine Optimization (SEO) and documentation. The usage of ᴹᴰ ensures that the content is accurately represented and indexed correctly by search engines, which may not recognize plain superscripted letters as the official Marque Déposée symbol. Additionally, using the correct symbols ensures compliance with legal and branding guidelines, preserving the authenticity and recognition of the trademark.

2. Correct Representation Across Browsers and Platforms

Another critical reason for using ᴹᴰ instead of a HTML Entity (🅫 or 🅫), simple “M” and “D” or other symbols is that the Modifier Letter Capital M and D are universally supported across most modern browsers and platforms. In contrast, the 🅫(Raised Md Sign) and other HTML entities may not render consistently, leading to potential misrepresentation of the content. By using ᴹᴰ (ᴹ (Modifier Letter Capital M) and ᴰ (Modifier Letter Capital D)), we ensure that the trademark symbol is correctly displayed to all users, regardless of their browser or device.

3. Steps to Use ᴹᴰ in Your Content

To use ᴹᴰ in your content, you can simply copy to clipboard the characters from here: ᴹᴰ, and paste them directly into your website’s text editor. All major browsers should support these characters and prevents any display issues. If your current font does not support these characters, a default web-safe font would be invoked, and will include the standard font look and feel on your page.

Supported Symbol of MD (Marque Déposée) All Major Browsers:
ᴹᴰ
Take a look at these production example websites who are using on their websites:

1. https://www.purina.ca/fr/beggin/dog-treats/beggin-strips-bacon-peanut-butter
2. https://www.nestleprofessional.ca/fr/nestle-confectionery/miettes-de-smarties
3. https://business.michelin.ca/fr/pneus/michelin-megaxbib

4. Conclusion

Using the correct representation for the French trademark symbol, ᴹᴰ, is essential for both legal compliance and proper content indexing by search engines. By following the guidelines outlined above, you can ensure that your content accurately reflects the Marque Déposée symbol and is correctly displayed across all platforms and browsers. This small but significant detail helps maintain the professionalism and credibility of your website.

This structured approach ensures clarity and compliance with proper usage, enhancing both the legal accuracy and user experience on your site.

The post How can I add the French trademark symbol MD to my Website? appeared first on Sourced Code.

In this article, we will be configuring your AEM ui.content maven module to import the rep:policy as expected to allow the everyone group to view the /content/sourcedcode folder.

Step 1

Create a file named _rep_policy.xml under /ui.content/src/main/content/jcr_root/content/sourcedcode/_rep_policy.xml

Step 2

Update and add the _rep_policy.xml file, within /ui.content/src/main/content/META-INF/vault/filter.xml

Step 3

Ensure that the /ui.content/pom.xml has the correct plugins installed. Make sure the versions are exactly the same as the configuration as looking like below.

Step 4

It’s very important that the is set to merge, or else the ui.content package will always overwrite the rep:policy node from the installed AEM environment. In step #3, make sure line:8 is set to your desires.

other options include:
ignore: Ignores the packaged access control and leaves the target unchanged.
overwrite: Applies the access control provided with the package to the target. this also removes existing access control.
merge: Merge access control provided with the package with the one in the content by replacing the access control entries of corresponding principals (i.e. package first). It never alters access control entries of principals not present in the package.
merge_preserve: Merge access control in the content with the one provided with the package by adding the access control entries of principals not present in the content (i.e. content first). It never alters access control entries already existing in the content.
clear: Clears all access control on the target system.

The post Importing rep:policy nodes in the ui.content maven content package appeared first on Sourced Code.

Typically a scaled AEM structure, security is the highest priority. Typically Content Author’s privileges are restricted, so AEM page publishing is restricted; therefore AEM Workflows are utilised. Click here to skip the the Touch UI – AEM Workflow topic.

1. Touch UI – Site Console – Quick Publish

If you have the right privilege to replicate a page, and all it’s referenced resources, you can simply publish a page with the “Quick Publish” button from the Site Console’s navigation.

How to publish a page using the “Quick Publish” AEM feature:

1. Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/sites.html/content.
2. Step 2: Select on the “Targeted Page” by clicking on the thumbnail tile.
3. Step 3: Click on “Quick Publish” to replicate the Page.
4. Done.

2. Touch UI – Site Console – Manage Publication

If you have the right privilege to replicate a page, and all it’s referenced resources, you can simply replicate a page with the “Quick Publish” button from the Site Console’s navigation.

But if you wish to manage the “referenced resources”, you can use the “Manage Publication” replication AEM feature.

How to publish a page using the Manage Publication AEM feature:

1. Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/sites.html/content.
2. Step 2: Select on the “Targeted Page” by clicking on the thumbnail tile.
3. Step 3: Click on the “Manage Publication” (if your screen is too small, click on the drop down … icon to expose this link).
4. Step 4: Select on the “Publish” option.
5. Step 5: Click on “Next”.
6. Step 6: Review References: By default, all resources in AEM that are referenced by the targeted page will be replicated. References items should be reviewed before replicating the page.
7. Step 7: Review References – Select on the “Targeted Page” by clicking on the thumbnail tile.
8. Step 8: Review References – Click on “Published References” to reveal a dialogue of all the referenced resources.
9. Step 9: Review References – Manage “Targeted References”; radio button clicked mean to “include resource as a part of the page replication. Click on “Done” to save settings.
10. Step 10: Click on “Publish” to replicate the Page.
11. Done.

Steps 2 & 3

Steps 4 & 5

Steps 6…10

3. Touch UI – Editable Page – Sidebar Drop Options

If you have the right privilege to replicate a page, after a change within the AEM Page Editor, a replication from the sidebar drop options can be utilised to replicate the page.

How to publish a page using from the “Editable Page” AEM feature:

1. Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/editor.html/content/we-retail/us/en/about-us.html.
2. Step 2: Click on “Publish Page” to replicate the Page.

4. Touch UI – Activate a Page with an AEM Workflow

Typically a scaled AEM structure, security is the highest priority. Typically Content Author’s privileges are restricted, so AEM page publishing are restricted; therefore AEM Workflows are utilised.

One of the most popular page publishing type AEM Workflows utilised in AEM is Content Approval AEM Workflows. Content Approval AEM Workflows are implemented based on the business requirements and context of the AEM customer, but as an example of this blog article, we will take the “Request to Publish”, out of the box AEM Workflow model as an example.

The “Request to Publish” is an example of an out of the box AEM Workflow model that can be used by Content Authors with less privileges. When the “Request to Publish” AEM Workflow has been started, a AEM Workflow task is sent to a supporting user-group, for them to approve the request. Once the request have been approved, the page will be replicated; typically a system user is replicating the page with the correct privileges.

How to publish a page using from the “Activate a Page” AEM Workflow:

1. Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/sites.html/content.
2. Step 2: Select on the “Targeted Page” by clicking on the thumbnail tile.
3. Step 3: Click on “Create” to reveal a drop down menu & Click on “Workflow”.
4. Step 4: Select on the targeted “Workflow Model”.
5. Step 5: Input a “Workflow Title”.
6. Step 6: Click on “Next”.
7. Step 7: Click on “Create”.
8. Done. When the page is approved the page will be published.

Steps 2 & 3

Steps 4…6

Step 7

5. CRX/DE – Replication Tab

In some cases where an administrator needs to quickly publish a page, they are utilise the “Replication Tab” within the CRX/DE web console. This feature is only used by users who knows that they are doing.

How to publish a page using “CRX/DE Replication Tab”:

1. Step 1: Navigate to the CRX/DE Console http://localhost:4502/crx/de/index.jsp
   .
2. Step 2: Select on the “Targeted Page”.
3. Step 3: Select on the “Replication” tab.
4. Step 4: Click on “Replicate” to replicate the Page.
5. Done.

The post 5 Popular Ways to Replicate a Page in AEM appeared first on Sourced Code.

Every time when a new asset is installed (via the package manager) or uploaded into AEM, the OOTB (out of the box) AEM workflow launchers will be triggered. During the operation/processing of these assets, the author instance will start consuming the CPU, and the environment may be slowed down, depending on the number of assets being processed at the time.

Since all your assets have already been processed by another AEM author environment, it would not make sense for each asset to again be processed; this will be a waste of usage of the CPU.

I am recommending that if a large amount of AEM DAM assets (that already been processed, zipped in a content package) are being installed via package manager into a production live environment, to inform or disable all authors to stop authoring within a time frame. Within the time frame, disable the workflow launchers and install the assets into the production AEM instance. Finally, re-enable the workflow launchers after all assets have been successfully installed.

To enable/disable workflow launchers, check out this article. How to enable/disable AEM Workflow Launchers

The post Strategy to Consider when Migrating a Large Amount of Assets into an AEM author Instance appeared first on Sourced Code.

During appropriate understanding, we may need to disable workflow launchers services; always remember to re-enable after disabling these services.

1. Disable AEM Workflow Launchers

a. Open the AEM system console component page:

b. Use Google Chrome, Firefox, or other browsers to quickly find text on a page. Control(or CMD on Mac) + F to find the fully qualified java name below. Click on the “stop” button to disable each workflow service.

This is an example of how the services will look when they are found:

You will be redirected to the services detail page when 
the stop button have been clicked on. Refresh the package, 
and you will be redirected back to the component services list page:

2. Disable AEM Workflow Launchers with cURL

Use the cUrl command to “disable” AEM workflow launchers:

3. Enable AEM Workflow Launchers

a. Open the AEM system console component page:

b. Use Google Chrome, Firefox, or other browsers to quickly find text on a page. Control(or CMD on Mac) + F to find the fully qualified java name below. Click on the “start” (play) button to disable each workflow service.

This is an example of how the services will look when they are found:

You will be redirected to the services detail page when 
the start button have been clicked on. Refresh the package, 
and you will be redirected back to the component services list page:

4. Enable AEM Workflow Launchers with cURL

Use the cUrl command to “enable” AEM workflow launchers:

The post How to enable/disable AEM Workflow Launchers appeared first on Sourced Code.