https://brand.bhdicaire.com/en/Brand standards and implementation notes for BHDicaire.com.Hugo -- gohugo.ioen-cahttps://brand.bhdicaire.com/en/sitemap/Mon, 10 Aug 2026 00:00:00 +0000https://brand.bhdicaire.com/en/sitemap/<p>This page lists the main public pages on the brand site.</p>https://brand.bhdicaire.com/en/legal/terms/Sat, 11 Jul 2026 00:00:00 +0000https://brand.bhdicaire.com/en/legal/terms/<p>This is a personal digital sandbox website operated by Benoît H. Dicaire out of Montreal, Canada. It serves as a living archive of thoughts, technical experiments, and deep dives into security, privacy, and technology.</p>https://brand.bhdicaire.com/en/legal/responsible-disclosure/Sat, 11 Jul 2026 00:00:00 +0000https://brand.bhdicaire.com/en/legal/responsible-disclosure/<p>If you believe you found a vulnerability affecting this website or its public infrastructure, thank you for taking the time to report it responsibly.</p>https://brand.bhdicaire.com/en/legal/public-machine-readable-files/Sat, 11 Jul 2026 00:00:00 +0000https://brand.bhdicaire.com/en/legal/public-machine-readable-files/<p>This page gathers the public machine-readable files and operational endpoints for this website.</p> <h2 id="security-and-contact-discovery">Security and contact discovery<a class="heading-anchor" href="#security-and-contact-discovery" aria-label="Link to Security and contact discovery">#</a></h2> <ul> <li><a href="https://brand.bhdicaire.com/.well-known/security.txt"><code>/.well-known/security.txt</code></a> : vulnerability disclosure and security contact metadata.</li> <li><a href="https://brand.bhdicaire.com/security.txt"><code>/security.txt</code></a> : root-level copy of the security contact metadata.</li> <li><a href="https://brand.bhdicaire.com/humans.txt"><code>/humans.txt</code></a> : people, tools, and site credits.</li> <li><a href="https://brand.bhdicaire.com/human.txt"><code>/human.txt</code></a> : compatibility copy of <code>humans.txt</code>.</li> </ul> <h2 id="crawlers-and-indexing">Crawlers and indexing<a class="heading-anchor" href="#crawlers-and-indexing" aria-label="Link to Crawlers and indexing">#</a></h2> <ul> <li><a href="https://brand.bhdicaire.com/robots.txt"><code>/robots.txt</code></a> : crawler access preferences and specific user-agent constraints.</li> <li><a href="https://brand.bhdicaire.com/sitemap.xml"><code>/sitemap.xml</code></a> : XML sitemap for search engines and crawlers.</li> <li><a href="https://brand.bhdicaire.com/en/sitemap/"><code>/en/sitemap/</code></a> : human-readable sitemap.</li> </ul> <h2 id="language-model-context">Language model context<a class="heading-anchor" href="#language-model-context" aria-label="Link to Language model context">#</a></h2> <ul> <li><a href="https://brand.bhdicaire.com/llms.txt"><code>/llms.txt</code></a> : concise LLM-oriented site context.</li> <li><a href="https://brand.bhdicaire.com/llms-full.txt"><code>/llms-full.txt</code></a> : expanded LLM-oriented site context.</li> </ul> <p><strong>AI Scraping &amp; Data Mining Policy:</strong> The machine-readable files indexed under this section outline the explicit scraping permissions for this domain. Automated collection, data mining, or training of LLMs outside of the rules specified in our <code>/robots.txt</code> or via standard <code>X-Robots-Tag</code> HTTP headers is strictly prohibited.</p>https://brand.bhdicaire.com/en/legal/privacy/Sat, 11 Jul 2026 00:00:00 +0000https://brand.bhdicaire.com/en/legal/privacy/<p>This brand site is operated by Benoît H. Dicaire from Canada. I try to keep the site privacy-respecting by default and to collect as little personal information as practical.</p>https://brand.bhdicaire.com/en/legal/accessibility/Sat, 11 Jul 2026 00:00:00 +0000https://brand.bhdicaire.com/en/legal/accessibility/<p>I want this website to be usable by as many people as practical, including people using keyboards, screen readers, zoom, high-contrast settings, and assistive technologies.</p>https://brand.bhdicaire.com/en/legal/license/Sat, 28 Feb 2026 00:00:00 +0000https://brand.bhdicaire.com/en/legal/license/<p>A page which clarifies how the content on this site is licenced</p>https://brand.bhdicaire.com/en/docs/user-interface/components/pageheader/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/components/pageheader/<p>PageHeader patterns should establish section, title, metadata, and primary context without custom exceptions. Keep alignment, width, and optional elements consistent across page types.</p>https://brand.bhdicaire.com/en/docs/user-interface/patterns/accessibility/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/patterns/accessibility/<p>Accessibility is part of the component contract. Preserve keyboard access, visible focus, sufficient contrast, semantic headings, useful labels, and predictable reading order.</p>https://brand.bhdicaire.com/en/docs/user-interface/patterns/responsive/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/patterns/responsive/<p>Responsive behavior should preserve purpose, not merely shrink the desktop page. Keep navigation reachable, avoid overlapping text, and use constraints that make the same content work at small and wide sizes.</p>https://brand.bhdicaire.com/en/docs/user-interface/components/datatable/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/components/datatable/<p>DataTables should support scanning, sorting, filtering, and repeated comparison. Keep column labels stable, expose sort direction, and avoid hiding essential data behind decorative layouts.</p>https://brand.bhdicaire.com/en/docs/user-interface/primitives/token-names/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/primitives/token-names/<p>Token names should describe purpose, not decoration. Prefer names that survive a visual redesign, and avoid one-off tokens unless they represent a reusable decision.</p>https://brand.bhdicaire.com/en/docs/user-interface/patterns/padding/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/patterns/padding/<p>Padding protects content inside a component. Keep it stable across states so hover, focus, badges, and longer labels do not resize the layout.</p>https://brand.bhdicaire.com/en/docs/user-interface/components/cards/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/components/cards/<p>Cards are for repeated items or framed tools. Avoid nesting cards inside cards, and keep radius, padding, and hierarchy consistent across a set.</p>https://brand.bhdicaire.com/en/docs/foundations/brand-voice/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/brand-voice/<p>Write plainly, with enough context to make decisions easy. Prefer concrete nouns, short explanations, and direct verbs. Avoid hype, ornamental phrasing, and text that describes the interface instead of helping the reader act.</p>https://brand.bhdicaire.com/en/docs/user-interface/primitives/typography/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/primitives/typography/<p>Interface typography should stay compact, readable, and consistent. Reserve large display sizes for page-level hierarchy and keep controls, tables, and sidebars tighter.</p>https://brand.bhdicaire.com/en/docs/foundations/typography/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/typography/<p>Typography carries most of the brand expression. Display type is for names and strong hierarchy, sans text is for interface clarity, serif text is for readable prose, and mono text is for code, keys, and exact values.</p>https://brand.bhdicaire.com/en/docs/user-interface/patterns/margin/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/patterns/margin/<p>Margins separate regions. Use them to create rhythm between sections, not to repair component internals or compensate for unstable content size.</p>https://brand.bhdicaire.com/en/docs/foundations/illustrations/diagrams/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/illustrations/diagrams/<p>Diagrams should answer a specific question. Use consistent labels, visible direction, and only the detail required to explain the relationship, flow, or boundary being documented.</p>https://brand.bhdicaire.com/en/docs/user-interface/components/button-groups/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/components/button-groups/<p>Button groups should make related actions feel connected. Use them for compact command sets or mutually related choices, not as decoration around unrelated links.</p>https://brand.bhdicaire.com/en/docs/user-interface/primitives/size/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/primitives/size/<p>Size primitives should reduce judgment calls. Use named steps for fixed-format controls, predictable spacing for dense tools, and responsive constraints where content length can vary.</p>https://brand.bhdicaire.com/en/docs/foundations/illustrations/mindmaps/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/illustrations/mindmaps/<p>Mindmaps are useful when a topic has many related parts but no strict sequence. Keep labels short, avoid crossing lines when possible, and make the central concept obvious at a glance.</p>https://brand.bhdicaire.com/en/docs/brand-assets/media-kit/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/brand-assets/media-kit/<p>The media kit should help someone reference BHDicaire.com accurately. Keep it concise: approved names, short descriptions, contact context, and links to current logo material.</p>https://brand.bhdicaire.com/en/docs/user-interface/patterns/layout/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/patterns/layout/<p>Layouts should match the job of the page. Documentation needs room for reading and navigation, dashboards need dense comparison, and landing surfaces need strong first-viewport signals.</p>https://brand.bhdicaire.com/en/docs/foundations/colours/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/colours/<p>Colours should clarify hierarchy before they decorate. Use the site tokens first, reserve the accent for identity and action, and keep neutral surfaces quiet enough for long reading and repeated operational use.</p>https://brand.bhdicaire.com/en/docs/user-interface/components/button/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/components/button/<p>Buttons are for explicit commands. Use clear labels or familiar icons, keep hit areas stable, and reserve stronger styles for actions that need priority.</p>https://brand.bhdicaire.com/en/docs/foundations/logo/usage/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/logo/usage/<p>Use the logo where ownership must be clear: headers, downloadable assets, and official brand surfaces. Preserve clear space, keep contrast high, and do not stretch, recolour, rotate, or combine it with unapproved marks.</p>https://brand.bhdicaire.com/en/docs/brand-assets/logo/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/brand-assets/logo/<p>Logo assets should be distributed from the canonical brand site. Include enough variants for normal use, but avoid carrying old experiments or page-specific exports.</p>https://brand.bhdicaire.com/en/docs/foundations/illustrations/icons/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/foundations/illustrations/icons/<p>Icons should make controls easier to scan. Use an established icon before drawing a custom mark, pair unfamiliar icons with accessible labels, and keep stroke, size, and alignment consistent.</p>https://brand.bhdicaire.com/en/docs/user-interface/patterns/grid/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/patterns/grid/<p>Use grids to align related content and make scanning predictable. Define column behavior explicitly so cards, tables, and navigation do not shift unexpectedly between viewports.</p>https://brand.bhdicaire.com/en/docs/user-interface/primitives/color/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/primitives/color/<p>Interface colour primitives should express hierarchy, state, and action. Keep semantic use stable so a colour means the same thing across documentation, tables, and tools.</p>https://brand.bhdicaire.com/en/docs/user-interface/components/breadcrumbs/Mon, 01 Jan 0001 00:00:00 +0000https://brand.bhdicaire.com/en/docs/user-interface/components/breadcrumbs/<p>Breadcrumbs should show location without becoming a second table of contents. Keep them short, ordered from broad to specific, and useful on deep pages.</p>