Tight coupling of integration with smart contracts to building dapps

[janewang]

In our docs today, we seem to have an assumption that anyone integrating with smart contracts is building a dapp, but I think dapp developers are a small part of the audience that needs to know how to integrate with smart contracts. The people that build dapps are generally the same people that built the smart contract it integrates with. But for every smart contract built, there are N applications that may want to integrate with it. For example, we're leaving out wallets like Meru who integrated directly with the Blend protocol, or exchanges and issuers that will need to invoke functions on token contracts.
How can we refactor the docs content we have to support all audiences? I've found a few sections with content that could be reusable:
In our Build Applications section, we have two different sections on building different flavors or aspects of dapps (Guestbook, Dapp Frontend). There is really valuable information in the former that isn't exclusive to dapp developers (ex. generating bindings), which could be pulled out and expanded upon to include generating bindings in other languages like Java, which isn't possible with the CLI. Unfortunately, all the content that demonstrates how to use those bindings is interwoven with content on building a frontend using HTML and JavaScript.
In our How-To Guides section, we have a Dapp Development subsection which has a ton of relevant info as well (ex. interacting with smart contracts) but again its interwoven with React code and doesn't have good SEO

thread: https://stellarfoundation.slack.com/archives/C049E67BFSP/p1742319714952089