# Usage Examples > [!summary] > Use these patterns when creating new Eval Labs Canon notes, homepage sections, screenshots, and brand references. --- ## Standard page opening ```md --- cssclasses: - eval-labs-note --- # Page Title > [!summary] > One clear sentence explaining what this note is for. --- ## First Section Plain explanation. ``` --- ## Homepage Logo/Text Table Use this for the homepage identity unit: ```md | | | |---|---| | ![[assets/binary-eval-logo.png]]<br><em>Eval Labs Logo.</em> | Eval Labs serves as the definitive proprietary AI audit-layer, engineered to govern and validate the hyper-complex outputs of Lucia’s cognitive core. | ``` CSS owns the sizing, spacing, purple rail, mobile stacking, and invisible table treatment. Do not size the image in the Markdown embed. --- ## Screenshot block ```md >![[assets/ui-review-queue.png]] _Review Queue. Human evaluators score Lucia’s responses and save notes._ ``` Keep captions short. --- ## Summary callout ```md > [!summary] > Eval Labs exists to make Lucia’s behavior reviewable, repeatable, and safer to improve. ``` --- ## Risk callout ```md > [!risk] > Do not treat one good response as proof of stable behavior. Use a saved suite and rerun it after changes. ``` --- ## Verified callout ```md > [!verified] > Saved custom suites are live and can be reused for regression checks. ``` --- ## Eval-specific wording Good: ```text This run shows a repeated tone regression in overwhelmed-owner prompts. ``` Better: ```text This run shows Lucia becoming more verbose under operator stress, which increases scanning burden and should fail the calm/usefulness bar. ``` --- ## Template for new brand notes ```md --- cssclasses: - eval-labs-note --- # Note Title > [!summary] > What this note governs. --- ## Rule The operating rule goes here. --- ## Use when - case one - case two - case three --- ## Avoid - failure mode one - failure mode two - failure mode three --- ## Example ```text Concrete example here. ``` ```