Level 75
In this episode Jeffrey said that will be a whole series about Jetstream. So you have to just wait.
Nov 22, 2020
12
Level 7
Jetstream
Hey folks,
Just wondering if there's any info on when Laracasts will feature a comprehensive series on Jetstream?
With Laravel 8 having been out for a few months now, it seems as if this probably should have been available by now.
Level 7
Thanks for your reply.
I did spot that episode although it was published some time ago in terms of the speed web development moves.
Unfortunately a lot of us don't have the luxury to wait around and will have to lean on other inferior resources to be able to continue with new projects, since it seems Jetstream is unavoidable. Please note that this is intended to be feedback rather than a complaint. I think Jeffrey and the team have done a great job so far and guiding us through numerous technologies in a concise and easy to digest way.
Level 75
You can still use Laravel/UI if you want.
Level 122
since it seems Jetstream is unavoidable
No, you can also use Laravel/breeze
Level 59
We will cover Jetstream... but it is 100% avoidable. Not sure where you got the impression that it’s a required package.
Level 7
Thanks for your replies.
So my understanding is that Laravel 8 provides basic authentication "out of the box" however this does not include any views or controllers to register or login to user accounts. The Official Documentation no longer mentions Laravel/UI as far as I can see but instead suggests users install Jetstream to get something up and running quickly.
Most websites/webapps require user login and profile capabilities and of course being an open framework anything is technically avoidable as a developer is free to add and modify the code as they wish. Perhaps a more accurate word might have been convenient.
I can see the documentation provides information on Manually Authenticating Users so maybe this is the way to implement my own login system without deviating from the documentation (i.e by installing packages that are not referenced).
Am I missing something and way off here?
Level 52
There are three approaches:
- use Jetstream (if you like Tailwind and Livewire)
- use laravel / ui (if you want something simple)
- use Fortify and create your views (but you can also get those from laravel / ui to start)
Level 75
And besides that really what jetstream scaffolds, those technologies have learning videos anyway and documentation. They are basically just Stacks you choose to use.
For example my chosen stack is fetch Js with mostly regular CSS, yet there's no videos covering just that. To me a stack is something the developer should learn on their own, but just my opinion.
To add to @bestmomo answer, a 4th option, manually creating everything, which is well covered in the authentication chapter in the documentation.
The only thing I cannot understand is why Tailwind is being used in a simple starter application. Seems that laravel UI is the same as Breeze except for tailwind. Seriously what in the World is wrong with regular plain CSS for a starting point.
1 like
Level 52
Seriously what in the World is wrong with regular plain CSS for a starting point.
What is wrong is only the fact that CSS is not that easy to master and it is much easier and faster to use a framework.
We could have the same reasoning with Javascript or PHP framework. Twenty years ago I was coding with simple PHP, vanilla Javascript, and CSS was still pretty mysterious.
Now things have changed a lot and technology is evolving at high speed and it seems that we often have to run to catch up with it.
Personally, I abandoned all JavaScript frameworks because browser APIs are quite sufficient.
I find it more difficult to do without a CSS framework but I have difficulty choosing and I never use the same one. On the other hand I often have a lot of CSS added to enhance the visual. I think in a year I will also give up CSS frameworks.
On the other hand I will keep Laravel for a long time!
1 like
Level 14
After Jetstream release:
Dammit, they are still using Laravel UI.
...
Let's make Laravel Breeze.
...
Dammit, they are still using Laravel UI.
...
Just joking here ;)
But I could not disagree with jlrdw, Laravel Breeze seem just another try to push tailwind.
I still prefer Laravel UI, I like the usage of Traits, where you override only what you need. Also it has already several presets, even for tailwind, so not sure why get yet another auth package.
About OP questions, don't worry if Laravel UI is not in docs, because Taylor said that will be mainteined in future, we all hope. Also it doesn't need too much docs to get started, just installation, but that it's easy.
2 likes
Level 7
Tailwind seems to be very much liked within the Laravel community from what I've seen. I noticed an interesting thread over on Hacker News a few days ago, it's obvious that there's mixed opinion on the necessity for CSS frameworks.
I've been around a while and so far found regular plain css to work fine, with it being quick and simple to work with and not change often enough to need to learn a new CSS framework every 12-18 months. I'm sure Laravel has featured Bootstrap, Bulma and Tailwind over the last few years.
Is regular CSS that bad? I'll have to take some time to explore Tailwind and find out for myself when I get time.
One consideration for me is having a project that's both compliant and accessible; accessible includes making your site available without compromise for those with limited bandwidth. I believe Laravel.com uses Tailwind as I'm sure many large projects do.
Is it standards-compliant and performant?
Of course I'm absolutely not trying to point the figure at Laravel.com here or show any disrespect to the project, that's not my intention, I just thought it was an interesting topic to explore.
Level 75
@thewebartisan7 see my post here: https://laracasts.com/discuss/channels/general-discussion/taylor-discusses-jetstream-and-laravel-ui
According to Taylor in that video, UI will be maintained.
@zoidq you have to consider, those css frameworks (libraries) use normal css in the background.
So tailwind is doing nothing that normal css with media queries for mobile isn't doing.
Edit: I am missing something, I looked over Breeze, no trait like the UI has.
Will someone explain to me what is / was wrong with the UI for scaffolding Auth. I thought it was great.
1 like
Please or to participate in this conversation.