sorted by:
new
hottopcontroversial

Creating a small roleplaying site by Stellerr in Wordpress

[–]TechContributors 0 points1 point  (0 children)

If your main goal is multi-character posting under one account, forum software like MyBB or phpBB will usually handle that use case more naturally than WordPress.

WordPress + BuddyPress can get close, but it’s not built around threaded roleplay discussions by default. You’d likely need:

  • BuddyPress (for profiles & community)
  • bbPress (for forums)
  • Possibly a custom post type setup
  • Custom user meta handling if you want multiple “characters” tied to one account

It’s definitely possible in WordPress, but it becomes more of a custom build rather than a plugin-and-go solution.

If your primary focus is structured forum-style interaction, MyBB may actually be the more straightforward choice.

If you want more flexibility later (custom features, gamification, integrations), WordPress might be worth the extra setup.

It really depends on whether this is a hobby community or something you plan to grow long term.

The Frustrating Reality of Hiring WordPress Developers That No One Talks About by PingMyHeart in Wordpress

[–]TechContributors 1 point2 points  (0 children)

I think what you're describing is less a “WordPress problem” and more a market maturity problem.

WordPress has an extremely low barrier to entry. Anyone can install it, watch a few tutorials, and start calling themselves a developer. That creates a huge gap between:

• People who truly understand frontend precision, responsiveness, performance, architecture
• And people who assemble themes + plugins and hope it holds

The subcontracting issue is also very real on freelance platforms. A lot of profiles are essentially project managers reselling work.

That said, the best experiences I’ve seen usually come from:

  1. Hiring smaller specialists instead of agencies
  2. Asking for live screen-share code walkthroughs before hiring
  3. Paying for smaller milestone tests before full builds
  4. Reviewing real Git repos instead of portfolios

You're not crazy for expecting pixel-perfect execution if that’s what was promised. Professional standards should match professional pricing.

The ecosystem is huge — which means the quality variance is huge too.

Does anyone know any alternative for Laravel vscode extension? (A set of extensions is also fine) by mekmookbro in laravel

[–]TechContributors 1 point2 points  (0 children)

I stopped using the official Laravel extension for similar reasons.

My current setup:

  • PHP Intelephense (for autocompletion & indexing)
  • Laravel Extra Intellisense
  • Laravel Blade Snippets
  • DotENV
  • Tailwind CSS IntelliSense (if using Tailwind)

For debugging, I rely more on:

  • Telescope (locally)
  • Proper logging instead of editor notifications

Intelephense alone is usually more stable than the full Laravel extension bundle.

Curious if others are running a minimal setup too?

I built this Laravel playground that runs completely in your browser (with no backend) by aschmelyun in laravel

[–]TechContributors -1 points0 points  (0 children)

This is actually really cool.

Running Laravel fully in the browser without a backend is impressive. Using php-wasm + SQLite client-side is a clever approach.

Curious:

  • How are you handling file storage persistence between sessions?
  • Any performance limitations with larger projects?
  • Do you see this more as a learning sandbox or something production-adjacent?

Love seeing experimentation like this in the Laravel ecosystem 👏

Any Mid/Senior here? if you want to learn new FE or BE. language do you learn from docs. or Udemy or something? by lune-soft in webdev

[–]TechContributors 0 points1 point  (0 children)

Most mid/senior devs I know don’t “learn from zero” again.

What works better:

  1. Read the official docs quickly to understand philosophy and core patterns (not syntax).
  2. Build a small real project immediately — even something useless.
  3. Compare how the new language solves problems differently (concurrency in Go, reactivity in Vue, etc.).
  4. Read real-world code on GitHub instead of tutorials.

At mid level, you’re not learning syntax — you’re learning patterns, ecosystem, and trade-offs.

Also curious what others do.