Ecommerce Portal Enhancement

[Rishi Solanki]

Devs,

We would like to propose few enhancement over ecommerce portal in OFBiz. In
other words we want to demonstrate how to use ecommerce portal for creating
your own site. Regarding the same, we were looking at some wiki documents
to browse the features already exists and demonstrated by Ecommerce portal.
After browsing all the features we understand from ecommerce site OFBiz
have, that, it covers all the aspects as a framework to demonstrate all the
possible features OFBiz can support for Ecommerce. Also it demonstrate how
these features uses the data model.

So we were thinking to use ecommerce clone to demonstrate our purpose. That
means, how an OFBiz user can create a modern Ecommerce site using the OFBiz
Ecommerce portal. But on further diagnose we found that, the ecomclone have
been removed in last month as result of email thread - *"Removing the
ecomclone webapp from the ecommerce component"*. Also we gone thru the
usage of *ecomseo* webapp and it also use the ecommerce to demonstarte its
own seo related features metioned here
<https://cwiki.apache.org/confluence/display/OFBIZ/Search+Engine+Optimisation%2C+SEO+in+ecommerce>.


With all this said, we would like to use the *ecomseo* for our purpose or
if community is not okay with it then we can add one more webapp parallel
to ecommerce. We are fine in either way. Following are the enhancements we
would like to propose for it, so that we can show an modern ecommerce site
using OFBiz *ecomseo* or *new webapp*.

- *ecomseo* or *new webapp* already cover the search engine friendly URLs
using the SeoControlServlet and SeoCatalogUrlFilter. We just need to make
sure all the features are working properly if we browse to *ecomseo*. As
while browsing we have seen that the breadcrumbs are not working properly
in all cases, also on changing catalogs page doesn't show the related data
in *ecomseo*. So first we will fix all the related issue exists in *ecomseo*
.
- Like many modern ecommerce site, we would like show the catalogs as menu
and category navigation in the menu bar. That means, if required we can set
some data specific to *ecomseo *or* new webapp.*
- *Category Navigation:* should shown from Solr instead of product and
category data.
- *Product Search Pages:* should shown from Solr instead of product
keywords. With all the basic feature filtering criteria.
- *Product Detail Page:* should show the minimum required fixed set of
product features. That means, it does not cover all type of products like
configurable products and other complex products. This also mean that, at
some point we would like to narrow the ecommerce features and keep the
general items required by mostly.
- *Login and Registration:* We would like to add basic site registration
process with minimum information.
- *Shopping Cart:* Shopping cart will have all the basic functionality with
fancy UI and JS support.
- *Checkout:* Only one single page checkout with no steps. Fancy UI and JS
support. It also includes the changes on assumption like by default billing
and shipping address will be same and based on user action process will
separate them.
- *Overall Changes:* With the above basic flow changes on ecommerce, we
would also override the decorators, UI, UX and add JS support to follow the
latest standards.


We would love to hear from community on this, and inputs on other areas if
we missed something. Also if we do agree to do these changes, then we will
start documenting the things one by one in detail on wiki probably with
some wireframes to understand the things better. And after community agree
on each item we can start on fixing the flows as per the final design.

Thanks to Jacques and Pranay for the adding useful documents on wiki. It
help us for identifying the work flows, the usage of apps, and preparing
this basic plan. Thanks to Arun Patidar for discussion and planning.

References:
- https://cwiki.apache.org/confluence/display/OFBIZ/
Search+Engine+Optimisation%2C+SEO+in+ecommerce
- https://cwiki.apache.org/confluence/display/OFBIZ/
Business+Process+Stories+and+Use+Cases+Library
- https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce



--
Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: [phone]
http://www.hotwaxsystems.com

[james_sg]

Hi Rishi,

You can consider the use of microdata or related, for the purpose of SEO.

For further info, see
https://developers.google.com/search/docs/guides/intro-structured-data
https://developers.google.com/search/docs/data-types/products

Regards,
James

Rishi Solanki wrote

Devs,

We would like to propose few enhancement over ecommerce portal in OFBiz. In
other words we want to demonstrate how to use ecommerce portal for creating
your own site. Regarding the same, we were looking at some wiki documents
to browse the features already exists and demonstrated by Ecommerce portal.
After browsing all the features we understand from ecommerce site OFBiz
have, that, it covers all the aspects as a framework to demonstrate all the
possible features OFBiz can support for Ecommerce. Also it demonstrate how
these features uses the data model.

