Skip to content
This repository was archived by the owner on May 31, 2025. It is now read-only.

Add explanations #3

@imliam

Description

@imliam

This repository is a good reference to refer back to, but in the past when onboarding new team members who have maybe come from a different framework/ecosystem I've had to explain why some of these conventions are in place to help them understand the choices.

I feel like this would be a good place to explain why some of these conventions and guidelines are in place. Some I can think of off the top of my head:

  • Helper functions are named in snake_case because that's what vanilla PHP functions are named like
  • Tables are pluralised because they represent multiple instances of data - each instance being an individual row inside the table
  • Models are named singularly because they represent a single instance of something that, not a collection of them

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions