summernote-bricks/index.html at master · eissasoubhi/summernote-bricks · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <meta name="description" content="Summernote Bricks v3 release-candidate status and compatibility overview.">
  <title>Summernote Bricks v3</title>
  <style>
    :root { color-scheme: light dark; font-family: system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; }
    * { box-sizing: border-box; }
    body { margin: 0; line-height: 1.55; }
    main { width: min(920px, calc(100% - 32px)); margin: 0 auto; padding: 72px 0; }
    h1 { font-size: clamp(2.4rem, 7vw, 5rem); line-height: 1; margin: 0 0 20px; }
    h2 { margin-top: 48px; }
    .lead { font-size: 1.2rem; max-width: 720px; }
    .status { display: inline-block; padding: 6px 10px; border: 1px solid currentColor; border-radius: 999px; font-weight: 700; }
    .grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(220px, 1fr)); gap: 16px; margin-top: 24px; }
    .card { border: 1px solid color-mix(in srgb, currentColor 25%, transparent); border-radius: 12px; padding: 20px; }
    .card h3 { margin-top: 0; }
    code { font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; }
    a { color: inherit; text-underline-offset: 3px; }
    nav { display: flex; flex-wrap: wrap; gap: 16px; margin-top: 32px; }
    .note { margin-top: 40px; padding: 18px 20px; border-left: 4px solid currentColor; }
  </style>
</head>
<body>
  <main>
    <span class="status">v3 release candidate</span>
    <h1>Summernote Bricks</h1>
    <p class="lead">A small optional composer for standalone Summernote plugin buttons. The v3 source line is built around native Summernote contracts, semantic persisted HTML, strict TypeScript and reproducible package/browser validation.</p>

    <nav aria-label="Project links">
      <a href="https://github.com/eissasoubhi/summernote-bricks">Repository</a>
      <a href="https://github.com/eissasoubhi/summernote-bricks/blob/develop/README.md">v3 README</a>
      <a href="https://github.com/eissasoubhi/summernote-bricks/blob/develop/docs/V3_UPGRADE.md">Upgrade guide</a>
      <a href="https://github.com/eissasoubhi/summernote-bricks/issues/3">v3 roadmap</a>
    </nav>

    <h2>Validated ecosystem</h2>
    <div class="grid">
      <section class="card">
        <h3>Heading</h3>
        <p>Standalone semantic heading brick registered through the normal Summernote plugin lifecycle.</p>
        <a href="https://github.com/eissasoubhi/summernote-heading">summernote-heading</a>
      </section>
      <section class="card">
        <h3>Gallery</h3>
        <p>Backend-agnostic gallery brick with application-provided image sources and semantic persisted output.</p>
        <a href="https://github.com/eissasoubhi/summernote-gallery">summernote-gallery</a>
      </section>
      <section class="card">
        <h3>Bricks</h3>
        <p>Optional toolbar composition UX. It groups buttons that are already registered by standalone plugins.</p>
        <a href="https://github.com/eissasoubhi/summernote-bricks">summernote-bricks</a>
      </section>
    </div>

    <h2>Compatibility evidence</h2>
    <p>The maintained browser gate exercises Summernote <strong>0.9.1</strong> with BS3, BS4, BS5 and Lite across Chromium, Firefox and WebKit. It validates real packed Bricks, Heading and Gallery artifacts, including standalone and composed behavior.</p>

    <div class="note">
      <strong>Not published yet.</strong> The v3 source line is still release-candidate work. No v3 npm package or GitHub Release should be assumed available until explicit release approval and registry verification are complete.
    </div>

    <h2>Why there is no interactive v3 demo here yet</h2>
    <p>The previous page executed the legacy Summernote 0.8.18-era demo. Keeping that page during the v3 promotion would falsely represent the supported runtime. A new interactive demo should consume the same public package artifacts users can install, so it will follow actual v3 publication rather than vendoring an unreleased build.</p>
  </main>
</body>
</html>