Suryakanta Maharana

z
Creating Websites for EMEA
Region using WCM tool
Table of Contents :

 Introduction
 Purpose
 Fuze Overview and Function
 Page Design
 Eloqua Form Development
 Releasing and HardLaunch Activities
 Benifits
1. Introduction :-
 This Project is all about building New Web sites for EMEA region using Web Content Manager
tool. Also known as Fuze. Websites allows customers to know about 3M Products and its
relative information. It provides all the details about Health and Electrical, Safety and consumer
related products. Here, we built the page and publish it to live. So that users can access it.

 We use Jira tool with Kanban methodology to Manage the work.

1.1 Kanban Overview :

About Kanban:

 Kanban is a work management system designed to help visualise your work and maximise efficiency
through encouraging continuous flow. ​
 Kanban helps visualise your work using a Kanban board and cards, so we can understand our progress
in the development cycle better as well as share with stakeholders in an easy-to-understand format.​
 Kanban is a ‘pull’ system, which means when you have the bandwidth you simply pull work from “to-do”
into “in progress” until it reaches “done”. ​
 Kanban does not use sprints and no longer uses story points to report on capacity. Instead, the focus is
on continuous flow, limiting WIP and cycle time.

JIRA Workflow in Kanban Board:

 A story represents what it is the team needs to deliver.

 Stories are the building blocks of larger pieces of work (epics). Each story will represent an item of work
that needs to be done to contribute to the completion of the epic. Stories can then be broken down into
subtasks.
 Stories will first be added to the backlog where they will be prioritised by the product owner. Throughout
the development cycle, the product owner and story authors will prioritise stories to ensure the most
important stories are at the top of list.
 The story author or product owner is responsible in ensuring the story meets the definition of ready
(DoR) before adding it into the development queue and meets the definition of done (DoD) before
closing the story.
 The development team are responsible for completing the tasks detailed in the story.
Jira Story Workflow
1.2 Requirements for Website Construction process :

 Total number of pages in website.

 Site hierarchy for the pages in the site.
 Portal place – These are static pages stored and maintained within Fuze.
 Page title, Friendly URL, Meta description and keywords details.
 Content (includes text, link and images) to be placed in the pages.
 Navigation details.
 Wire Frame – UI design to be followed to construct a page.
 Eloqua Briefing Document for Eloqua form development.
 Hard Launch information (Site crawl for Search and Old sites redirects)

1.3 Source to Build Web content:

We will use HCL web content manager tool [1] to add, update and delete data for the websites which are
already in live and for currently in under building.

Below are the environment details:

Environment Source URL
HCL Web Content http://fuzeauth.3m.com/wps/myportal/Applications/
manager (Fuze url) Content/Authoring/
Development URL https://fuzeauth.3m.com/
Eloqua URL https://secure.p04.eloqua.com/Main.aspx

Live URL https://www.3m.com

2. Purpose :-

Purpose:
This campaign webpage is designed to effectively promote and sell your product, ensuring a smooth and informative
experience for potential customers. The site offers an interactive platform where users can:

Directly Inquire and Receive Answers: A user-friendly form allows customers to quickly send their queries. This helps
bridge communication, allowing you to respond promptly to specific customer needs and provide tailored assistance.

Locate Nearby Dealers Easily: The "Find a Dealer" section empowers users to locate the nearest authorized dealer with
just a few clicks. This feature simplifies the buying process and increases foot traffic to your dealers, boosting offline sales
and customer satisfaction.

Seamless Product Sales: Integrated e-commerce capabilities make it possible for users to complete purchases directly on
the webpage. This functionality is invaluable for converting interest into actual sales by reducing the steps between
discovering a product and completing a purchase.
3. Fuze Overview and Function

 Fuze is the website development platform for 3M. It delivers a responsive experience across all
devices and simplifies development with pre-built design patterns. Various services are integrated to
access 3M's web platforms.
 Fuze is split between 2 interfaces. The Front-end displays content, WCM Administration stores the
content. This section explains how website content is organized.

Front-end:

The front-end is where content is displayed as a web page. Edits to the page properties are done here.
In-line editing can also be used to create and modify content.
WCM Administration:

It is Also called as Back-end. It stores the content for a website. It’s like a special type of file
manager. Home page of WCM looks as below:
Functionality:

1- Portal Place Creation:

 New Portal Place should be Created in the Backend, where the site areas and content related to new
website we are building will be stored in that portal place.
 This helps the data to be stored in correct path for the replication locals along with the base site.
2- How Portal Places and Libraries Interact:
 When a website is created, the portal place and the Top-Level Site Area are created.
 The portal place contains 1 homepage.
 Based on the locale requested in the website request, the Top-Level Site Area is created in a
specified locale.
 The portal place for the website Excellere site is called HCB_Excellere. Within it, there is a
home portal page mapped to.
 All portal pages created underneath the homepage are mapped to Page-Level-Site Areas in
the same Top-Level Site Area in the en_GB library.
3- Create a Project:

 Go to WCM Administration. http

://fuzeauth.3m.com/wps/myportal/en_US/Applications/Content/Authoring/
 In the menu, select New Project.
 The New Project window will open.
 Within the New Project window, enter the name of the new project.
 Once Project name is given, Navigate to Properties  and give user access as All Authenticated portal
users And Manager access.
 Once access is given, click on OK. It appears a below:
 Now save and close. The project will be created succesfully.
