Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

eddieol's avatar

What conventions to use when developing with multiple remote teams

I'm trying to develop a 30 pack of Laravel websites, different designs and formats. For this to happen I need to work with a team of developers and I need to assure a minimal quality for each website. So far I worked alone.

After they are done, only one person will maintain and develop extra features for all websites.

What minimal conventions (technical/functionality/security/safety/extendable) should I give them in order to be sure that they are working on the same path and pattern?

I thought of a few:

  • Rules for documenting the code:

    1. Use method names that are easily understandable
    2. Use sections for HTML tags
    3. Use descriptive name for classes and models
    4. Extend classes
    5. If you do the same thing in 2 Methods, you should build Helper classes
  • use the latest stable version of programming language (Laravel x, PHP y, etc)

  • database with only one user that can write

  • access database only locally or by VPN

  • use Cron Jobs, rather than doing a lot of processing real-time

  • choose the right HTTP expiration time for headers

  • Use gzip or other compressing methods for the HTML

  • Use caching for:

    • HTML
    • queries
  • CSS:
    • external CSS Files
    • use sass/less that are compiled together with all the other CSS included files
    • minify imports
  • JS:
    • external JS Files
    • compile all the JS files into one
    • minify imports
  • Mobile friendly
    • set 4-5 intervals of resolutions
    • think and develop the HTML + CSS for each resolution
0 likes
1 reply

Please or to participate in this conversation.