> For the complete documentation index, see [llms.txt](https://bcds.gitbook.io/handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bcds.gitbook.io/handbook/digital-scholarship-methods/introduction-to-digital-exhibits/platforms.md). # ΒΆ Platforms Platform selection will influence decisions about site organization and design, among other things. You may or may not start out knowing what platform you want to use, or you may change your mind about the chosen platform based on the way you want to organize your exhibit, the way you want visitors to interact with it, and whether you want to have the object available in digital collection form as well. Some considerations that should be made when considering platforms include: * Ease of use and customizability * Whether there needs to be a searchable collections component * Whether exhibits should be navigable linearly, non-linearly, or both * The types and level of interactivity desired * Accessibility for the disabled Some common platform options: * Omeka ([.net](https://www.omeka.net/) and [.org](https://omeka.org/)) \[[accessibility statement](https://omeka.org/classic/docs/GettingStarted/Accessibility_Statement/)] * [Exhibit.so](https://exhibit.so/) - [ ](https://exhibit.so/docs/accessibility-statement)\[[accessibility statement](https://exhibit.so/docs/accessibility-statement)] * [Scalar](https://scalar.me/anvc/scalar/) * Wordpress (.[com](https://wordpress.com/) and .[org](https://wordpress.org/)) \[[accessibility statement](https://wordpress.org/about/accessibility/)] * [ArcGIS Story Maps](https://storymaps.arcgis.com/) \[[accessibility guidance](https://www.esri.com/arcgis-blog/products/arcgis-storymaps/constituent-engagement/writing-accessible-story-map-content/)] * For more information, see [Comparing Systems for Creating Digital Exhibits](https://docs.google.com/document/d/1eOxHfZBiIAk562WZaM2mbt-beMX0uvfPuQSHWyd3h0Q/edit) by Dr. Pamella Lach --- # 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://bcds.gitbook.io/handbook/digital-scholarship-methods/introduction-to-digital-exhibits/platforms.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.