@docsector/docsector-reader 3.6.0 → 4.0.1

package/src/pages/manual/content/blocks/embedded-urls.overview.en-US.md

@@ -7,15 +7,15 @@ This block is a higher-level alternative to raw iframe markup when the source is
 ## Markdown Syntax
 
 ```html
-<d-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE" title="YouTube player demo">
+<d-block-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE" title="YouTube player demo">
 Optional caption rendered as inline Markdown.
-</d-embedded-url>
+</d-block-embedded-url>
 ```
 
 You can also omit the caption body when the provider preview already gives enough context:
 
 ```html
-<d-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P" />
+<d-block-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P" />
 ```
 
 ## Supported Providers

package/src/pages/manual/content/blocks/embedded-urls.overview.pt-BR.md

@@ -7,15 +7,15 @@ Este block é uma alternativa de nível mais alto ao uso manual de iframe quando
 ## Sintaxe Markdown
 
 ```html
-<d-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE" title="Demo do player do YouTube">
+<d-block-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE" title="Demo do player do YouTube">
 Legenda opcional renderizada como Markdown inline.
-</d-embedded-url>
+</d-block-embedded-url>
 ```
 
 Você também pode omitir o corpo quando o preview do provider já entrega contexto suficiente:
 
 ```html
-<d-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P" />
+<d-block-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P" />
 ```
 
 ## Providers suportados

package/src/pages/manual/content/blocks/embedded-urls.showcase.en-US.md

@@ -2,24 +2,24 @@
 
 ### YouTube Video
 
-<d-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE&autoplay=1&loop=1" title="YouTube player demo">
+<d-block-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE&autoplay=1&loop=1" title="YouTube player demo">
 The original playback query parameters stay attached to the provider URL.
-</d-embedded-url>
+</d-block-embedded-url>
 
 ### Spotify Track
 
-<d-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P?si=1234">
+<d-block-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P?si=1234">
 Spotify links render with the provider-specific compact player height.
-</d-embedded-url>
+</d-block-embedded-url>
 
 ### CodePen Demo
 
-<d-embedded-url url="https://codepen.io/team/codepen/pen/PNaGbb?default-tab=result" title="Interactive demo">
+<d-block-embedded-url url="https://codepen.io/team/codepen/pen/PNaGbb?default-tab=result" title="Interactive demo">
 Use the same block for live front-end demos without dropping to raw HTML.
-</d-embedded-url>
+</d-block-embedded-url>
 
 ### Unsupported URL Fallback
 
-<d-embedded-url url="https://example.com/docs/embed-me" title="External API docs">
+<d-block-embedded-url url="https://example.com/docs/embed-me" title="External API docs">
 Unsupported providers render a safe link card so the reading flow still keeps the URL visible and actionable.
-</d-embedded-url>
+</d-block-embedded-url>

package/src/pages/manual/content/blocks/embedded-urls.showcase.pt-BR.md

@@ -2,24 +2,24 @@
 
 ### Vídeo do YouTube
 
-<d-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE&autoplay=1&loop=1" title="Demo do player do YouTube">
+<d-block-embedded-url url="https://www.youtube.com/watch?v=M7lc1UVf-VE&autoplay=1&loop=1" title="Demo do player do YouTube">
 Os parâmetros originais de reprodução continuam anexados à URL do provider.
-</d-embedded-url>
+</d-block-embedded-url>
 
 ### Faixa do Spotify
 
-<d-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P?si=1234">
+<d-block-embedded-url url="https://open.spotify.com/track/7ouMYWpwJ422jRcDASZB7P?si=1234">
 Links do Spotify renderizam com a altura compacta específica do provider.
-</d-embedded-url>
+</d-block-embedded-url>
 
 ### Demo no CodePen
 
-<d-embedded-url url="https://codepen.io/team/codepen/pen/PNaGbb?default-tab=result" title="Demo interativa">
+<d-block-embedded-url url="https://codepen.io/team/codepen/pen/PNaGbb?default-tab=result" title="Demo interativa">
 Use o mesmo block para demos front-end ao vivo sem cair para HTML bruto.
-</d-embedded-url>
+</d-block-embedded-url>
 
 ### Fallback para URL não suportada
 
-<d-embedded-url url="https://example.com/docs/embed-me" title="Documentação externa da API">
+<d-block-embedded-url url="https://example.com/docs/embed-me" title="Documentação externa da API">
 Providers não suportados renderizam um card seguro com link externo, mantendo a URL visível e acionável no fluxo de leitura.
