Is it worth creating an online portfolio store in pure PHP?

Question

PHP

If I am a beginner web developer, is it worth making an online store for a portfolio in pure PHP, or is it better to develop it right away under CMS? Because, as I understand it, now there are more freelance orders for creating a site specifically for CMSs than for pure PHP? And when applying for a job, knowledge of CMSs is already needed there.

Answer 1

Depending on what you want to demonstrate:
If the ability to program in PHP, the skill of a web developer, then the presence in the portfolio of an open source engine for a store (or anything, in general), the quality of the code and UX of which characterizes your skill in this business will definitely not hurt . At the same time, it is not necessary to use completely pure PHP: look at the current frameworks (Laravel, Symfony, Kohana, Yii, Zend, Nette, etc) and make a choice between one of them or naked PHP / bicycle according to the criterion "in which case the code that implements my idea will be the most readable, extensible, reliable and productive" (in especially simple cases, a framework is overkill, in most more or less complex cases it is better with a framework).
If the ability to create and maintain online stores, then the projects implemented on generally accepted e-commerce CMS (PrestaShop, OpenCart, Magento, osCommerce / ZenCart, etc.) I think will be more valuable in the portfolio.

Answer 2

Of course do. If you have time and you are 13-15 years old, then this is a great way to fill bumps and pump your skill. That's usually how you become a programmer. From the beginning you write shit, then you read about MVC, you rewrite it, it turns out MVC is shit, then you learn about frameworks and write shit on a framework. Then you go to a cool office and they beat the shit out of you for a year and after that you become a specialist.

Answer 3

From the point of view of freelancing, it is better to take a ready-made well-known product, such as opencart. Maybe write a couple of modules for it. In freelancing, most clients want "fast, cheap, and good support." Tomorrow you will leave for another project, and who will understand your code?
And when applying for a job - work is different. Most want you to know at least one major framework - like zend, symfony, yii, lavarel. If you know one, you will be able to deal with the other in a reasonable time. And a specific CMS is wanted mainly by those who already have a number of products on this CMS.

Answer 4

It always makes sense to do something for the portfolio.

Answer 5

If a beginner, it is better to study existing cms and their approaches. It’s better to write bicycles not when you don’t know other products, but when you know well and they don’t suit you.

Answer 6

the correct chain in your case is as follows: pure php -> framework -> tsms -> store, it is possible without the tsms link. pure php -> store - it will be such a store that at one not so distant moment it will become impossible to modify. writing a framework is a lifetime, until you write, forget about the store, and at the same time study popular fv, so writing a framework can be shortened. pure php -> tsms - the topic is even more pernicious than anything in pure php. tsms should be done on top of a layer in which lower-level tasks have already been solved, and the creation of tsms in itself can turn out to be more complicated and non-trivial than the creation of fv, a bunch of various aspects and subtleties will come out that you don’t suspect in advance. in general, writing tsms can also be shortened. it remains to sort out and study everything that is ready from the foreseeable and choose something.

Answer 7

For a portfolio - only on CMS, for yourself - as you like. It is the knowledge of the intricacies of working with a certain (popular) CMS that will make you very attractive in the eyes of a potential employer, who, as already mentioned here, is guided by the rules - cheap and fast.

Answer 8

If there is extra time then go ahead in pure php. The easiest way to put on VP or opencart

Answer 9

A whole Internet store is probably not why. Write a basket separately, make filters separately, in principle there is nothing more needed there. Shut up sorting.

Answer 10

I would first learn the framework. Then he wrote tsms, and then the store. I wrote tsms 6 months. For a year, he made a dozen websites and online stores. In general, deal with the framework, because you will write in pure php for a long time

Answer 11

from experience I can say - if it is with a normal design - then it's worth it, because they are being taken to the picture

Answer 12

Don't waste your time with pure PHP. Start with any common framework, make something simple on it that you can use. The main thing is to clearly set yourself a TK. Look at the architecture, the organization of the code, make a couple of modules. And get pleasure, and you will not fight about your own ignorance. The main thing is to take something normal - Laravel, Kohana, Yii, even opencart is possible to start with something simple.
You don't start planting a forest when you need to make a wooden fence, do you? It just seems that everything is simple. Not easy, seriously.