4- Create Page :
 Portal Pages in Fuze display design pattern and portlet content. Portal pages can be created with an
automatic site area or without one.
 This site area will be placed in the site area that the parent page is mapped to.
 The name of the site area is taken from the Friendly-URL field.
 All of the following configurations are done within the Create Page window of the
4. Page Design :-
 We have SSN section and Footer section where user can navigate to different different pages.

 After SSN we have a Hero sction where user can find the details of the page and product.

 We one jump menu baar that can jump anywhere of page as per user.
 We have column section where user can find the used of the product and can read the details

and can navigate to the product.

 We have find dealer section where user can click and find teh dealer near him/her.

 The we have Eloqua form where user can direct contact to us with his/her querry.
5. Eloqua Form Development :-

 Eloqua is a form that is build and updated on webpages to collect the information of users about there
interests and opinions on particular products or items.

 Creating and Configuring the Eloqua form :

 Open Eloqua Server by using the url https://secure.p04.eloqua.com/Main.aspx Home page looks like
below
 Using a create a form, we can create new asset for Eloqua form.
 Use the name generator to create a name for the form. Please ensure that you change the
html name of the form to match the main name of the form.
 Use the name generator to create a name for the form. Please ensure that you change the
html name of the form to match the main name of the form.
 Using the briefing document given, drag and drop all the custom and contact fields and give
custom fields an appropriate HTML Name (do not change HTML name of contact fields).
 Update the value of Redirect to web page components to Always redirect to same landing
page and MMM API intergration Landing page
 Map all the postdata server fields with correct source and target fields, matching with the field
names in the design.
 Then Update the code in page.
6. Releasing and HardLaunch Activities :-

In Releasing activity we have to publish the project and setup the vanity url and heflag

Publish Project:
 Once edit mode opens -> click on Manage -> We can see all the content items with draft
status and all the items belong to same local.
 Select all the content items by clicking on 100 items per pages
 After selecting all the items, click on Approve under more dropdown.
 All the content items will be aproved. Then click on Publish project button at the top of the
page.
 It takes 3- 4 hours for the page to be live.
Hard Launch:

Hardlaunch activities are those that will be done once the site is in live. And the ticket is moved to
Hardlaunch. Below 2 are the ones that are done during hardlaunch status.

1. Vanity Url
2. Redirects
3. Sitecrawls

Vanity Url:

Vanity URL's are nothing but short URL's which will be used as an alternative URL. These short URL's will be
used for accessing the page. Vanity URL's will be requested during campaign times.

Redirects:

Redirects will help to redirect from one page to another page. This is mainly used when new
sites or pages are build in the place of old one. These will be mainly used to navigate from old
sites to the new site. We have Page level redirects, Domain level redirects and Root
level redirects. We are not using Domain level & Root level redirects nowadays. But if you come
across any request related to them, just raise a ITSM tickets for them as well.
Site Crawl:

 Site crawl will help to enable the site in the search engines. Mainly it will help to find the pages in the internal
search of the specific site.

 Previously the crawl requests are requested as an ITSM ticket which is later added as a comment to the Jira
address of the respective week. Later, the Jira details are provided to the user via mail and the incident is set as
resolved.

 Crawl requesting URL - https://fuzeauth.3m.com/my3M/en_US/crawl_url/

 Below are the current steps to request a URL to be crawled,

1. select the locale and enter the respective URL of that locale

2. You will receive a message with the current JIRA ID once the details are submitted.

3. The requested URLs will be automatically added in the comments of the respective Jira ID after 4 hours.
HREF Lang

 How it feels when you are a native of Italy and on searching for any products in search engine gives you
the results related to US or UK? You obviously expect Italian results to pop-up first on your screen. Here
comes the use of HREF.

 HREF lang tag allows search engines to pop-up the results belonging to a particular region or country in
the first results page followed by the similar products from other regions and sites.

 For Example : A user in France is searching for "Bonding and Assembly" in a search engine and he
would be left astonished with the results.

 He can no where see the results on the page though we have the page live -
https://www.3mfrance.fr/3M/fr_FR/solutions-adhesives-assemblage/ The reason being that HREF lang
is not implemented for this site in fr_FR locale.

 On the other hand, if a user in Canada is searching for Bonding and Assembly, he can easily get it on
the top of the page as HREF lang is implemented for this site in en_CA locale. Look at the grab below.
7. Benifits :-

 Enhanced Customer Engagement: The interactive form and dealer locator foster a highly engaging environment

that makes it easier for potential customers to connect with your brand, ask questions, and receive support.

 Increased Sales Conversion: With a direct route to both online purchases and local dealers, customers are more

likely to complete their purchase. The page’s structure guides customers efficiently from discovery to decision,

reducing friction and improving conversion rates.

 Wider Reach and Brand Visibility: By providing a seamless online presence, this page helps attract a broader

audience. The convenience and accessibility offered make your brand more attractive to digital-savvy customers

looking for hassle-free shopping experiences.

 Customer-Centric Experience: The website is designed with the customer journey in mind, making it simple for

them to find information, locate dealers, and buy products. This increases customer satisfaction, loyalty, and

likelihood of repeat purchases.

 Real-Time Market Insights: Through customer queries and dealer searches, you gain valuable insights into what

customers are interested in, which can inform future marketing and product development strategies.
-: Thank You :-