So we were thinking to use ecommerce clone to demonstrate our purpose. That
means, how an OFBiz user can create a modern Ecommerce site using the OFBiz
Ecommerce portal. But on further diagnose we found that, the ecomclone have
been removed in last month as result of email thread - *"Removing the
ecomclone webapp from the ecommerce component"*. Also we gone thru the
usage of *ecomseo* webapp and it also use the ecommerce to demonstarte its
own seo related features metioned here
<https://cwiki.apache.org/confluence/display/OFBIZ/Search+Engine+Optimisation%2C+SEO+in+ecommerce>.


With all this said, we would like to use the *ecomseo* for our purpose or
if community is not okay with it then we can add one more webapp parallel
to ecommerce. We are fine in either way. Following are the enhancements we
would like to propose for it, so that we can show an modern ecommerce site
using OFBiz *ecomseo* or *new webapp*.

- *ecomseo* or *new webapp* already cover the search engine friendly URLs
using the SeoControlServlet and SeoCatalogUrlFilter. We just need to make
sure all the features are working properly if we browse to *ecomseo*. As
while browsing we have seen that the breadcrumbs are not working properly
in all cases, also on changing catalogs page doesn't show the related data
in *ecomseo*. So first we will fix all the related issue exists in *ecomseo*
.
- Like many modern ecommerce site, we would like show the catalogs as menu
and category navigation in the menu bar. That means, if required we can set
some data specific to *ecomseo *or* new webapp.*
- *Category Navigation:* should shown from Solr instead of product and
category data.
- *Product Search Pages:* should shown from Solr instead of product
keywords. With all the basic feature filtering criteria.
- *Product Detail Page:* should show the minimum required fixed set of
product features. That means, it does not cover all type of products like
configurable products and other complex products. This also mean that, at
some point we would like to narrow the ecommerce features and keep the
general items required by mostly.
- *Login and Registration:* We would like to add basic site registration
process with minimum information.
- *Shopping Cart:* Shopping cart will have all the basic functionality with
fancy UI and JS support.
- *Checkout:* Only one single page checkout with no steps. Fancy UI and JS
support. It also includes the changes on assumption like by default billing
and shipping address will be same and based on user action process will
separate them.
- *Overall Changes:* With the above basic flow changes on ecommerce, we
would also override the decorators, UI, UX and add JS support to follow the
latest standards.


We would love to hear from community on this, and inputs on other areas if
we missed something. Also if we do agree to do these changes, then we will
start documenting the things one by one in detail on wiki probably with
some wireframes to understand the things better. And after community agree
on each item we can start on fixing the flows as per the final design.

Thanks to Jacques and Pranay for the adding useful documents on wiki. It
help us for identifying the work flows, the usage of apps, and preparing
this basic plan. Thanks to Arun Patidar for discussion and planning.

References:
- https://cwiki.apache.org/confluence/display/OFBIZ/
Search+Engine+Optimisation%2C+SEO+in+ecommerce
- https://cwiki.apache.org/confluence/display/OFBIZ/
Business+Process+Stories+and+Use+Cases+Library
- https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce



--
Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: [phone]
http://www.hotwaxsystems.com

[james_sg]

More people are shopping with their mobile phones;
Would be good to have responsive web design for ecommerce.

james_sg wrote

Hi Rishi,

You can consider the use of microdata or related, for the purpose of SEO.

For further info, see
https://developers.google.com/search/docs/guides/intro-structured-data
https://developers.google.com/search/docs/data-types/products

Regards,
James

Rishi Solanki wrote

Devs,

We would like to propose few enhancement over ecommerce portal in OFBiz. In
other words we want to demonstrate how to use ecommerce portal for creating
your own site. Regarding the same, we were looking at some wiki documents
to browse the features already exists and demonstrated by Ecommerce portal.
After browsing all the features we understand from ecommerce site OFBiz
have, that, it covers all the aspects as a framework to demonstrate all the
possible features OFBiz can support for Ecommerce. Also it demonstrate how
these features uses the data model.

So we were thinking to use ecommerce clone to demonstrate our purpose. That
means, how an OFBiz user can create a modern Ecommerce site using the OFBiz
Ecommerce portal. But on further diagnose we found that, the ecomclone have
been removed in last month as result of email thread - *"Removing the
ecomclone webapp from the ecommerce component"*. Also we gone thru the
usage of *ecomseo* webapp and it also use the ecommerce to demonstarte its
own seo related features metioned here
<https://cwiki.apache.org/confluence/display/OFBIZ/Search+Engine+Optimisation%2C+SEO+in+ecommerce>.


