As you now can check Yii 3.0 application template preview via How to get started with Yii 3.0 application please voice your opinion on it.
Which one you like best?
0 voters
Please explain your choice. Thanks!
More Clean Architecture, KISS Principle.
As long as the template keep MVC separation strongly, I think it’s Ok.
yii3 basic app structure is confusing lot of people using yii are not composer experts or php experts, my only concern is it will make it difficult for beginners to get stared.
We need to attract more people to yii not push them away by introducing abstractions which are hard to grasp.
I agree with @alirz23.
The new yii-project-template looks too sophisticated to me. Isn’t it an overly designed layer that serves only to the formal beauty of the structure? yii-base-web, yii-base-cli and yii-base-api would be enough.
I understand that it might be solved by a good documentation, though.
I believe that once you’ve install the new template, you’ll get a standard directory structure with standard functionalities that we used to get from app-basic template.
As others have said, It is a complicated structure. The major problem being, the sources folders are not clear as in Yii2. I would like to install template and start coding outright. Until that’s solved and made obvious, my vote goes to Yii2 template.
Another thing that need to be clear is how the REST API fits in that specific template. In Yii2 I would just install "yiisoft/yii2-rest": "~1.0.0" and delete Views folder. But dunno how to deal with Yii3 template
I missed the composer require yiisoft/yii-base-api which does nicely what I wanted for rest API
what is funny in the poll is most of people voted for yii3 don’t even know about the actual problem
So we have to emphasize that the new yii 3 template “yii-project-template” is a kind of place holder for the actual templates: “yii-base-web”, “yii-base-cli” and “yii-base-api”. Ideally we should easily be able to select only the required functionalities through those 3 templates and other libraries.
I would like to keep 2.0 approach and only let composer be used for additional code not main app. Also index.php should be simpler.
My proposal basically would be to have a template, which would allow you to install as in Yii2 in a practical and simple way, usually the majority seeks to install the Application Web Template, which for me, the best proposal is @hiqsol with the base web skeleton and skeleton master, since it allows updating the base web skeleton without reinstalling it simply by updating and its installation was simple and intuitive with the basic configurations of any web application.
Hopefully we will have the DB layer working, since this will allow more people to relate and we can make corrections of other important packages, and so we can move faster.
On the other hand you can create another template, which of a clear example of how to use yii-base-api, yii-base-cli, so that we can all clearly understand what is the best way to work.
Sorry my bad english.
I think the purpose of a template should be to bootstrap a new app with minimal effort.
This is what I got after running the command
composer create-project --prefer-dist --stability=dev yiisoft/yii-project-template myapp
With this, I’ve to create everything from scratch. For that we have Laravel.
We need a basic template same as like yii2.
I really like the idea of a “yii-base” template with “yii-base-web”, “yii-base-cli”, “yii-base-api” templates for each purpose. We currently tend to always use the yii2-advanced template because we usually need cli, a frontend and backend webapp - or even more than 2 web parts. So the ability to only add api/cli/web as needed for a product, but as many of each as you need within the product, seems powerful. It’s also very much in line with current application design views and will make Yii 3 future-proof for the next decade!
However I also wholeheartedly agree with everyone concerned about accessibility for new and novice users and the learning curve required. It was quite a struggle for us to get started with yii2 about 3 years ago and it was not for the faint-hearted. It’s also Yii’s greatest disadvantage to Laravel and others. So overcoming this should be part of the Yii 3 agenda, but not at the expense design quality based architecturally sound decisions when we have other ways of lowering the barrier to entry and making Yii3 easy to get started with.
So why not do something like this?
composer require foxy/foxy:^1.0.0 to get yii-base-web to work, just make foxy a dependency of yii-base-webThe product I’ll be building:
- Will have a website (= adds
composer require yiisoft/yii-base-web)- Will have an API (= adds
composer require yiisoft/yii-base-api)- Will have batch jobs (= adds
composer require yiisoft/yii-base-cli)- Will be used from a command line interface (= adds
composer require yiisoft/yii-base-cli)- Will have users that register and/or login (= adds a user module)
- Will need role-based access control (= adds
composer require yiisoft/yii-rbac)etc.
[Start button]
Good ideas. Thanks!
It would be cool, if new Yii3 web template will have some basic CMS features to start, like Admin panel, menu editor, RBAC manager, logging module, modular structure etc, like Yii2 Starter Kit, which is really popular (but too complicated for beginners). Such “yii-base-cms” will gain new developers to use Yii for common tasks, like website rapid development.
I don’t think it’s a good idea: