MAGENTO PREP

Get Started. It's Free
or sign up with your email address
Rocket clouds
MAGENTO PREP by Mind Map: MAGENTO PREP

1. 1.1 ONLINE MERCHANDISING

1.1. MARKETING STRATEGIES

1.1.1. OMNICHANNEL

1.1.2. MULTICHANNEL

1.1.3. Affiliate marketing

1.1.4. Social marketing

1.1.5. Email marketing

1.1.6. Word of mouth marketing

1.1.7. social merchandising techniques

1.1.7.1. Wishlist /sharing buttons

1.1.7.2. Tailoring related products or suggestions of users

1.1.7.3. Reviews

1.1.8. SMART REQUIREMENTS

1.1.8.1. S - SPECIFIC

1.1.8.2. M - MANAGEABLE

1.1.8.3. A - ASSIGNABLE

1.1.8.4. R - RELEVANT

1.1.8.5. T - TIME RELATED

1.2. STEPS OF SETTING UP A NEW ONLINE STORE

1.2.1. STRATEGY(90%)

1.2.1.1. WHO IS YOUR COMPETITION?

1.2.1.2. WHAT WILL SET YOU APPART?

1.2.1.3. WHAT ARE YOU OFFERING THAT YOUR COMPETITORS WILL NOT OFFER?

1.2.1.4. WHY DO YOU WANT TO GET INTO THE BUSINESS?

1.2.2. TECHNOLOGY

1.2.2.1. DETERMINING THE PLATFORM TO START WITH

1.2.2.1.1. Small company (limited funds)

1.2.2.1.2. Bigger company (more funds)

1.2.2.2. HOSTING

1.2.2.2.1. recommendation

1.2.2.2.2. Talk to your hosting partner

1.2.2.3. DEPLOYMENT

1.2.2.3.1. Launching new site is easier then migrating the existing one

1.2.2.4. MAINTENANCE

1.2.2.4.1. Basic level

1.3. SEARCH STRATEGIES

1.3.1. Keyword search

1.3.1.1. Search bar needs to be visible

1.3.1.2. Include and, the, or

1.3.2. Auto-suggest

1.3.2.1. Based on the keywords and phrases, to be found by client

1.3.3. Guided navigation

1.3.3.1. Help customer reach the decision we want them to reach

1.3.3.2. The technology is still up/coming and expensive to do right

1.4. UPSELLING/CROSS-SELLING

1.4.1. UPSELL

1.4.1.1. Alternative/more expensive option; awareness of other options on website

1.4.2. CROSS-SELL

1.4.2.1. Don't show options already in cart (they might reconsider their options)

1.4.2.2. Show them complementary products

1.5. SEO IN ECOMMERCE

1.5.1. Quality URL structure

1.5.1.1. Don't use numbers/IDs

1.5.1.2. Use words (up to 75 characters)

1.5.2. Good information architecure

1.5.2.1. Questions

1.5.2.1.1. What are the paths to the categories?

1.5.2.1.2. How do they relate to the products?

1.5.2.1.3. Is there any correlation?

1.5.2.1.4. What about breadcrumbs?

1.5.2.1.5. How do you expect people to flow through your website?

1.5.2.1.6. Are there well-organized sections of content?

1.5.3. Duplicate content

1.5.3.1. Using rel="canonical" to avoid duplicate content flags

1.5.4. Sitemap

1.5.5. ATTRIBUTE WEIGHT IN MAGENTO

1.5.5.1. how likely Magento will return a match from that attribute

2. 1.2 SECURITY

2.1. USER DATA SECURITY STANDARDS IN DIFFERENT MARKETS

2.1.1. Different security standards for EU, USA and Canada

2.1.1.1. EU data privacy states - you cannot store most any customers data outside the EU

2.1.2. EU COOKIE LAW

2.2. PCI STANDARDS AND PROCESSES

2.2.1. PCI SAQ - a detailed piece of info to assess whether we and our website are following best security practices