With all this said, we would like to use the *ecomseo* for our purpose or
if community is not okay with it then we can add one more webapp parallel
to ecommerce. We are fine in either way. Following are the enhancements we
would like to propose for it, so that we can show an modern ecommerce site
using OFBiz *ecomseo* or *new webapp*.

- *ecomseo* or *new webapp* already cover the search engine friendly URLs
using the SeoControlServlet and SeoCatalogUrlFilter. We just need to make
sure all the features are working properly if we browse to *ecomseo*. As
while browsing we have seen that the breadcrumbs are not working properly
in all cases, also on changing catalogs page doesn't show the related data
in *ecomseo*. So first we will fix all the related issue exists in *ecomseo*
.
- Like many modern ecommerce site, we would like show the catalogs as menu
and category navigation in the menu bar. That means, if required we can set
some data specific to *ecomseo *or* new webapp.*
- *Category Navigation:* should shown from Solr instead of product and
category data.
- *Product Search Pages:* should shown from Solr instead of product
keywords. With all the basic feature filtering criteria.
- *Product Detail Page:* should show the minimum required fixed set of
product features. That means, it does not cover all type of products like
configurable products and other complex products. This also mean that, at
some point we would like to narrow the ecommerce features and keep the
general items required by mostly.
- *Login and Registration:* We would like to add basic site registration
process with minimum information.
- *Shopping Cart:* Shopping cart will have all the basic functionality with
fancy UI and JS support.
- *Checkout:* Only one single page checkout with no steps. Fancy UI and JS
support. It also includes the changes on assumption like by default billing
and shipping address will be same and based on user action process will
separate them.
- *Overall Changes:* With the above basic flow changes on ecommerce, we
would also override the decorators, UI, UX and add JS support to follow the
latest standards.


We would love to hear from community on this, and inputs on other areas if
we missed something. Also if we do agree to do these changes, then we will
start documenting the things one by one in detail on wiki probably with
some wireframes to understand the things better. And after community agree
on each item we can start on fixing the flows as per the final design.

Thanks to Jacques and Pranay for the adding useful documents on wiki. It
help us for identifying the work flows, the usage of apps, and preparing
this basic plan. Thanks to Arun Patidar for discussion and planning.

References:
- https://cwiki.apache.org/confluence/display/OFBIZ/
Search+Engine+Optimisation%2C+SEO+in+ecommerce
- https://cwiki.apache.org/confluence/display/OFBIZ/
Business+Process+Stories+and+Use+Cases+Library
- https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce



--
Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: [phone]
http://www.hotwaxsystems.com

[Paul Foxworthy]

On 16 October 2016 at 16:46, james_sg <[hidden email]> wrote:


> More people are shopping with their mobile phones;
> Would be good to have responsive web design for ecommerce.
>

Yes, responsive web design would be a good idea. But it should be done
using theming, so it would be applicable to all of OFBiz and not just
ecommerce.

Cheers

Paul Foxworthy

[Pierre Smits]

The *oshop* solution (and associated *ecbootstrap* theme) are a step in the
direction of bringing ecommerce functions to mobile devices. See:

   - for the *oshop* component:
   https://oem.ofbizci.net/oci-2/products/ecommerce/p_orrtiz-oshop
   - for the *ecbootstrap* theme:
   https://oem.ofbizci.net/oci-2/products/themes/themes-front/p_orrtiz-ecbootstrap

From there on you can link through to the code repos on Github of each.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Oct 17, 2016 at 2:10 AM, Paul Foxworthy <[hidden email]> wrote:

> On 16 October 2016 at 16:46, james_sg <[hidden email]> wrote:
>
>
> > More people are shopping with their mobile phones;
> > Would be good to have responsive web design for ecommerce.
> >
>
> Yes, responsive web design would be a good idea. But it should be done
> using theming, so it would be applicable to all of OFBiz and not just
> ecommerce.
>
> Cheers
>
> Paul Foxworthy
>

[Rishi Solanki]

James, Paul, Pierre,

Thank you for your response, inputs, ideas and references. We do agree to
have responsive UI/UX compatible to most devices especially mobile. Also we
tried to inlist this point in our summary but not clearly. With all the
above mentioned points, we would include the responsive web design in the
list.