-</d-embedded-url>
+</d-block-embedded-url>

package/src/pages/manual/content/blocks/expandable.overview.en-US.md

@@ -4,32 +4,32 @@ Expandable blocks collapse secondary content behind a clickable title.
 
 They are a good fit when the main section should stay short, but readers may still need optional details, checklists, appendix material, or longer examples.
 
-The block is authored with the custom Markdown element `<d-expandable>`.
+The block is authored with the custom Markdown element `<d-block-expandable>`.
 
 ## HTML Example
 
 The custom element can be authored directly in page Markdown:
 
 ````html
-<d-expandable title="Why hide this content?">
+<d-block-expandable title="Why hide this content?">
 
 Use expandable blocks when the main section should stay concise but readers may still need more detail.
 
-</d-expandable>
+</d-block-expandable>
 
 ### Open by Default
 
-<d-expandable title="Release checklist" open="true">
+<d-block-expandable title="Release checklist" open="true">
 
 - Review breaking changes
 - Update screenshots
 - Run smoke tests
 
-</d-expandable>
+</d-block-expandable>
 
 ### Rich Content
 
-<d-expandable title="Deployment appendix">
+<d-block-expandable title="Deployment appendix">
 
 > [!TIP]
 > Keep the primary flow in the main section and move optional details here.
@@ -39,11 +39,11 @@ npm install
 npm run build
 ```
 
-</d-expandable>
+</d-block-expandable>
 ````
 
 ## Notes
 
 - Use `open="true"` when the section should start expanded.
 - Keep page headings outside the expandable block. Headings inside the body are flattened to regular paragraphs so the page ToC stays stable.
-- Avoid nesting one `<d-expandable>` inside another in this first version.
+- Avoid nesting one `<d-block-expandable>` inside another in this first version.

package/src/pages/manual/content/blocks/expandable.overview.pt-BR.md

@@ -4,32 +4,32 @@ Blocos expansíveis recolhem conteúdo secundário atrás de um título clicáve
 
 Eles funcionam bem quando a seção principal precisa continuar curta, mas o leitor ainda pode precisar de detalhes opcionais, checklists, apêndices ou exemplos mais longos.
 
-O bloco é escrito com o custom element Markdown `<d-expandable>`.
+O bloco é escrito com o custom element Markdown `<d-block-expandable>`.
 
 ## Exemplo em HTML
 
 O custom element pode ser escrito diretamente no Markdown da página:
 
 ````html
-<d-expandable title="Por que esconder este conteúdo?">
+<d-block-expandable title="Por que esconder este conteúdo?">
 
 Use blocos expansíveis quando a seção principal deve continuar concisa, mas o leitor ainda pode precisar de mais detalhes.
 
-</d-expandable>
+</d-block-expandable>
 
 ### Aberto por Padrão
 
-<d-expandable title="Checklist de release" open="true">
+<d-block-expandable title="Checklist de release" open="true">
 
 - Revisar breaking changes
 - Atualizar screenshots
 - Rodar smoke tests
 
-</d-expandable>
+</d-block-expandable>
 
 ### Conteúdo Rico
 
-<d-expandable title="Apêndice de deploy">
+<d-block-expandable title="Apêndice de deploy">
 
 > [!TIP]
 > Mantenha o fluxo principal na seção principal e mova detalhes opcionais para cá.
@@ -39,11 +39,11 @@ npm install
 npm run build
 ```
 
-</d-expandable>
+</d-block-expandable>
 ````
 
 ## Observações
 
 - Use `open="true"` quando a seção precisar começar aberta.
 - Mantenha os títulos principais fora do bloco expansível. Títulos dentro do corpo viram parágrafos comuns para manter o ToC estável.
-- Evite aninhar um `<d-expandable>` dentro de outro nesta primeira versão.
+- Evite aninhar um `<d-block-expandable>` dentro de outro nesta primeira versão.

package/src/pages/manual/content/blocks/expandable.showcase.en-US.md

@@ -2,25 +2,25 @@
 
 ### Basic
 
-<d-expandable title="Why hide this content?">
+<d-block-expandable title="Why hide this content?">
 
 Use expandable blocks when the main section should stay concise but readers may still need more detail.
 
-</d-expandable>
+</d-block-expandable>
 
 ### Open by Default
 
-<d-expandable title="Release checklist" open="true">
+<d-block-expandable title="Release checklist" open="true">
 
 - Review breaking changes
 - Update screenshots
 - Run smoke tests
 
