Is it possible to make an online store without knowledge of php?

Question

CMS

Hello! Beginning maker! Now I am offered an order for an online store with online payment, a shopping cart and customer registration (this item is still in question). Is it possible to implement such functionality without knowledge of php? I read that there are some plugins in WP and so on, is it possible to do this with the help of them?

Answer 1

It can be built on a CMS to make it work. But it is better to refuse if you have never done it.

Answer 2

Is it possible to implement such functionality without knowledge of php?

Without knowledge of any of the server languages, this is impossible

Answer 3

If you need to sell your products, then a bunch of service as a service in the business-to-business segment of turnkey solutions. Google an online store in (5)15 minutes

Answer 4

It is possible without knowledge if you pay someone who knows, otherwise you will have to study to some extent

Answer 5

In your case, there are only two reasonable alternatives:

• Refuse
  
• Become an intermediary, and either simply order work on the side, or do the layout part, and give the rest to a subcontractor. And we must understand that the organization of the project is also difficult, so the first option is more reasonable.
  

Answer 6

1) everything is simple, do not use git for deployment (git pull on the server), there are other things for this, capistrano, capifoni, etc.
As for the differentiation of rights, everything is also simple here, just make two repositories, one has the right to push everything and the other - the one that is prod or something like that, only you (or someone in charge), and make it a separate origin. Then the rights will be completely separated and you will be able to make decisions about what goes to the server and what does not.
2) you can put actions on push hooks in bitbucket, for example, to pull your CI-ku, run tests there (do you write tests?) and deploy. Then, in order to roll out the version, you just need to do a git push, and then magic. Well, again, if we divided the repositories into separate origins, we can also control who can deploy and who can't.

Answer 7

Use GIT Flow .

Answer 8

Speaking purely conceptually, there should be a main branch (Release), and brunches for a specific task should be made from it. When the task is ready, merge with the main branch. This is one approach, and by no means the only one. In your case, you can make a release, branch test from it, and branch further from the test into tasks. When the task is ready - pour it into the test, after the tests - release. 1 requirement - prohibition of merging directly into the release past the tests.

Answer 9

git flow for branches, jenkins for deployment.