Also if anyone can answer on the question, which webapp we should use to
implement all this would be great. *ecomseo* is one option, and adding one
new webapp is another option. We just wated to make sure before proceeding
because, we don't want to override the purpose of an app intended to
demonstrate very specific item. If we use *ecomseo *then we would like to
maintain the SEO and URLs purpose of that application. If not then we will
go for new webapp.

Please suggest. Thanks again for your help!


Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: [phone]
http://www.hotwaxsystems.com

On Mon, Oct 17, 2016 at 12:39 PM, Pierre Smits <[hidden email]>
wrote:

> The *oshop* solution (and associated *ecbootstrap* theme) are a step in the
> direction of bringing ecommerce functions to mobile devices. See:
>
>    - for the *oshop* component:
>    https://oem.ofbizci.net/oci-2/products/ecommerce/p_orrtiz-oshop
>    - for the *ecbootstrap* theme:
>    https://oem.ofbizci.net/oci-2/products/themes/themes-front/
> p_orrtiz-ecbootstrap
>
> From there on you can link through to the code repos on Github of each.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Oct 17, 2016 at 2:10 AM, Paul Foxworthy <[hidden email]>
> wrote:
>
> > On 16 October 2016 at 16:46, james_sg <[hidden email]> wrote:
> >
> >
> > > More people are shopping with their mobile phones;
> > > Would be good to have responsive web design for ecommerce.
> > >
> >
> > Yes, responsive web design would be a good idea. But it should be done
> > using theming, so it would be applicable to all of OFBiz and not just
> > ecommerce.
> >
> > Cheers
> >
> > Paul Foxworthy
> >
>

[Jacques Le Roux]

Hi Rishi,

I prefer we create a new plugin. For 2 reasons:

 1. keep the ecomseo webapp as is
 2. Review the new "create plugin" mechanism

The ecomseo webapp serves 2 purposes.

 1. To create a SEO friendly URLs
 2. To demonstrate the controller include mechanism. If you look at the ecomseo webapp you will see there is nothing specific but the servlets from
    the product component

That why I prefer to have a new plugin. We will then be sure that ecomseo will not be tainted by new things added. And it could be possibly reused in
the new plugin simply as a webapp as it is now in ecommerce, it's not UI related at all, only SEO related.

And it's also a good occasion to create a new component by using the new "create plugin" mechanism. Of course the new plugin will ultimately be a
specialpurpose component, but in the meantime this will help to review the new "create plugin" mechanism and if necessary improve it.

Jacques


Le 17/10/2016 à 10:27, Rishi Solanki a écrit :

> James, Paul, Pierre,
>
> Thank you for your response, inputs, ideas and references. We do agree to
> have responsive UI/UX compatible to most devices especially mobile. Also we
> tried to inlist this point in our summary but not clearly. With all the
> above mentioned points, we would include the responsive web design in the
> list.
>
> Also if anyone can answer on the question, which webapp we should use to
> implement all this would be great. *ecomseo* is one option, and adding one
> new webapp is another option. We just wated to make sure before proceeding
> because, we don't want to override the purpose of an app intended to
> demonstrate very specific item. If we use *ecomseo *then we would like to
> maintain the SEO and URLs purpose of that application. If not then we will
> go for new webapp.
>
> Please suggest. Thanks again for your help!
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: [phone]
> http://www.hotwaxsystems.com
>
> On Mon, Oct 17, 2016 at 12:39 PM, Pierre Smits <[hidden email]>
> wrote:
>
>> The *oshop* solution (and associated *ecbootstrap* theme) are a step in the
>> direction of bringing ecommerce functions to mobile devices. See:
>>
>>     - for the *oshop* component:
>>     https://oem.ofbizci.net/oci-2/products/ecommerce/p_orrtiz-oshop
>>     - for the *ecbootstrap* theme:
>>     https://oem.ofbizci.net/oci-2/products/themes/themes-front/
>> p_orrtiz-ecbootstrap
>>
>>  From there on you can link through to the code repos on Github of each.
>>
>> Best regards,
>>
>> Pierre Smits
>>
>> ORRTIZ.COM <http://www.orrtiz.com>
>> OFBiz based solutions & services
>>
>> OFBiz Extensions Marketplace
>> http://oem.ofbizci.net/oci-2/
>>
>> On Mon, Oct 17, 2016 at 2:10 AM, Paul Foxworthy <[hidden email]>
>> wrote:
>>
>>> On 16 October 2016 at 16:46, james_sg <[hidden email]> wrote:
>>>
>>>
>>>> More people are shopping with their mobile phones;
>>>> Would be good to have responsive web design for ecommerce.
>>>>
>>> Yes, responsive web design would be a good idea. But it should be done
>>> using theming, so it would be applicable to all of OFBiz and not just
>>> ecommerce.
>>>
>>> Cheers
>>>
>>> Paul Foxworthy
>>>

