> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/developer-hub/readme.md).

# S-Docs Developer Hub

Technical reference for S-Docs architecture, SDKs, Flow actions, template logic, and S-Sign extensibility.

Use this hub as the technical source of truth for programmatic document generation, system architecture, e-signature extensibility, and advanced template logic. Start here when you need schemas, execution patterns, SDK entry points, and merge-layer syntax.

### System Architecture & Schema

Use this section to understand the internal processing engine, transaction boundaries, and the core data model.

#### S-Docs architecture & schema

Use this section to understand the S-Docs generation engine, document transaction flow, and core document data model. It includes the S-Docs ERD and object reference for generation-layer analysis.

* [How S-Docs Generates Documents](/developer-hub/s-docs-system-architecture/how-s-docs-generates-documents.md)
* [S-Docs Objects](/developer-hub/s-docs-system-architecture/s-docs-objects.md)
* [S-Docs Entity-Relationship Diagram](/developer-hub/s-docs-system-architecture/s-docs-entity-relationship-diagram.md)

#### S-Sign architecture & schema

Use this section to understand the S-Sign envelope engine, signing transaction flow, and core e-signature data model. It includes the S-Sign ERD and object reference for envelope and licensing analysis.

* [How S-Sign Generates Envelopes](/developer-hub/s-sign-system-architecture/how-s-sign-generates-envelopes.md)
* [S-Sign Objects](/developer-hub/s-sign-system-architecture/s-sign-objects.md)
* [S-Sign Entity-Relationship Diagram](/developer-hub/s-sign-system-architecture/s-sign-entity-relationship-diagram.md)

### Automation & Programmatic Interfaces

Use this section to invoke generation through Apex, Flow, and Lightning runtime. It covers Apex SDK methods, LWC references, and Flow invocable actions, including bulkification behavior and transaction limits.

* [Flow Reference](/developer-hub/document-workflows/flow-reference.md)
* [S-Docs LWC Reference](/developer-hub/document-workflows/s-docs-lwc-reference.md)
* [Method Reference](/developer-hub/document-workflows/software-development-kit/document-generation.md) and [Method: generateDocsInBatch](/developer-hub/document-workflows/software-development-kit/document-generation/method-generatedocsinbatch.md)

### Advanced Template Logic

Use this section to build complex dynamic documents. It covers Named Queries for custom SOQL injection, Component Templates for reusable document blocks, and Conditional Logic parsing for runtime rendering.

* [Named Query Reference](/developer-hub/template-configuration-and-styling/reference-named-query-syntax.md)
* [Component Template Reference Guide](/developer-hub/template-configuration-and-styling/component-template-reference-guide.md)
* [Conditional Logic Reference](/developer-hub/template-configuration-and-styling/conditional-logic-reference.md)

### Document Lifecycle & S-Sign Extensibility

Use this section when generation is only the first transaction. It covers post-generation routing through Document Actions and S-Sign Apex licensing and envelope mechanics for custom signing flows.

* [Document Actions](broken://spaces/qNhwNwsut3uqS2daHMHX/pages/f2WgR0XzXNL2F93lqMfP)
* [Reference: Document Actions Framework](/developer-hub/document-workflows/software-development-kit/reference-document-actions-framework.md)
* [S-Sign Licensing (Apex)](/developer-hub/s-sign-system-architecture/s-sign-licensing-apex.md) and [How S-Sign Generates Envelopes](/developer-hub/s-sign-system-architecture/how-s-sign-generates-envelopes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/developer-hub/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.