-</d-expandable>
+</d-block-expandable>
 
 ### Rich Content
 
-<d-expandable title="Deployment appendix">
+<d-block-expandable title="Deployment appendix">
 
 > [!TIP]
 > Keep the primary flow in the main section and move optional details here.
@@ -30,4 +30,4 @@ npm install
 npm run build
 ```
 
-</d-expandable>
+</d-block-expandable>

package/src/pages/manual/content/blocks/expandable.showcase.pt-BR.md

@@ -2,25 +2,25 @@
 
 ### Básico
 
-<d-expandable title="Por que esconder este conteúdo?">
+<d-block-expandable title="Por que esconder este conteúdo?">
 
 Use blocos expansíveis quando a seção principal deve continuar concisa, mas o leitor ainda pode precisar de mais detalhes.
 
-</d-expandable>
+</d-block-expandable>
 
 ### Aberto por Padrão
 
-<d-expandable title="Checklist de release" open="true">
+<d-block-expandable title="Checklist de release" open="true">
 
 - Revisar breaking changes
 - Atualizar screenshots
 - Rodar smoke tests
 
-</d-expandable>
+</d-block-expandable>
 
 ### Conteúdo Rico
 
-<d-expandable title="Apêndice de deploy">
+<d-block-expandable title="Apêndice de deploy">
 
 > [!TIP]
 > Mantenha o fluxo principal na seção principal e mova detalhes opcionais para cá.
@@ -30,4 +30,4 @@ npm install
 npm run build
 ```
 
-</d-expandable>
+</d-block-expandable>

package/src/pages/manual/content/blocks/files.overview.en-US.md

@@ -7,15 +7,15 @@ They are useful for checklists, sample bundles, PDFs, release notes, and any oth
 ## Markdown Syntax
 
 ```html
-<d-file src="/files/manual/release-checklist.txt" title="Release checklist" size="1 KB">
+<d-block-file src="/files/manual/release-checklist.txt" title="Release checklist" size="1 KB">
 Download the example attachment used in this manual.
-</d-file>
+</d-block-file>
 ```
 
 You can also omit the caption body when the file name already provides enough context:
 
 ```html
-<d-file src="/files/manual/release-checklist.txt" size="1 KB" />
+<d-block-file src="/files/manual/release-checklist.txt" size="1 KB" />
 ```
 
 ## Notes

package/src/pages/manual/content/blocks/files.overview.pt-BR.md

@@ -7,15 +7,15 @@ Eles são úteis para checklists, bundles de exemplo, PDFs, notas de release e q
 ## Sintaxe em Markdown
 
 ```html
-<d-file src="/files/manual/release-checklist.txt" title="Checklist de release" size="1 KB">
+<d-block-file src="/files/manual/release-checklist.txt" title="Checklist de release" size="1 KB">
 Baixe o anexo de exemplo usado neste manual.
-</d-file>
+</d-block-file>
 ```
 
 Você também pode omitir o corpo da legenda quando o nome do arquivo já fornece contexto suficiente:
 
 ```html
-<d-file src="/files/manual/release-checklist.txt" size="1 KB" />
+<d-block-file src="/files/manual/release-checklist.txt" size="1 KB" />
 ```
 
 ## Observações

package/src/pages/manual/content/blocks/files.showcase.en-US.md

@@ -2,16 +2,16 @@
 
 ### Local File with Caption
 
-<d-file src="/files/manual/release-checklist.txt" title="Release checklist" size="1 KB">
+<d-block-file src="/files/manual/release-checklist.txt" title="Release checklist" size="1 KB">
 Download the example checklist published from `public/files/manual`.
-</d-file>
+</d-block-file>
 
 ### Local File with Automatic Size
 
-<d-file src="/files/manual/release-checklist.txt" />
+<d-block-file src="/files/manual/release-checklist.txt" />
 
 ### External File URL
 
-<d-file src="https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf" title="Reference PDF" size="13 KB">
+<d-block-file src="https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf" title="Reference PDF" size="13 KB">
 The same block can point to a CDN or object storage URL without changing the page layout.
-</d-file>
+</d-block-file>

package/src/pages/manual/content/blocks/files.showcase.pt-BR.md

@@ -2,16 +2,16 @@
 
 ### Arquivo Local com Legenda
 
-<d-file src="/files/manual/release-checklist.txt" title="Checklist de release" size="1 KB">
+<d-block-file src="/files/manual/release-checklist.txt" title="Checklist de release" size="1 KB">
 Baixe o checklist de exemplo publicado a partir de `public/files/manual`.
