Define the reusable signature appearance contract
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- ドキュメント
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- php
- 領域
- backend, documentation
調査の方向性
Start by reviewing code and tests for signature-template editing, Policy Workbench configuration, previews, stamp rendering, PhpNative XObject generation, placeholders, and Unicode issue #8155; complete and review LibreSign/documentation#113 as factual input. Produce durable project documentation defining the representation, validation, variables, rendering and migration boundaries, then review #9048 and #9049 against it and update their assumptions. Done means every checklist item in this issue is documented and both downstream epics have been reviewed.
索引モデルが issue の本文から書いたものです。
説明
Goal
Document and define the reusable signature-appearance contract that future editor, preview, PDF rendering and AI-assisted authoring work must follow.
This is an architecture and planning task. It does not implement a new template engine, editor, renderer or AI feature.
The contract must first serve normal LibreSign functionality. AI is only a future consumer of that contract.
Current-state inputs
Before deciding the future contract, document and review the current behavior of:
- signature footer/template editing;
- Policy Workbench signature-footer configuration;
- preview generation;
- signature stamp rendering;
- PhpNative appearance/XObject generation;
- other renderer-specific differences;
- current template variables/placeholders;
- Unicode behavior and #8155.
Use code and tests as the source of truth.
LibreSign/documentation#113 documents the current signature appearance and preview pipeline and must be completed/reviewed as factual input before this synthesis is finalized. That documentation task must not decide the future appearance contract.
Contract to define
Document the minimum stable representation and rules for:
- appearance/template content;
- supported layout/formatting;
- variable/placeholders and their types;
- default/fallback behavior;
- validation errors;
- safe style/markup subset if markup is used;
- preview input/output;
- final PDF/XObject rendering input;
- Unicode/font requirements;
- compatibility/migration for existing stored templates;
- renderer-specific capabilities/fallbacks.
Do not choose raw HTML, Twig, JSON/AST or another representation because it is convenient for AI. Select or document a representation only after current product/rendering requirements are understood.
Restricted execution
If a template engine is part of the future contract, define an intentionally restricted environment.
The contract must exclude:
- arbitrary functions or PHP execution;
- filesystem access;
- remote/network resources;
- unrestricted includes/imports;
- scripts/event handlers;
- unrestricted CSS or URL-bearing constructs;
- unknown placeholders that silently produce misleading signed output.
Invalid or unsupported input must fail predictably before signing.
Unicode and fonts
Use #8155 as concrete evidence that text encoding/font behavior must be part of the contract.
Document:
- which character ranges the future contract must support;
- how unsupported characters are handled;
- renderer/font requirements;
- how preview and final output remain consistent.
Do not implement the Unicode fix in this architecture task.
Preview and final rendering
The contract must make clear that preview and final PDF rendering consume the same validated semantic representation.
Document any renderer-specific differences that cannot currently be eliminated.
UX input
The contract must expose enough information for future editor UX to know:
- which formatting controls are meaningful;
- which variables can be inserted;
- which validation errors need to be shown;
- what preview can reproduce accurately;
- which advanced implementation concepts should remain hidden from normal users.
Do not implement the editor in this issue.
Required architecture artifact
Store the final contract in durable project-owned documentation.
It must include:
- current-state summary;
- chosen/future representation;
- allowed variables;
- validation/sanitization boundary;
- preview/rendering boundary;
- Unicode/font behavior;
- compatibility/migration rule;
- explicit non-goals and unsafe constructs.
Downstream handoff
Before this issue is complete:
- review #9048 against the documented contract;
- review #9049 against the documented representation, variable registry, validator/sanitizer, preview and rendering boundaries;
- update those epics where assumptions differ;
- do not create AI implementation issues based on an older assumed format.
Out of scope
Do not:
- implement a new template engine;
- modify the production editor;
- modify the renderer;
- fix #8155;
- add AI authoring;
- add new template variables.
Done when
- A single reusable signature appearance representation is documented.
- Validation/sanitization rules are explicit.
- Variable/placeholder behavior is explicit.
- Preview and final-render boundaries are explicit.
- Unicode/font behavior is explicit.
- Existing stored templates have a compatibility/migration rule.
- Unsafe execution/resource access is excluded by contract.
- The contract is stored in durable project-owned documentation.
- #9048 and #9049 have been reviewed against the final contract.
- 主要言語
- PHP
- スター
- 844
- フォーク
- 176
- 平均マージ
- 14時間 3分
- マージ済み PR(30日)
- 344
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
LibreSign/libresign のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnf対応中かも @vitormattos が 5 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
LibreSign/libresign#9366 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 83/100
LibreSign/libresign#9007 · コメント 2 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
LibreSign/libresign#8284 · コメント 5 件 ·
メンテナーはふだん 1 日以内に返信
-
frontend javascript technical debt
難易度 5/5 1週間以上 初心者へのやさしさ 8/100
メンテナーはふだん 1 日以内に返信
LibreSign/libresign の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
Automattic/blocks-engine#6318 ·
メンテナーはふだん 1 日以内に返信
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 82/100
-
35-feedback
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信