Meta tags:
description=The Block Kit UI framework is built with blocks, block elements and composition objects.;

Headings (most frequently used words):

blocks, block, kit, placing, within, surfaces, building, adding, interactivity, to, with, elements, onward, defining, single, stacking, multiple, accessibility, considerations,

Text of the page (most frequently used words):
block (40), blocks (39), the (33), kit (20), and (20), text (19), you (18), app (17), type (17), slack (14), your (12), elements (12), #surfaces (12), with (11), for (10), can (10), builder (9), all (8), that (8), section (8), will (7), apps (6), interactive (6), read (6), mrkdwn (6), example (6), each (6), modals (6), within (5), objects (5), reference (5), guide (5), when (5), content (5), messages (5), resources (4), interactivity (4), using (4), view (4), composition (4), components (4), add (4), button (4), include (4), field (4), message (4), array (4), preview (4), layouts (4), com (4), request (4), fields (4), visual (4), home (4), are (4), developer (3), learn (3), tools (3), stacking (3), building (3), check (3), guides (3), individual (3), buttons (3), this (3), users (3), top (3), level (3), from (3), screen (3), used (3), like (3), them (3), json (3), tabs (3), their (2), privacy (2), changelog (2), manage (2), marketplace (2), docs (2), community (2), learning (2), samples (2), program (2), onward (2), adding (2), accessibility (2), considerations (2), multiple (2), defining (2), single (2), placing (2), overview (2), out (2), alternatively (2), need (2), manually (2), element (2), start (2), our (2), prepare (2), user (2), interaction (2), action (2), plain_text (2), here (2), such (2), menus (2), not (2), allow (2), reader (2), created (2), different (2), use (2), https (2), fred (2), enriquez (2), time (2), off (2), new (2), want (2), together (2), create (2), skip (2), contains (2), every (2), available (2), other (2), apis (2), how (2), tab (2), built (2), enterprise (2), 2026, technologies, llc, salesforce, company, rights, reserved, various, trademarks, held, respective, owners, choices, support, cookie, preferences, terms, status, newsletter, blog, events, resource, library, trailhead, certifications, workshops, paths, code, tutorials, sdks, bolt, frameworks, cli, copy, markdown, next, auth0, sign, links, previous, including, following, everything, allows, well, give, try, info, implementing, handle, requests, flow, way, respond, appropriately, follow, inspire, handling, component, surface, opened, door, people, push, expecting, helpful, prompt, reaction, action_id, click_me_123, value, true, emoji, click, accessory, made, interact, via, inputs, has, attempt, build, appending, supported, necessary, posting, expected, behavior, readers, default, post, any, interior, underlying, structure, therefore, make, accessible, must, either, newly, range, generate, complete, one, shown, above, drag, drop, rearrange, design, naug, aug, npaid, header, chosen, layout, place, order, stacked, complex, specifications, required, prototyping, sandbox, let, choose, configure, specifying, which, along, describe, paid, represented, object, there, special, setup, needed, however, just, open, pack, generic, colorful, interlocking, plastic, bricks, should, instructions, first, compatible, some, only, particular, more, about, these, uses, designed, construct, stacks, love, consume, eager, see, take, peek, whether, composing, experience, same, sculpting, specially, structured, express, itself, result, clear, communication, between, its, define, options, features, certain, may, also, contain, usually, arranged, 100, framework, page, 日本語版ページ, legacy, workflows, messaging, govslack, search, upgrading, outmoded, dialogs, formatting, rich, authentication, admin, manifests, management, platform, concepts, quickstart, welcome, dev, main,

