CMS, framework or pure PHP?

Question

Yii

Hello, for starters: I am a beginner PHP programmer who already knows html / css at a more or less sufficient level, javascript at the level of understanding syntax, well, I can write something very simple with a database in PHP. At one fine moment, I realized that it was time to use all this in practice, and then I was once offered to write an updated website for the department of my university. It is already almost made up, and the question has come, which concerns the server part. But since I'm still a very, very newbie, I can't decide how exactly I should start developing this back-end, since I don't want to write another site with redneck PHP and HTML code in one file. The functionality of the site will be as follows:

1. 1) Ability to add, delete, update information (news, for example, photos)
   
2. 2) Ability to add new files
   
3. 3) In the future, the possibility of registration
   

As a matter of fact, the questions are:
1) What is better to choose: CMS, some kind of framework or write in pure PHP with MVC architecture? I would like to stop at writing a site on some framework or on a clean one, but maybe it’s worth using an already made CMS and not inventing bicycles?
2) If you choose not a CMS, then is it worth writing in pure PHP without frameworks? Maybe it's too early to start writing a project on a framework?

Answer 1

From the point of view of reducing labor costs - take a CMS like Wordpress with the Custom Pages plugin and wrap the whole site around it. It will be faster, probably more reliable (because you still have little experience, and there is a more or less debugged solution), but with practically no benefit to you.
From the point of view of usefulness, it is worth taking some serious framework (Symfony2, Yii2, Laravel) and making it on it. There will be a lot of useful experience - in fact, almost all development, if frameworks have not been used before. It will be hard, longer, but much more useful. Moreover, it is more useful only for you, because due to inexperience you will make a lot of small mistakes and the department will receive a site with some problems.
I don’t suggest choosing pure PHP - you won’t do anything good without experience, it will be a waste of time and with zero benefit for everyone.
Therefore, it is up to you to decide in whose favor you will work on the project: for your own or for the departments. At uni, I would work for myself.

Answer 2

For the department, do it on CMS. Writing from scratch, even on a framework, is half the battle. You finish your studies, leave, and then people have to live with it. Wordpress (or even Drupal) is fine.
For learning, I recommend doing something separate for yourself on some kind of framework. Otherwise, enthusiasm may simply not be enough to bring to mind such a simple task, I'm not saying that it will still need to be supported.
In the case of CMS, any student will be able to modify (as a rule, it is enough to install plugins). And in the case of "from scratch" the next person who will deal with it will strive to make a new site.

Answer 3

I advise you to use the Framework - and you will spend a little time and get experience. A CMS is to make a site in haste, with minimal experience. Pure php generally disappears immediately, as there are too many unnecessary gestures.
I advise you to write your projects in pure php, using design patterns. Write your cms/framework. A very useful thing in terms of experience. But it will take a lot of time.
Therefore:
- you need to create a site quickly - cms. This is how web studios work. Fast and cheap.
- you need to create a site and engage in its further support and development for more than one year - Framework definitely.
- you create a website for yourself and for learning purposes - pure PHP.
And at the end I will give you a link very useful. There you will learn about everything that a good developer needs.
getjump.me/en-php-the-right-way

Answer 4

At one fine moment, I realized that it was time to put it all into practice ...

Needed from the start!
One way or another, you write redneck code. They learn from practice and mistakes, improving each time.
Nothing can be said about the questions without knowing the timing.

Answer 5

I am a beginner PHP programmer

From here the conclusion is immediately - if you want to code, then a framework, if you want money and fame - CMS. On pure php, you will not take either one, but you will earn a headache.
Let me explain. The framework will save (as far as possible) from any security errors and, on occasion, from wasting time. The CMS will give you what you want, minus the coding.

Answer 6

You can choose the middle option, take the same OctoberCMS, get CMS and the laravel framework in one bottle.

Answer 7

I would recommend framework. It is safer, many things are implemented for you, you can get acquainted with interesting approaches and architectures. Look towards Symphony 3.

Answer 8

Pure php of course.

Answer 9

Use drupal without hesitation. Correctly written above - people then work with these sites, you won’t be able to write anything sane from the first time on the framework, it makes no sense to even consider pure puff.
Take Drupal and with the help of the views module you do everything perfectly.

Answer 10

With photos and other "not easy" it is better to use the possibilities of deferred processing. You need a front on angular, and on the ratchet and beanstalk server, drive messages via wamp over websocket and manage the entire zoo of services through the supervisor :) In short, the ws server should be a dumb bus, just like the bininstall itself. Difficult to pass around. Then the site would finally be cool, realtime and all that :))

Answer 11

I wrote an article on this topic:
cms vs framework
In short:
pure php - only if the php skill goes off scale and you know exactly why not cms and not framework
csm - if there is cms covering 95% of the project's needs + the load is planned not sky -high
framework - all other cases