> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/reference/platform-concepts.md). # Platform concepts Across Appfarm Create there are a number of important **platform concepts**, primarily for advanced data manipulation and formatting.


Conditions	Compare values and add dynamic behavior to an app.	conditions.png	Conditions
Data bindings	Connect UI components and action nodes to data.	data_binding.png	Data bindings
Date and time	Manipulate, format, and localize datetime values.	date-time.png	Date and time
Event handlers	Trigger actions based on automatic and user-initiated events.	event_handlers.png	Event handlers
Filters	Create a subset of data to display or process.	filters.png	Filters
Find references	Quickly locate dependencies in your solution.	find_references.png	Find references
Functions	Run advanced conditions and calculations using JavaScript.	functions.png	Functions
Markdown	Format plain text for display in the UI.	markdown.png	Markdown
Objects	A data structure used to store and reference data.	objects.png	Objects
Operators	Compare values when building conditions and filters.	operators.png	Operators
Value processor	Perform simple operations to manipulate and format data.	value-processor.png	Value processor

--- # 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://docs.appfarm.io/reference/platform-concepts.md?ask=&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.