> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/integrations/integrations-and-data-flow/sourceforge.md).

# SourceForge

You can now add your interactive demos to your SourceForge profile and invite your prospects as well as visitors to interact with your demos if you're a paid customer of both SourceForge and Storylane.

All you have to do is:

**Step 1:** Log in to your SourceForge dashboard and click on the “Interactive Demo” tab under "Plus Package" in the left-sided panel.

**Step 2:** From the list, find Storylane on the top, and click "Set Up".

<figure><img src="/files/sP5CDZqg9QnweMct9c0p" alt=""><figcaption></figcaption></figure>

**Step 3:** In the next screen (as seen below), enter the URL of the demo that you created on your Storylane dashboard and add the demo image you wish to set for the demo. Hit save.

<figure><img src="/files/LdGYn4DTkQT03mmscgmL" alt=""><figcaption></figcaption></figure>

**Buyer Insights**

The insights you'll receive when a prospect interacts with your demos on SourceForge are identical to what you get while embedding on your website/ sending it to buyers and will appear inside the Analytics section. This will include views, clicks, and form submissions.

**Note:** You don't have to create new copies of the demo to track your SourceForge engagement. You can simply create aliases (new links) of your demo and embed the alias onto SourceForge. Storylane analytics will then track engagement data from SourceForge separately for the alias link.


---

# 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://docs.storylane.io/integrations/integrations-and-data-flow/sourceforge.md?ask=<question>&goal=<endgoal>
```

`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.