Text of the page (random words):
block kit slack developer docs guide skip to main content guides reference samples tools changelog dev program manage apps welcome quickstart resources slack platform concepts ai in slack apis app management app manifests admin resources authentication block kit overview formatting with rich text upgrading outmoded dialogs to modals enterprise enterprise search for apps govslack interactivity messaging slack marketplace surfaces workflows legacy 日本語版ページ block kit on this page block kit the block kit ui framework is built with blocks block elements and composition objects blocks are visual components that can be arranged to create app layouts apps can add blocks to surfaces like the home tab messages and modals you can include up to 50 blocks in each message and 100 blocks in modals or home tabs blocks may also contain block elements block elements are usually interactive components such as buttons and menus blocks and block elements are built with composition objects composition objects define text options or other interactive features within certain blocks and block elements whether you re composing layouts for modals messages or tabs the block kit building experience is the same your app will be sculpting specially structured json to express itself the result is clear interactive communication between your app and its users eager to see block kit in action take a peek in block kit builder read on to learn how you can construct the stacks of blocks that app surfaces love to consume placing blocks within surfaces blocks are used within all app surfaces home tabs messages and modals can all be designed using blocks each of them uses a blocks array that you prepare by stacking individual blocks together check out app surfaces to learn more about using these different surfaces and how to add blocks to your app s home tab messages and modals some blocks can only be used in particular app surfaces read the block kit reference guides to check if a block is compatible with your app s surfaces building blocks there s no special setup needed to start using blocks in app surfaces however just as when you open a pack of generic colorful interlocking plastic bricks you should read the instructions first defining a single block each block is represented in our apis as a json object here s an example of a section block type section text type mrkdwn text new paid time off request from example com fred enriquez n n https example com view request preview in block kit builder every block contains a type field specifying which of the available blocks to use along with other fields that describe the content of the block block kit builder is a visual prototyping sandbox that will let you choose from configure and preview all the available blocks if you want to skip the builder the block reference guide contains the specifications of every block and the json fields required for each of them stacking multiple blocks individual blocks can be stacked together to create complex visual layouts when you ve chosen each of the blocks you want in your layout place each of them in an array in visual order like this type header text type plain_text text new request type section fields type mrkdwn text type npaid time off type mrkdwn text created by n example com fred enriquez type section fields type mrkdwn text when naug 10 aug 13 type section text type mrkdwn text https example com view request preview in block kit builder block kit builder will allow you to drag drop and rearrange blocks to design and preview block kit layouts alternatively you can use the block reference guide to manually generate a complete blocks array like the one shown above your newly created array of blocks can be used with a range of different app surfaces accessibility considerations when posting messages it is expected behavior that screen readers will default to the top level text field of the post and will not read the content of any interior blocks in the underlying structure of the message therefore to make an accessible app you must either include all necessary content for screen reader users in the top level text field of your message or do not include a top level text field if the message has blocks and allow slack attempt to build it for you by appending content from supported blocks to be read by the screen reader adding interactivity to blocks with block elements blocks can be made to interact with users via block kit elements elements include interactive components such as buttons menus and text inputs here s an example of a button element within a section block blocks type section text type mrkdwn text this is a section block with a button accessory type button text type plain_text text click me emoji true value click_me_123 action_id button action view in block kit builder when you add an interactive component to a surface in your slack app you ve opened the door to user interaction people will push your app s buttons and expecting a helpful and prompt reaction apps need to handle the requests that start to flow their way and respond appropriately follow our guide to handling user interaction to prepare your app for the interactivity that block kit will inspire block kit builder allows you to add elements to blocks as well give it a try alternatively read the block kit element reference guide for all the info you ll need for manually implementing individual elements onward check out the following guides for everything blocks blocks block elements including interactive components composition objects view objects previous using auth0 for sign in with slack links next overview copy as markdown placing blocks within surfaces building blocks defining a single block stacking multiple blocks accessibility considerations adding interactivity to blocks with block elements onward tools slack cli bolt frameworks slack sdks block kit builder developer program code samples tutorials all tools learn learning paths workshops slack certifications trailhead resource library all learning resources community slack community slack events resources docs blog slack marketplace developer newsletter manage apps your apps status privacy terms cookie preferences support changelog your privacy choices 2026 slack technologies llc a salesforce company all rights reserved various trademarks held by their respective owners