> For the complete documentation index, see [llms.txt](https://attr.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attr.sygnal.com/sa5-embeds/table-embeds/future.md). # Future ## Image Previews Some content will just be too large to display in the intended space. Three options; * Image Previews * Scaling * Scrolling ## Content Embeds Future Possibly add smart URL conversions, e.g. video embedding Possibly look to pull certain styling * Cell color, text color, highlight, bold, italics * Alignment or justification ## Themes Support all natural content forms in Google doc ## Controls Consider row-level controls, e.g. custom CSS Header controls Subheader controls Column level controls CSS grid conversion support to FR's Scrollable - plus clear indicators and mobile support SA5 DATA ## Responsiveness * Possible smart change from a grid view to an item view * Desktop = row and column table format * Mobile = item view, with column headers duplicated as row headers and items individually shown Smart view * Sorting and filtering, smart headers, etc * Pagination? --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://attr.sygnal.com/sa5-embeds/table-embeds/future.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.