> 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/hubs-docs/integrations-hub/integrations/sourceforge.md).
# SourceForge
Engage prospective buyers when they visit your SourceForge profile
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".
**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.
**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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.storylane.io/hubs-docs/integrations-hub/integrations/sourceforge.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.
.png)
