Next-generation WordPress eCommerce Experience for WordPress sites at Newfold Digital.
- Ecommerce module displays
Home or Dashboard
page for Brand plugin, with below options:- Live site preview for both, live and coming soon mode for WordPress site with view & edit site options
- Next steps to setup your site helps customers to complete below tasks:
- To add store info
- Setup online payment options like PayPal, Stripe, RazorPay. Also choose offline payment options like, check payments, bank transfers & C.O.D
- Setup shipping options like Shippo.
- Configure tax settings
- Add/import products
- Customers who have selected
novice
as WordPress experience level will have access to Signup to BlueHost WP academy / Yoast academy for learning purpose. - There is also link for Customers to view list of
Completed tasks
- Ecommerce module also displays
Store
option which gives snapshot of recent customer activity with details like total sales, net sales, recent orders, products sold, visitors, views and also a link to detailedAnalytics
page of Woocommerce plugin. Store
page also, allows customers to Purchase/Enable/Manage and learn more about YITH extended plugins like:- YITH Booking and Appointment for WooCommerce
- YITH WooCommerce AJAX Search
- YITH WooCommerce Gift Cards
- YITH WooCommerce Wishlist
- YITH WooCommerce Customize My Account Page
- YITH WooCommerce Ajax Product Filter.
- Under Store we have a
Products & Services
submenu option which provides following options:- Easy access to Add new product/Import CSV of products into your store.
- Option to setup bookings & appointments or offer gift cards on purchases via YITH extended plugins.
- Next submenu under Store is
Sales & Promotions
where customer can setup different promotional offers on products in their store.- Here we display 13 different campaign setup options offered by
WonderCart
plugin underAll Campaigns
tab. - There is also a
Settings
tab where users can customize look & feel of how sales campaigns are displayed on their Store page.
- Here we display 13 different campaign setup options offered by
- Next submenu under Store is
Payments
where we store owner can setup payments option accepted on purchases at Store.- There 3 online payment options via payments gateways like PayPal, Stripe & RazorPay(only for India location).
- We also offer offline payments option via cheque, bank transfer or cash on delivery.
- Final submenu under Store is
Store details
with following options:- Store location and complete address, email address of store owner and currency in which products/services are displayed on the store.
- Under
shipping option
tab on the store details page you can connect to Shipping partner like, Shippo (based on your store location). - Under
tax settings
tab, store owner can choose to enable/disable sales tax.
Store
page should give a brief overview ofrecent customer activity
on Ecommerce website.Store
page displays section to setupEcommerce features
where users can purchase/enable/manage YITH extended plugins.- It is required to install & activate
WooCommerce
plugin for below plugins to work,YITH PayPal Payment
plugin for - facilitating payments via PayPal,WonderCart
plugin for - creating sales & promotional campaigns,YITH Stripe Payments
plugin for - facilitating payments via StripeEcomdash
plugin for - managing marketplace and ecommerce website sales.
Home
page should display warningsenabled but not effective, requires WooCommerce in order to work.
for above YITH plugins, incase WooCommerce isn't setup.- If
WooCommerce
plugin isn't setup,Store
tab should ask users to first install & activateWooCommerce
till then all the sub-menu options underStore
menu should be disabled. Products & Services
tab should provide customers access to purchase services offered by YITH extended plugins like: YITH Booking and Appointment for WooCommerce and YITH WooCommerce Gift Cards.Sales & Promotions
submenu allows customers to installWonderCart
plugin if it is not already installed & activated. OnceWonderCart
is activated it offers option to setup different promotional campaigns.Payments
tab facilitates Customers to connect their accounts to receive payments via popular online payment options like PayPal, Stripe and RazorPay. Customers can also choose to accept offline payment via options like: check payments, bank transfers & C.O.D.Store details
tab facilitates setup ofShippo
third party shipping software for e-commerce businesses.
composer config repositories.newfold composer https://newfold-labs.github.io/satis
composer require newfold-labs/wp-module-ecommerce
Follow instructions at GH Packages Setup.
npm install @newfold-labs/wp-module-ecommerce
In your React component you can import the eCommerce module as so,
import { NewfoldECommerce } from "@newfold-labs/wp-module-ecommerce";
function EcommercePage(props) {
return <NewfoldECommerce {...props} />;
}
More on Newfold WordPress Modules
We have switched to GH packages for publishing newer versions of the ecommerce module.
if you're doing something that will not break anything or not adding any new dependency. But, only doing basic stuff like bug fixes, copy changes etc. Change which doesn't really impact the plugin in bigger way you can put them under the last number of versions.
If you're doing something, like adding a new library, or changing something in the way the plugin can use our module then it's better to upgrade the minor version which is the 2nd digit of version.
In rare scenarios, like UI redesign where the change is bigger or a major refactor, we update the 1st digit of version.
-
Merge approved PRs into trunk branch
-
Do version update to new one in package.json
-
Run, npm install (this will auto update version in package-lock.json)
-
Commit above change in separate commit (commit message: Bump to new version value)
-
Go to https://github.com/newfold-labs/wp-module-ecommerce/releases
-
Click on Draft a new release button (Note: Saving as draft, pipeline is not running.)
-
By default, you'll always create a release from target: trunk branch. In case we are making changes to crazydomains then we must switch to the legacy branch do the fixes there and create a release from target: legacy branch as it currently runs older version
-
Give V dot version that you want to release and click on create a new tag.
-
Click Generate release notes button it will basically collect all the pull requests that came in from the previous release to now and then just create a summary. (It won't track any direct comments to the trunk. It will just only track pull request)
-
Keep Set as the latest release checkbox
checked
as it is by default. -
Click Publish a release button.
-
Go to https://newfold-labs.github.io/satis/ Satis is a PHP registry for our packages.
-
On above URL in
package
filter, you can search for ecommerce -
We have set up an integration within our workflow itself so once workflow completes, we trigger alert to Satis that newer version of ecommerce module is released and rebuild Satis so that it can show newer version in packages (Repo: https://github.com/newfold-labs/satis/actions)
-
The newer version will appear in 5 to 10 minutes of rebuilding.
-
We do not have permission to rerun Satis build, so in case it fails PRESS1 team can help.
-
You can check the status of Statis build & Publish workflow here https://github.com/newfold-labs/wp-module-ecommerce/actions
-
On successful completion you can see latest package here https://github.com/newfold-labs/wp-module-ecommerce/pkgs/npm/wp-module-ecommerce
-
In composer.json file, update version of newfold-labs/wp-module-ecommerce
-
In package.json file, newfold-labs/wp-module-ecommerce : version number
-
Run command,
npm i --legacy-peer-deps
-
Package-lock.json should auto update.
-
Once Satis starts showing updated version run below command for composer update,
$ composer update newfold-labs/wp-module-ecommerce -W
-
We need to create a branch (naming convention: dependencies/newfold-labs/wp-module-ecommerce-version_number).
-
Currently we don't have the permission to publish directly to the BlueHost plugin So, we need to create a fork basically of the repo then push it to that fork and then create a pull request against the develop branch.
-
The new release process is thus completed.