2.2.2. Cardholder date must not ever be stored or transmitter unencrypted

2.2.3. Unencrypted data must not be seen by unqualified individuals

2.2.4. Encrypted cardholder data is still subject of safety measures

2.3. PA-DSS / PCI-DSS rules and practices

2.3.1. Every organization that handles credit cards needs to comply with PCI DSS

2.3.1.1. Build and maintain a security network

2.3.1.2. Protect cardholder data

2.3.1.3. Implement strong access control measures

2.3.1.4. Ensure the maintenance of information security policies

2.3.2. Vendors that make and sell payment applications need to meet PA DSS

2.3.3. PA-DSS VS PCI-DSS

2.3.3.1. PA-DSS -> VALIDATING COMPLIANCE OF A SYSTEM OR PROGRAM

2.3.3.2. PCI-DSS -> VALIDATING OF AN ORGANIZATION (PEOPLE+SYSTEMS+HARDWARE)

2.3.4. PROCESS OF GETING CERTIFIED AS PCI COMPLIANT

2.3.4.1. 1. Determine merchant level

2.3.4.1.1. Visa

2.3.4.1.2. MasterCard

2.3.4.2. 2. Determine the SAQ

2.3.4.3. 3. Complete the SAQ

2.4. SSL USAGE

2.4.1. When transmitting cardholder, SSL is a must

2.4.2. PREFERENCE - TLS1.2

2.4.3. Browser vendors - forcing all sites to switch to HTTPS

2.5. BEST PRACTICES

2.5.1. 1. Don't store cardholder/sensitive data -> option save credit card gone from M2

2.5.2. 2. Take care of who handles cardholder data

2.5.3. 3. Use HTTPS

3. 1.3 UX

3.1. GOOD UX

3.1.1. Max of 5 options

3.1.2. Important to give the user context of their position on the website

3.1.3. Clear header navigation (dropdowns if possible)

3.1.4. Breadcrumbs

3.1.5. Good detail in footer

3.1.6. CLEAR CALLS TO ACTION

3.1.7. ENOUGH WHITESPACE TO SET APART IMPORTANT ELEMENTS

3.1.8. CART LINK OBVIOUS

4. 1.4 LAWS AND REGULATIONS

4.1. DISABILITY COMPLIANCE ISSUES

4.2. PRIVACY

4.2.1. Privacy policy

5. 1.5 SYSTEM DEVELOPMENT

5.1. AGILE, SCRUM, WATERFALL

5.1.1. WATERFALL

5.1.2. AGILE

5.1.3. SCRUM

5.1.4. DIFFERENCE BETWEEN WATERFALL AND AGILE

5.1.4.1. WATERFALL - COMPLETELY FINALIZE THE PRODUCT BEFORE SHIPPING

5.1.4.2. AGILE - MORE SHIPPING, MORE DEPLOYMENTS, THE PRODUCT DOESN'T HAVE TO BE POLISHED

5.2. Basic terms and core constituents of system development life cycles

5.2.1. Identify Current Problems

5.2.2. Plan

5.2.3. Design

5.2.4. Build

5.2.5. Test

5.2.6. Deploy

5.2.7. Maintain

6. 1.6 OMNICHANNEL

6.1. Complex inventory management

6.2. Drop ship

6.3. Buy online / ship to store

7. 1.7 DATA ANALYTICS AND TESTING

7.1. Google universal analytics

7.2. A/B testing

7.2.1. Shows customers A(original) or B(updated) version - what users prefer

7.2.2. Next step - multivariate testing

7.3. Optimization

7.4. Personalization

7.4.1. Using customer's name

7.4.2. Showing product they are interested in

7.4.3. Adjusting sales emails

8. 1.8 TAXES

8.1. VAT (VALUE ADDED TAX)

8.2. DIGITAL VAT

8.3. IN-STATE AND OUT OF STATE

8.3.1. In-state ->from one state in the US to the same state (TX to TX)