[Jacques Le Roux]

Forgot to suggest that the new plugin could simply start by using the same webapp than ecomseo

Jacques


Le 19/10/2016 à 14:25, Jacques Le Roux a écrit :

> Hi Rishi,
>
> I prefer we create a new plugin. For 2 reasons:
>
> 1. keep the ecomseo webapp as is
> 2. Review the new "create plugin" mechanism
>
> The ecomseo webapp serves 2 purposes.
>
> 1. To create a SEO friendly URLs
> 2. To demonstrate the controller include mechanism. If you look at the ecomseo webapp you will see there is nothing specific but the servlets from
>    the product component
>
> That why I prefer to have a new plugin. We will then be sure that ecomseo will not be tainted by new things added. And it could be possibly reused
> in the new plugin simply as a webapp as it is now in ecommerce, it's not UI related at all, only SEO related.
>
> And it's also a good occasion to create a new component by using the new "create plugin" mechanism. Of course the new plugin will ultimately be a
> specialpurpose component, but in the meantime this will help to review the new "create plugin" mechanism and if necessary improve it.
>
> Jacques
>
>
> Le 17/10/2016 à 10:27, Rishi Solanki a écrit :
>> James, Paul, Pierre,
>>
>> Thank you for your response, inputs, ideas and references. We do agree to
>> have responsive UI/UX compatible to most devices especially mobile. Also we
>> tried to inlist this point in our summary but not clearly. With all the
>> above mentioned points, we would include the responsive web design in the
>> list.
>>
>> Also if anyone can answer on the question, which webapp we should use to
>> implement all this would be great. *ecomseo* is one option, and adding one
>> new webapp is another option. We just wated to make sure before proceeding
>> because, we don't want to override the purpose of an app intended to
>> demonstrate very specific item. If we use *ecomseo *then we would like to
>> maintain the SEO and URLs purpose of that application. If not then we will
>> go for new webapp.
>>
>> Please suggest. Thanks again for your help!
>>
>>
>> Rishi Solanki
>> Manager, Enterprise Software Development
>> HotWax Systems Pvt. Ltd.
>> Direct: [phone]
>> http://www.hotwaxsystems.com
>>
>> On Mon, Oct 17, 2016 at 12:39 PM, Pierre Smits <[hidden email]>
>> wrote:
>>
>>> The *oshop* solution (and associated *ecbootstrap* theme) are a step in the
>>> direction of bringing ecommerce functions to mobile devices. See:
>>>
>>>     - for the *oshop* component:
>>> https://oem.ofbizci.net/oci-2/products/ecommerce/p_orrtiz-oshop
>>>     - for the *ecbootstrap* theme:
>>> https://oem.ofbizci.net/oci-2/products/themes/themes-front/
>>> p_orrtiz-ecbootstrap
>>>
>>>  From there on you can link through to the code repos on Github of each.
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> ORRTIZ.COM <http://www.orrtiz.com>
>>> OFBiz based solutions & services
>>>
>>> OFBiz Extensions Marketplace
>>> http://oem.ofbizci.net/oci-2/
>>>
>>> On Mon, Oct 17, 2016 at 2:10 AM, Paul Foxworthy <[hidden email]>
>>> wrote:
>>>
>>>> On 16 October 2016 at 16:46, james_sg <[hidden email]> wrote:
>>>>
>>>>
>>>>> More people are shopping with their mobile phones;
>>>>> Would be good to have responsive web design for ecommerce.
>>>>>
>>>> Yes, responsive web design would be a good idea. But it should be done
>>>> using theming, so it would be applicable to all of OFBiz and not just
>>>> ecommerce.
>>>>
>>>> Cheers
>>>>
>>>> Paul Foxworthy
>>>>
>
>

[Rishi Solanki]

All,

Thank you for your reply and suggestions. We will discuss this and come up
with summarized details from email thread, on which we can proceed further.
Hopefully in start of next week or in this weekend.

