# Link
This component is used to either navigate within your matestack application or to navigate to outside URLs.
## Parameters
This component creates an ``-tag and expects a mandatory path input and optional options parameters.
### path
If the path input is a **string** it just uses this string for the link target.
If the path input is a **symbol** (e.g. :root\_path) it calls the Rails url helper method in order to generate the link target
You can also just use the Rails url helper methods directly. They will return a string which is then used as the link target without any further processing.
### text (optional)
The text that gets wrapped by the ``-tag. If no text is given the link component looks for further arguments within itself (see examples below).
### id (optional)
Expects a string with all ids ``-tag should have.
### class (optional)
Expects a string with all classes ``-tag should have.
### method (optional, default is get)
The HTTP request method the link should implement.
### target (optional, default is nil)
Specify where to open the linked document.
### title (optional)
Specify a title for the link (shown on mouseover).
## Example 1
This example renders a simple link within a `
Here
```
## Example 2
This example renders a link without a specific link-text, so it wraps the rest of its content.
```ruby
div id: "foo", class: "bar" do
link path: "https://matestack.org", title: "The matestack website" do
plain "Here"
end
end
```
returns
```markup
```
## Example 3
This example renders a link around a div and the link opens in a new tab.
```ruby
div id: "foo", class: "bar" do
link path: "https://matestack.org", target: "_blank" do
div do
plain "Here"
end
end
end
```
returns
```markup
```
## Example 4
This example renders a link with a get request to the **root\_path** within your Rails application.
```ruby
div id: "foo", class: "bar" do
link path: :root_path do
plain "Here"
end
end
```
returns
```markup
```
## Example 5 - path from symbol
This example renders a link with a get request to any within your Rails application. In case you want to switch between pages within one specific matestack app, using the `transition` component probably is a better idea though!
```ruby
div id: "foo", class: "bar" do
link path: :inline_edit_path, text: 'Click to edit'
end
```
returns
```markup
```
## Example 6 - path from symbol with params
You can also dynamically create `paths` from symbols and params, as displayed below:
```ruby
div id: "foo", class: "bar" do
link path: :single_endpoint_path, params: {number: 1}, text: 'Call API endpoint 1'
end
```
returns
```markup
```
## Example 7 - path via Rails path helper method
You can also used Rails path helper methods:
```ruby
div id: "foo", class: "bar" do
link path: single_endpoint_path(number: 1), text: 'Call API endpoint 1'
end
```
returns
```markup
```
---
# Agent Instructions: 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:
```
GET https://docs.matestack.io/matestack-ui-core/1.5.0/components-api/core-components/link.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.