Commerce Plugin - interest?

[BenSeitz]

@plaidpowered

When it comes to plugin structure (assuming it’s just a standard plugin in the plugins folder, not a separate panel, which is still an option), what would be better: [1] one plugin where we drop all the core & 3rd party submodules into, (the plugin’s index could auto-load the modules) or [2] multiple plugins in Kirby’s plugin folder (so there would be a Cart plugin, a Checkout plugin, an Orders plugin, all completely independent of each other)?

Since the sub-kart-plugins would need kart it would make more sense to have them within the kart folder and not in the standard plugin folder, wouldn’t it?

So installation could be as follows:
You drop the kart folder in the plugin folder (or a git submodule) - then go to the panel, open the hamburger menu, select “Shop” which would copy the blueprints and templates into the site folder

PS: no matter whats the name for the plugin, I would really recommend white labeling the panel plugins (Calling it Shop or E-Commerce). It’s called “Panel” and not “Kirby” - that’s one of the many beauties of kirby CMS: No logo, no name, nowhere in the panel.

[distantnative]

While products, categories and so on can be represented by pages – where would we store global kart settings such as VAT sets, general settings?

[texnixe]

I agree, it’s really one of the smallest problems to copy a few files or folders into the right places. I don’t think we want to end up with the mess we have in Wordpress, Joomla and Co. where the files are all over the place which makes it difficult to handle. let alone getting it ready for production …

[BenSeitz]

@distantnative

While products, categories and so on can be represented by pages – where would we store global kart settings such as VAT sets, general settings?

in some sort of config file - and (if the customer needs to change it) with a special panel plugin.

[plaidpowered]

@distantnative

While products, categories and so on can be represented by pages – where would we store global kart settings such as VAT sets, general settings?

I would assume this gets dropped into Kirby’s config folder. There’s already config.php in there, there could be a kart.php too. That way a developer could manage it by hand, or through the panel.

Edit: ninja’d by @BenSeitz

[plaidpowered]

I think the discussion has already proven that one plugin, with optional child modules, is the best structure. (Not the least of reasons: for easy de-installation) Now to decide if it’s going to be a standard Kirby plugin, or a separate panel.

[distantnative]

@BenSeitz

and (if the customer needs to change it) with a special panel plugin.

I’d say you really want to set it up and change it through the panel. I’m thinking about, when it comes to coupon codes and things like this, you don’t want to manage this through editing a config file

[distantnative]

@plaidpowered

Now to decide if it’s going to be a standard Kirby plugin, or a separate panel.

If it can be realized through the panel hooks coming in next releases, I’d go for standard plugin and living inside the Kirby panel as @BenSeitz described.

[BenSeitz]

@plaidpowered

Now to decide if it’s going to be a standard Kirby plugin, or a separate panel.

I vote for standard Kirby plugin - or mydomain.com/shop would automatically go into the shop folder - which wouldn’t be ideal

[plaidpowered]

@BenSeitz

I vote for standard Kirby plugin - or mydomain.com/shop would automatically go into the shop folder - which wouldn’t be ideal

@distantnative

If it can be realized through the panel hooks coming in next releases, I’d go for standard plugin and living inside the Kirby panel as @BenSeitz described.

This is definitely my preference too.

[BenSeitz]

maybe we can get a special category in this forum - i think there will be a lot more discussions

PS: Or you could register an domain and we get our own forum?

[plaidpowered]

Yeah no kidding. I think I’m going to have to make my own development forum eventually. For now, I did make a github repo, if you want to start posting Ideas / Suggestions in the Issues area.

https://github.com/getkart/kart/issues

I’ll set up a domain & forum eventually. In these early stages, I do think having a thread on the Kirby forum is valuable, I want to get as many thoughts, concerns and ideas as possible from the developers who will actually be using it.

[BenSeitz]

Should Kart be usable without the panel?

[plaidpowered]

@BenSeitz

Should Kart be usable without the panel?

In keeping with the Kirby spirit, I think it should. Configuration and content should all be manageable through a standard text editor, the Kirby Panel extensions would just be “bonus”.

[BenSeitz]

@plaidpowered

the Kirby Panel extensions would just be “bonus”

I would love that a lot

[BenSeitz]

Should Kart use Kirby’s users and roles or have it’s own customer management?

[distantnative]

For the customer module (as in registered customers) I think we could use Kirby’s users with a special role

[BenSeitz]

Since you need to save a lot of information with a customer (shopping cart, adress, …) this would only work if by then user roles can have custom fields.
And: Changing the username (without creating a mess) wouldn’t be possible, which would be bad user experience.

[plaidpowered]

@BenSeitz

Since you need to save a lot of information with a customer (shopping cart, adress, …) this would only work if by then user roles can have custom fields.And: Changing the username (without creating a mess) wouldn’t be possible, which would be bad user experience.

I haven’t done much with Kirby user roles. On all the sites I’ve done, everybody is an admin. So I guess we’ll see what 2.1 brings before we write the customer module?

[BenSeitz]

@plaidpowered Yeah, sounds good to me.

On the other hand I like the idea of handling customers separated from users

• It feels more secure
• creating a new role needs to be done in the config.php (makes (de)installment more complicated)
• since theres a whole lot of customers managing them must be different from managing users…