8.3.2. Out-of-state -> form one state in the US to another state (TX to KS)

8.4. CROSS-BORDER

8.4.1. From one country to another (Italy to Serbia)

9. 2.1 BASIC CONCEPTS

9.1. MVC

9.1.1. MODEL - DATA

9.1.2. VIEW - HOW DATA IS PRESENTED

9.1.3. CONTROLLER - LINK BETWEEN M&V ; BUSINESS LOGIC

9.2. DATABASE SHARDING

9.2.1. Only for EE

9.2.2. SHARDING - splitting up DB into multiple shards (broken glass)

9.2.3. Allows better performance and scalability in diff configurations; DB can be split

9.2.3.1. SPLIT -> checkout orders

9.2.3.2. SPLIT-> products

9.3. VARNISH CACHE

9.3.1. Reverse proxy caching engine

9.3.2. sits in front of web server

9.4. TEMPLATES IN M2

9.4.1. Contain the HTML

9.4.2. PHP & HTML

9.4.3. Accepting PHP objects and render them as HTML

9.5. LAYOUTS IN M2

9.5.1. XML files containing instructions for what to show, where + how to show it

9.5.2. Layout XML files -> merged for specific pages

9.5.3. Customizing the page

9.6. EXTENDING MAGENTO 2 FUNCTIONALITY

9.6.1. determine what needs to be changed

9.7. ENABLING AN EXTENSION

9.7.1. Modules -> not big; Single Responsibility Principle

9.7.2. Files for extensions

9.7.2.1. REGISTRATION.PHP

9.7.2.2. ETC/MODULE.XML

9.7.2.2.1. Commands

9.7.3. AFTER COMMIT

9.7.3.1. PEER-REVIEW

9.7.3.2. QA

9.7.3.3. DEPLOY TO PRODUCTION

9.8. CONFIGURING SITE DESIGN TROUGH ADMIN PANEL (CONTENT>DESIGN>CONFIGURATION)

9.8.1. select store/theme combination that you wish to work with -> click EDIT

9.8.1.1. specific from theme to theme

9.8.1.2. adding config to this area is still not the easiest

9.9. INSTALLING AND ENABLING/DISABLING MAGENTO 2 EXTENSIONS

9.9.1. review code - possible security vulnerabilities

9.9.2. STEPS

9.9.2.1. SSH to server

9.9.2.2. copy files of new module

9.9.2.3. BIN/MAGENTO MODULE:ENABLE ((Module_name))

9.9.2.4. BIN/MAGENTO SETUP:UPGRADE

9.9.2.5. BIN/MAGENTO SETUP:DI:COMPILE

9.9.2.6. BIN/MAGENTO SETUP:STATIC-CONTENT:DEPLOY

9.9.2.7. BIN/MAGENTO CACHE:CLEAN

10. 2.2 MAGENTO API-S AND THIRD PARTY INTEGRATION

10.1. TYPES OF API

10.1.1. REST

10.1.1.1. URL and HTTP code based

10.1.2. SOAP

10.1.2.1. XML based

10.2. API AUTHENTICATION

10.2.1. Thir party app - OAuth 1.0a

10.2.2. For mobile - tokens

10.2.3. Administrators and customers - login credentials

10.3. API USERS

10.3.1. Same as a user if you're using token-based auth

10.4. Differences between M1 and M2 integration options

10.5. THIRD-PARTY INTEGRATION WITH MAGENTO 2 CE AND EE

10.5.1. EE additional API endpoints

10.5.1.1. Customer Balance

10.5.1.2. Gift card account

10.5.1.3. Gift registry

10.5.1.4. Gift wrapping

10.5.1.5. Reward

10.5.1.6. RMA

11. 2.3 MAGENTO WEBSITES, STORES AND STORE VIEWS

11.1. WEBSITE/STORE/STORE VIEW

11.1.1. WEBISTE - store_website table