-</d-file>
+</d-block-file>
 
 ### Arquivo Local com Tamanho Automático
 
-<d-file src="/files/manual/release-checklist.txt" />
+<d-block-file src="/files/manual/release-checklist.txt" />
 
 ### URL Externa de Arquivo
 
-<d-file src="https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf" title="PDF de referência" size="13 KB">
+<d-block-file src="https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf" title="PDF de referência" size="13 KB">
 O mesmo bloco pode apontar para um CDN ou URL de object storage sem mudar o layout da página.
-</d-file>
+</d-block-file>

package/src/pages/manual/content/blocks/quick-links.overview.en-US.md

@@ -7,18 +7,18 @@ They are useful for homepages, landing sections, and any page that should offer
 ## Markdown Syntax
 
 ```html
-<d-quick-links title="Get started">
-  <d-quick-link
+<d-block-quick-links title="Get started">
+  <d-block-quick-link
     title="Install"
     description="Set up the project"
     to="/guide/getting-started"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="GitHub"
     description="Open the repository"
     href="https://github.com/docsector/docsector-reader"
   />
-</d-quick-links>
+</d-block-quick-links>
 ```
 
 ## Notes

package/src/pages/manual/content/blocks/quick-links.overview.pt-BR.md

@@ -7,18 +7,18 @@ Eles são úteis para homepages, seções de entrada e qualquer página que prec
 ## Sintaxe em Markdown
 
 ```html
-<d-quick-links title="Comece aqui">
-  <d-quick-link
+<d-block-quick-links title="Comece aqui">
+  <d-block-quick-link
     title="Instalação"
     description="Configure o projeto"
     to="/guide/getting-started"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="GitHub"
     description="Abra o repositório"
     href="https://github.com/docsector/docsector-reader"
   />
-</d-quick-links>
+</d-block-quick-links>
 ```
 
 ## Observações

package/src/pages/manual/content/blocks/quick-links.showcase.en-US.md

@@ -1,34 +1,34 @@
 ## Showcase
 
-<d-quick-links title="Continue reading">
-  <d-quick-link
+<d-block-quick-links title="Continue reading">
+  <d-block-quick-link
     title="Getting Started"
     description="Install and run the project"
     to="/guide/getting-started"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="Headings"
     description="Open a block example with showcase"
     to="/manual/content/blocks/headings"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="GitHub"
     description="Open the repository"
     href="https://github.com/docsector/docsector-reader"
   />
-</d-quick-links>
+</d-block-quick-links>
 
 ## Smaller Group
 
-<d-quick-links title="Next actions">
-  <d-quick-link
+<d-block-quick-links title="Next actions">
+  <d-block-quick-link
     title="Page structure"
     description="Read the page container overview"
     to="/manual/content/structures/page"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="Quick Links overview"
     description="Return to the reference page"
     to="/manual/content/blocks/quick-links"
   />
-</d-quick-links>
+</d-block-quick-links>

package/src/pages/manual/content/blocks/quick-links.showcase.pt-BR.md

@@ -1,34 +1,34 @@
 ## Demonstração
 
-<d-quick-links title="Continue lendo">
-  <d-quick-link
+<d-block-quick-links title="Continue lendo">
+  <d-block-quick-link
     title="Começando"
     description="Instale e rode o projeto"
     to="/guide/getting-started"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="Títulos"
     description="Abra um exemplo de bloco com showcase"
     to="/manual/content/blocks/headings"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="GitHub"
     description="Abra o repositório"
     href="https://github.com/docsector/docsector-reader"
   />
-</d-quick-links>
+</d-block-quick-links>
 
 ## Grupo Menor
 
-<d-quick-links title="Próximas ações">
-  <d-quick-link
+<d-block-quick-links title="Próximas ações">
+  <d-block-quick-link
     title="Estrutura de página"
     description="Leia o overview do container de page"
     to="/manual/content/structures/page"
   />
-  <d-quick-link
+  <d-block-quick-link
     title="Overview de Quick Links"
     description="Volte para a página de referência"
     to="/manual/content/blocks/quick-links"
   />
-</d-quick-links>
+</d-block-quick-links>

package/src/pages/manual/content/blocks/stepper.overview.en-US.md

