From 092f1e44a231d26ef2841cd076486287da430566 Mon Sep 17 00:00:00 2001 From: webmaster Date: Tue, 3 Nov 2026 15:51:18 +0000 Subject: [PATCH] =?UTF-8?q?feat(freelancer-directory):=20Best=20Practices?= =?UTF-8?q?=20=E2=80=94=2012=20items=20in=20two=20independent=20columns?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds the twelfth item ("Look at a similar job they have already done") and splits the accordion into two independent columns of six. - Two independent columns (.bp-list > .bp-col, each its own grid, parent align-items:start) so opening an item grows only its own column and cannot shove the other. A single grid would re-size rows and make both columns jump on every click. - DOM / reading order is 1–6 (left column) then 7–12 (right column) — a decision, not an accident. - Exclusivity still one-open-at-a-time via the shared
plus the inline JS fallback; re-proved, including the strip-the-name test. - <=720 px collapses to a single column, no horizontal overflow. --- odoo-community-developers/index.html | 38 +++++++++++++++++++++++++--- 1 file changed, 34 insertions(+), 4 deletions(-) diff --git a/odoo-community-developers/index.html b/odoo-community-developers/index.html index 8e8b7dc..5a6f3fd 100644 --- a/odoo-community-developers/index.html +++ b/odoo-community-developers/index.html @@ -960,9 +960,11 @@ } /* ---- Best Practices accordion (page-scoped, additive). Reuses the house FAQ card - and "+/-" marker; items are full-width, single column. Exclusivity comes from the - native
attribute, with a small JS fallback in the page script. All - items are CLOSED on load — nothing carries `open`. ---- */ + and "+/-" marker. TWO INDEPENDENT COLUMNS of six (see .bp-list/.bp-col): each + column is its own grid, so opening an item grows only its own column and the + other column does not move. Exclusivity comes from the native
+ attribute, with a small JS fallback in the page script. All items are CLOSED on + load — nothing carries `open`. ---- */ .bp-lede { max-width: 760px; margin: 0 0 1.5rem; @@ -970,10 +972,26 @@ line-height: 1.7; color: var(--ink-soft); } + /* Parent grid: two columns pinned to the top (align-items:start), so an open item + in one column cannot push the other column down. DOM order is 1–6 then 7–12. */ .bp-list { + display: grid; + grid-template-columns: 1fr 1fr; + align-items: start; + column-gap: 2rem; + row-gap: 0.75rem; + max-width: 1100px; + } + .bp-col { display: grid; gap: 0.75rem; - max-width: 900px; + align-content: start; + } + /* 375 px and everything narrow: one column, no horizontal overflow. */ + @media (max-width: 720px) { + .bp-list { + grid-template-columns: 1fr; + } } .bp-item { background: var(--ivory); @@ -1217,6 +1235,7 @@

Best Practices

Hiring a freelancer goes better when a handful of things are settled before the work starts. These are not rules we impose, and they are not a verdict on anyone listed here — they are simply the points where this kind of work most often goes wrong.

+
Agree the shape of the work first — workpackage or hours @@ -1260,6 +1279,9 @@
+ +
+
Prefer a proven third-party module — check the OCA first
@@ -1295,6 +1317,14 @@
+
+ Look at a similar job they have already done +
+

Ask for one piece of work close to yours and look at it before you commit — a module, a migration, a report. Someone who can show you something near your problem is easier to trust than someone who can only describe it. If they cannot share a client's work, ask them to talk you through a job like yours instead.

+
+
+ +