11.1.1.1. Products are assigned to website

11.1.2. Store - store_group table

11.1.3. Store view - store table

11.1.3.1. To configure

11.1.3.1.1. Pricing

11.1.3.1.2. Attributes

11.1.3.1.3. +more for categories and products

11.2. THE APPLICATION OF SCOPE TO WEBSITES, STORES AND STORE VIEWS

11.2.1. Websites and store groups - similar in functionallity

11.2.2. Three scopes (STORE > CONFIGURATION)

11.2.2.1. Global scope

11.2.2.2. Website scope

11.2.2.2.1. Payment and shipping methods

11.2.2.3. Store view scope

11.2.3. You can switch language on one website

11.3. DISPLAY OF PRODUCT CATALOGS IN WEBSITES, STORES AND STORE VIEWS

11.3.1. NOT IN A SINGLE-STORE MODE (Stores > Configuration > General > Single-Store Mode)

11.3.1.1. Products > assigned to website - if not assigned to website, not visible

11.4. ADMINISTRATION OF WEBSITES, STORES AND STORE VIEWS

11.4.1. Stores > All stores

11.5. LOCALIZATION, TAXES AND PRICING IN WEBSITES, STORES AND STORE VIEWS

11.5.1. These are customized in websites and store views (not for a store)

11.6. PRODUCT ATTRIBUTE SCOPE

11.6.1. Applies to

11.6.1.1. Global

11.6.1.1.1. Store view will not be change the value

11.6.1.2. Store view

11.6.1.2.1. Depending on store's scope

12. 2.4 MAGENTO EDITION DIFFERENCES ENTERPRISE VS COMMUNITY

12.1. Advantages and disadvantages of each edition

12.1.1. ENTERPRISE EDITION ADVANTAGES

12.1.1.1. Has support

12.1.1.2. a lot of pre-built modules that will save dev time

12.1.1.3. DATABASE SCALABILITY

12.1.1.4. Advanced search

12.1.1.4.1. SOLR

12.1.1.5. JOB QUEUE opportunities Message Queues

12.1.1.5.1. Rabbit MQ

12.1.1.6. Google tag manager support

12.1.1.7. Extended admin rights management features / Additional admin logging

12.1.1.8. Ability to manage customer attributes and create custom customer attributes

12.1.1.9. Scheduled FTP/SFTP transfer via XML

12.2. CACHE, INDEXING, SEARCH AND OTHER FEATURE DIFFERENCES

12.2.1. No diff between CE and EE caching, other then the use of message queues(RabbitMQ)

12.2.2. Same with indexes

12.2.3. Solr available, will be changed to Elastic Search

13. 2.5 MAGENTO CLOUD

13.1. INTEGRATION - testing and development

13.2. STAGING - db, env variables, configurations and Fastly

13.3. PRODUCTION - a three node high-availability system

13.4. ADVANTAGE > Magento manages it

14. 2.6 MAGENTO SOLUTIONS

14.1. Bluefoot

14.1.1. CMS > integrated into EE

14.1.2. High quality WYSIWYG editor; drag and drop widgets

14.2. B2B

14.2.1. For B2B transactions

14.2.2. Provides

14.2.2.1. System for quoting

14.2.2.2. Managing groups of customers

14.2.2.3. Better inventory mgmt

14.3. Magento Business Intelligence

14.3.1. reports

15. 2.7 SEARCH ARCHITECTURE

15.1. SOLR

15.2. Elasticsearch

16. 2.8 INFRASTRUCTURE REQUIREMENTS

16.1. Can work with only

16.1.1. PHP

16.1.2. Apache/Nginx

16.1.3. MySQL

16.2. For better preformances

16.2.1. VARNISH

16.2.2. REDIS - for sessions and caching

16.2.3. Memcached

16.3. DB SHARDING

16.3.1. Cannot write directly to DB (usage of DB interface, better practice)

16.3.2. cannot use JOINs that affect sales or quote db