gacelita / ventas Goto Github PK

Publish the internal ansible playbook used for the demo server, and document deployment in general.

Customers should be listed properly in the administration.

WS API requests should have an option to be "realtime", in the sense that they should return results as they are available (think Datomic or ES queries). This is partially implemented but not used or finished. Quite trivial to be honest, just needs to be used somewhere (most likely, the administration).

Handle login/register for unregistered users, handle entering addresses, handle choosing a shipping method, handle choosing a payment method...surely you've seen this many times :)

There are almost no tests. Shame on me.

how to build the apps with shadow-cljs? any instruction detail? thanks

Most likely the user profile pages in the frontoffice are broken in one way or another. Fix them and add the missing pieces. Take a look at existing and popular ecommerce stores to get an idea of what's missing.

Allow users to ask questions to the store.
Task includes administration section (list pending questions and past threads) and frontoffice section (customer support button that sends the user to the customer support page, which has a form that lets him/her contact the store).
See other ecommerce platforms for references.

Allow creating product variations from the product page. Allow listing the product variations for a given product. Etc

As a bare minimum this should support importing and exporting products to/from Prestashop, Magento and WooCommerce. Not familiar with Shopify but it would be a good idea too.

Reviews should contain "title", "description", "images" and "rating" fields. The plugin should show the reviews for a product in the product page, and allow the user to do basic CUD operations (create, update, delete) on their own reviews. An administration section should be added for listing the reviews. Reviews should be able to be moderated by a privileged user.

Make what's currently developed for the :clothing theme look nice in a typical smartphone (mine's a Samsung Galaxy Grand Prime if you need a reference).

The priority is Stripe.

Hiya,

(migrate-and-reindex!) works partially on my machine.

Here's a repl session dump:

https://gist.githubusercontent.com/vemv/f1ef0f581e662718417d0837967e5a12/raw/95ebeaef691495703bda6148681f21540f0a796f/-

Two highlights:

• DEBUG [org.elasticsearch.client.RestClient:59] - request [DELETE http://127.0.0.1:9200/ventas] returned [HTTP/1.1 404 Not Found] (migrate-and-reindex!)
• INFO [ventas.database.seed:88] - Installing plugin :slider
  clojure.lang.ExceptionInfo: Response Exception

Environment context:

• No Docker
• running plain transactor ~/ventas/datomic/config/transactor.properties and elasticsearch with no prior setup other than a stock install.

What could it be going on?

Allow creating many independent stores with just one ventas instance.
Each should have its database and its Elasticsearch index.

• Get the host from the ring request
• The configuration should have a :multisite key, which should list the configurations for the available sites.
• Use the database and index from the corresponding configuration to serve the request.

ventas should have the option to automatically handle the stock when an order is confirmed. Right now there isn't even a stock field in the products :).
Caution: this should take into account the product variations.

The dashboard should show items that need attention from the store's owner: pending customer questions, pending reviews to approve, pending orders to confirm / ship, and products that are marked as shipped but haven't arrived yet (whenever tracking info is available)

In the administration, there should be a section showing the current state of the background tasks.

Current background tasks:

• Elasticsearch indexing
• Image resizing
• Prerendering

The administration section should list these tasks and allow:

• Seeing the number of items processed vs the total number of items
• Resetting (removing anything already processed)
• Starting and stopping

Spotted by CIDER.

Does *w-o-r* work for you?

Although there are plugins, they don't do anything. They should allow conditional activation of optional features (endpoints, entity types...). The administration should allow this. The fixtures and migrations of the plugins should be handled automatically.

Remove :clothing theme hardcoding. Allow changing the current theme both in development and in production.

Create a component for adding a "Products in the same category" panel to the product page

Ordered by feasibility / amount of work needed

In the Clojure side:

• the timbre logger, which is very nice (ventas.logging)
• ventas.database.entity pseudo-orm-thing (possibly taking things from the other ventas.database namespaces)
• utils.images but crediting optimus-img-transform for the foundational work

In both sides:

• server.ws, which provides a req/response websocket abstraction

In the ClojureScript side:

• ventas.routes bidi generator
  UPDATE: https://github.com/JoelSanchez/ventas-bidi-syntax
• components.notificator
• components.form, but it needs to handle more inputs/use-cases
• the slider component, but it needs to be a lot better
• the chartjs wrapper, but it needs to be a lot better
• the swagger-like thing (ventas.plugins.api)

For the future:

• datadmin idea
• the stripe component/integration

For each image I get a 500:

javax.imageio.IIOException: Can't read input file!

Perhaps they're Docker-only atm?

Email templates, email sending, email log

Mainly for SEO purposes, see prerenderer

Right now there are at least 2 CSS issues with the websocket web tool:

• Responses that are too long don't overflow correctly (click on products.list and see what happens)
• Spec documentation shows \n instead of newlines

I'm leaving this issue undone for now, as it's very beginner friendly.

Add or create a zoom component for the main image in the product page, similar to other online stores

Just add and apply these two plugins to have consistent formatting between contributors.

Right now it's useless, as it only lists entity transaction events. The activity log should register more events and describe properly the ones it already registers.

For entity creation, a link to edit the entity could be provided, along with what data it included when it was created.

Same for updates: show what was updated. Show the time when this happened.

Both creation and update events should be far more semantic. If an user is created, is it because a user was registered? Or something else?

Simply, orders should be listed properly in the administration.