Jacques, I'll check the plugin mechanism and update in the same thread. I
see one thread on this subject, will get back on this asap.

Thanks again for your help.





Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: [phone]
http://www.hotwaxsystems.com

On Thu, Oct 20, 2016 at 12:21 PM, Jacques Le Roux <
[hidden email]> wrote:

> Forgot to suggest that the new plugin could simply start by using the same
> webapp than ecomseo
>
> Jacques
>
>
>
> Le 19/10/2016 à 14:25, Jacques Le Roux a écrit :
>
>> Hi Rishi,
>>
>> I prefer we create a new plugin. For 2 reasons:
>>
>> 1. keep the ecomseo webapp as is
>> 2. Review the new "create plugin" mechanism
>>
>> The ecomseo webapp serves 2 purposes.
>>
>> 1. To create a SEO friendly URLs
>> 2. To demonstrate the controller include mechanism. If you look at the
>> ecomseo webapp you will see there is nothing specific but the servlets from
>>    the product component
>>
>> That why I prefer to have a new plugin. We will then be sure that ecomseo
>> will not be tainted by new things added. And it could be possibly reused in
>> the new plugin simply as a webapp as it is now in ecommerce, it's not UI
>> related at all, only SEO related.
>>
>> And it's also a good occasion to create a new component by using the new
>> "create plugin" mechanism. Of course the new plugin will ultimately be a
>> specialpurpose component, but in the meantime this will help to review the
>> new "create plugin" mechanism and if necessary improve it.
>>
>> Jacques
>>
>>
>> Le 17/10/2016 à 10:27, Rishi Solanki a écrit :
>>
>>> James, Paul, Pierre,
>>>
>>> Thank you for your response, inputs, ideas and references. We do agree to
>>> have responsive UI/UX compatible to most devices especially mobile. Also
>>> we
>>> tried to inlist this point in our summary but not clearly. With all the
>>> above mentioned points, we would include the responsive web design in the
>>> list.
>>>
>>> Also if anyone can answer on the question, which webapp we should use to
>>> implement all this would be great. *ecomseo* is one option, and adding
>>> one
>>> new webapp is another option. We just wated to make sure before
>>> proceeding
>>> because, we don't want to override the purpose of an app intended to
>>> demonstrate very specific item. If we use *ecomseo *then we would like to
>>> maintain the SEO and URLs purpose of that application. If not then we
>>> will
>>> go for new webapp.
>>>
>>> Please suggest. Thanks again for your help!
>>>
>>>
>>> Rishi Solanki
>>> Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: [phone]
>>> http://www.hotwaxsystems.com
>>>
>>> On Mon, Oct 17, 2016 at 12:39 PM, Pierre Smits <[hidden email]>
>>> wrote:
>>>
>>> The *oshop* solution (and associated *ecbootstrap* theme) are a step in
>>>> the
>>>> direction of bringing ecommerce functions to mobile devices. See:
>>>>
>>>>     - for the *oshop* component:
>>>> https://oem.ofbizci.net/oci-2/products/ecommerce/p_orrtiz-oshop
>>>>     - for the *ecbootstrap* theme:
>>>> https://oem.ofbizci.net/oci-2/products/themes/themes-front/
>>>> p_orrtiz-ecbootstrap
>>>>
>>>>  From there on you can link through to the code repos on Github of each.
>>>>
>>>> Best regards,
>>>>
>>>> Pierre Smits
>>>>
>>>> ORRTIZ.COM <http://www.orrtiz.com>
>>>> OFBiz based solutions & services
>>>>
>>>> OFBiz Extensions Marketplace
>>>> http://oem.ofbizci.net/oci-2/
>>>>
>>>> On Mon, Oct 17, 2016 at 2:10 AM, Paul Foxworthy <[hidden email]>
>>>> wrote:
>>>>
>>>> On 16 October 2016 at 16:46, james_sg <[hidden email]> wrote:
>>>>>
>>>>>
>>>>> More people are shopping with their mobile phones;
>>>>>> Would be good to have responsive web design for ecommerce.
>>>>>>
>>>>>> Yes, responsive web design would be a good idea. But it should be done
>>>>> using theming, so it would be applicable to all of OFBiz and not just
>>>>> ecommerce.
>>>>>
>>>>> Cheers
>>>>>
>>>>> Paul Foxworthy
>>>>>
>>>>>
>>
>>
>