@@ -0,0 +1,59 @@
+## Overview
+
+Stepper blocks render a native Quasar vertical Stepper inside Markdown, combining numbered headers, built-in navigation, and rich step content.
+
+They work well for onboarding flows, installation guides, release routines, and troubleshooting instructions where readers should move through a sequence in order.
+
+The block is authored with the custom Markdown elements `<d-block-stepper>` and `<d-block-step>`.
+
+## HTML Example
+
+````html
+<d-block-stepper>
+  <d-block-step title="Install dependencies">
+
+Run `npm install` in the project root.
+
+  </d-block-step>
+
+  <d-block-step title="Start the development server">
+
+Run `npm run dev` and open the local URL shown in the terminal.
+
+  </d-block-step>
+
+  <d-block-step title="Verify the result">
+
+> [!TIP]
+> Keep each step focused on one outcome.
+
+```bash
+npm run test
+```
+
+  </d-block-step>
+
+  <d-block-step
+    title="Ship the release"
+    icon="rocket_launch"
+    active-icon="rocket_launch"
+    done-icon="task_alt"
+  >
+
+Use icon attributes when a numbered prefix is not expressive enough for the step.
+
+  </d-block-step>
+</d-block-stepper>
+````
+
+## Notes
+
+- Every `<d-block-step>` must define a `title`.
+- The block uses Quasar's native vertical Stepper, so readers can move through the sequence using the step headers or the built-in navigation buttons.
+- Step bodies support regular Markdown content such as paragraphs, lists, alerts, code fences, images, tables, and math.
+- Each step can override the header icon through `icon`, `active-icon`, `done-icon`, and `error-icon`.
+- Intermediate steps show Continue and Back actions; the last step swaps the primary action to Finish.
+- Readers can also jump to any step directly from the headers.
+- Only the active step body is expanded at a time; previous and next steps stay visible in the header stack.
+- Headings inside a step are flattened into paragraph output so the page table of contents stays stable.
+- Treat nested Stepper blocks and other custom Docsector blocks inside a step as unsupported in this first version.

package/src/pages/manual/content/blocks/stepper.overview.pt-BR.md

@@ -0,0 +1,59 @@
+## Visão geral
+
+Os blocos Stepper renderizam o Stepper vertical nativo do Quasar dentro do Markdown, combinando cabeçalhos numerados, navegação embutida e conteúdo rico em cada etapa.
+
+Eles funcionam bem em onboarding, instalação, rotinas de release e instruções de troubleshooting nas quais a leitura deve seguir uma sequência.
+
+O bloco é escrito com os custom elements Markdown `<d-block-stepper>` e `<d-block-step>`.
+
+## Exemplo em HTML
+
+````html
+<d-block-stepper>
+  <d-block-step title="Instale as dependências">
+
+Execute `npm install` na raiz do projeto.
+
+  </d-block-step>
+
+  <d-block-step title="Inicie o servidor de desenvolvimento">
+
+Execute `npm run dev` e abra a URL local mostrada no terminal.
+
+  </d-block-step>
+
+  <d-block-step title="Valide o resultado">
+
+> [!TIP]
+> Mantenha cada etapa focada em um único resultado.
+
+```bash
+npm run test
+```
+
+  </d-block-step>
+
+  <d-block-step
+    title="Publique a release"
+    icon="rocket_launch"
+    active-icon="rocket_launch"
+    done-icon="task_alt"
+  >
+
+Use atributos de ícone quando a numeração sozinha não for expressiva o bastante para a etapa.
+
+  </d-block-step>
+</d-block-stepper>
+````
+
+## Observações
+
+- Todo `<d-block-step>` precisa definir `title`.
+- O bloco usa o Stepper vertical nativo do Quasar, então a leitura pode avançar pelos cabeçalhos das etapas ou pelos botões de navegação embutidos.
+- O corpo de cada etapa aceita Markdown comum, como parágrafos, listas, alertas, blocos de código, imagens, tabelas e matemática.
+- Cada etapa pode sobrescrever o ícone do cabeçalho com `icon`, `active-icon`, `done-icon` e `error-icon`.
+- As etapas intermediárias mostram Continuar e Voltar; na última etapa, a ação principal muda para Finalizar.
+- A navegação também pode ser feita diretamente pelos cabeçalhos.
+- Apenas o corpo da etapa ativa fica expandido por vez; as demais etapas continuam visíveis na pilha de cabeçalhos.
+- Títulos dentro de uma etapa são achatados para parágrafos, mantendo a tabela de conteúdos da página estável.
+- Nesta primeira versão, trate Stepper aninhado e outros custom blocks do Docsector dentro de uma etapa como conteúdo não suportado.