Back
Maymo

Discovering Laravel

@Maymo

Laravel the API Backend

Laravel may also serve as an API backend to a JavaScript single-page application or mobile application. For example, you might use Laravel as an API backend for your Next.js application. In this context, you may use Laravel to provide authentication and data storage / retrieval for your application, while also taking advantage of Laravel's powerful services such as queues, emails, notifications, and more.

If this is how you plan to use Laravel, you may want to check out our documentation on routing, Laravel Sanctum, and the Eloquent ORM.

1 • •

94

•
  • No matching results...
  • Searching...

/ 1000

moe_mizrak

Moe Mizrak

@moe_mizrak

@nunomaduro can you please do something about this madness - spam?

1 • •

36

•
moe_mizrak

Moe Mizrak

@moe_mizrak

you are literally spamming, and you have been warned before about that by @rtrudel kindly

• •

45

•
ilyosjon

Ilyosjon 🇺🇿

@ilyosjon

@Maymo It is great that you are trying to help community but just copy-pasting a paragraph from official docs is not good.

You better do a research and then write a tip or article with your own words and tone IMHO

• •

18

•
rtrudel

Richard Trudel

@rtrudel

Great to see you've changed your username! While your enthusiasm for sharing knowledge is fantastic, let me suggest some thoughts.

Multiple posts can flood the feed, limiting others' visibility. Instead of reposting documentation, try sharing your personal discoveries:

- Document interesting problems you've solved
- Highlight useful features you've found
- Share packages that improved your workflow
- Ask questions or answer others'

If you're passionate about documentation, start a blog - it's perfect for in-depth content like tip categories or step-by-step app building tutorials. You can share these articles here at a steady rhythm that gives the community time to engage, rather than posting everything at once.

Remember: valuable contributions come from personal experience and genuine interaction. Keep that enthusiasm, just channel it to enrich our collective knowledge!

I hope this helps you better understand the concerns raised and turn them into something constructive!

1 • •

17

•
Maymo

Discovering Laravel

@Maymo

The name king of Laravel triggered some people, i don't know why, but i changed it.

The username was my role, i chose it, it could have caused misunderstanding, i changed it.

But you are not seriouse by asking me what type of content i should post on social media. There are different types of content creator and consumer. I consume and create different content than you, and you must respect my choice.

If you don't like what I post, simply scroll away, if scrolling away is too much asked, create a simple adblocker filter. All the time you wasted in pointing random people on internet what they should and should not post, could be used to create tens of such extensions. That way you could have saved your self all the sleepless nights, you wasted with the fear of someone posting something you do not like on internet.

I do not like that you post personal stories, from which i learn nothing. Have i ever asked you to stop posting personal stories which are not interesting for me?

1 • •

10

•
KrishanK

Krishan König

@KrishanK

@Maymo what you are doing is just copying the docs. We can go to Laravel.com and read them there by ourselves. What value are you adding by just copy pasting docs of a framework many of us are familiar with?

1 • •

5

•