Jump to content
Kuuzu Forum

Recommended Posts

Hi Frank,

Happy to help in anyway I can. I’m not a developer or coder but I do run businesses that operates several e stores so my approach will be from the end user prospective.

I have already posted my views on the main forum but for clarity I’ll list them here again.

For me as a user,

1) Clean start with no legacy issues.

2) Totally modular design

3) Core code is made closed (no messing with it) use addons

4) Review how we make it responsive (bootstrap or alternative?) bootstrap works but is not the only option.

5) Totally integrated modification function. As and when updates to the core are made by the team they are pushed out and available in admin. User simply presses install and core is updated. (already available in opencart)

6) Totally integrated addon function. Same as 5 above but for addons. Both paid and free ( should consider the option of approved free addons and none approved) ( already available in opencart) Quality control will give a much better experience to the end user.

7) Store side editing function. A simple way to let you make changes to the store front with out needing to edit files.

😎 Data import capability. The only way to make it successful is if we make it easy for people to move to it from another osC versions or other carts.


As has already been mentioned every new project starts with good intentions, the challenge will be to stick to them.

Many have attempted similar projects before and make the mistake of becoming another “me to” product as its the quick and easy option.

We will need to offer something unique if we are to stand any chance of gaining traction in a very crowded market. In my opinion and “please do not take offense as none is intended” the mistake made by many of these “me to” carts is they just copy the previous “in trend” cart and add one or too extras features!

We need to start with the customer and only the customer as the main focus. The code is very important but its of no use to anyone without customers. I am sure we could produce beautiful tight super efficient code. The customer will never know this and many don't care as they will never see it. The only thing the customer will care about is what he sees when he installs and what the cart allows him to do. Its this out of the box experience that should be a key target for the project.

A quick example from my recent experience as I have just updated all by stores.

I looked at several alternatives. One stood out from all the others, this was open cart. As an out of box experience it won hands down. Why? It just looked very professional straight out of the box.

Let me know what required and if I can help I will. Help with funding in not out of the question just need to see a bit more meat on these fresh new bones.

 

Zahid

 

Share this post


Link to post
Share on other sites
Quote

Clean start with no legacy issues.

This means different things to different people. I don't think it means that we have to sit down with a blank sheet of paper and reinvent everything. We can certainly borrow ideas, algorithms, and even lots of code from existing projects (e.g., osC 2.4), without having to maintain any compatibility with that implementation. Is that the intent?

Share this post


Link to post
Share on other sites

It simply staring with an open mind with no preconceptions that this or that way is the best. What we can use from other projects is not an issue at the early stages. That can be dealt with by the team leaders as and when they get started.

We need a blank sheet of paper to allow all everyone's to freely input ideas as many as possible. But then its only my point of view, hopefully we will have many others and from these find that kernel we can convert to a killer cart.

Share this post


Link to post
Share on other sites

@JcMagpie  That's the right approach, but let's extend it just a bit further. Yes, Kuuzu is primarily a shopping cart, but there are many more things that may be needed to complement that. Our store may also want to have information pages, a blog, tutorials, maybe a forum.... We may even have store owners who just want a product catalog and no cart. I propose that we go beyond a killer cart and think about a killer framework that  can accommodate all of these things and more.

If you're going to think big....

Regards

Jim

  • Like 2

Share this post


Link to post
Share on other sites

As I proposed before, think about providing shopping modules (catalog system, cart/checkout -- use either or both) that can be plugged into any framework. Kuuzu would provide a simple framework for a store-only site, but developers could create more elaborate frameworks where Kuuzu shopping modules could be plugged in, along with compatible forum, blog, gallery, etc. modules. The idea would be that all these modules use the same theme/skin system, same common routines, site-wide login, etc., etc. It wouldn't necessarily be a full blown CMS, but a lightweight CMS (if you prefer to develop pages that way, and keep them in a database) could be something else plugged into the framework.

Share this post


Link to post
Share on other sites

@MrPhil

CMS and shopping cart are two different things serving two different purposes. This is a problem with Woocommerce -- it is a CMS with shopping engine bolted on.

I have in mind a core where everything else is an app and app is extended with plugins. Main apps I envisage will be Shop and Admin. Forum, CMS, CRM and anything else can then be added in as separate apps if required.

In any case, whole thing has to be carefully designed to allow for maximum flexibility in the future.

Rudolf

  • Like 3

Share this post


Link to post
Share on other sites

I didn't say that a shopping cart was a CMS. What I'm proposing is that we not build this thing as a standalone owns-the-site shopping cart (like the current osC), but as plug-in modules put into a framework. A module to run a catalog (database, search, display) and a separate module to handle a shopping cart, checkout, shipping, and payment. You could mix and match, depending on your needs. You can have a catalog-only site, without the overhead of the cart, or you can roll your own catalog pages with an "add to cart" or "buy now" button. Kuuzu would supply a simple store-only framework (with login and basic formatting functions), but these modules could be plugged into a more elaborate framework along with blog, forum, gallery, etc. modules.

The way that Content Management Systems are currently implemented leaves a lot to be desired (in my eyes). Your pages are generally some sort of HTML/template hybrid, stored in a database. The problem is, to get almost anything useful done, you need to have custom PHP code glued on to your framework. I'm not sure that overall it's any great improvement over just writing standard PHP pages that use a common library of utility functions, templating, etc.

Maybe we're actually talking about the same thing, and just having a violent agreement?

  • Like 1

Share this post


Link to post
Share on other sites
22 hours ago, Kymation said:

@JcMagpie  That's the right approach, but let's extend it just a bit further. Yes, Kuuzu is primarily a shopping cart, but there are many more things that may be needed to complement that. Our store may also want to have information pages, a blog, tutorials, maybe a forum.... We may even have store owners who just want a product catalog and no cart. I propose that we go beyond a killer cart and think about a killer framework that  can accommodate all of these things and more.

If you're going to think big....

Regards

Jim

The more flexible we are the more likely it is that people will want to migrate over. In my experience it pays to keeps doors open. A good strong flexible core that allows us to expand as and when required.

If we agree and allow for that in the design form the very start we really have nothing to lose and a lot to gain. CRM is key to many business as many plug into suppliers data. Also lets not forget accounting and tax/Vat returns. Not sure about other places by in the UK the tax office implement XML a few years ago, The ability to output store data in xml have ability to talk to main accounting software are just a few things.

Lets not forget the selling side,

Auto generate marketing emails for special offers?

Improved mailing support.

Oh and lets have some decent graphics capability, the current images are not a good selling point. People buy with there eye and having poor images an issue.

We should be able to have good quality large images gallery which are easy to mange on the admin side.

I am sure others will have many other ideas to add to this, so yes lets extend it as far as is necessary to get a good product.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×