-
Notifications
You must be signed in to change notification settings - Fork 81
[epic] migrate Soroban Docs into Stellar Docs #740
Comments
Hi Elliot great work, I was looking into one of the Todo points you mentioned
Have you explored using the |
Hi, Brian! Thanks for the suggestion! I've come across the unrelated histories flag as a probable solution, but haven't yet taken the time to figure out precisely how to use it. Do you have any experience with it? If so, I'd love some pointers. For a quasi-hypothetical example: Suppose I wanted to take all of the files that are located in the Not that you have to have the answers lol, just tossing out some of the thoughts that have been rattling around in my head. Thanks again! |
Hi Elliot, those are very good questions. Our team was doing it when migrating to a monorepo but we had additional tooling in place. |
Hi, if I want to submit a PR to add Java SDK example here, is it better to wait until the migration is completed and then submit it to stellar-docs, or is it better to submit it to this repo now? |
@thisBrian I actually did some toying around with it yesterday, and I think i did reasonably well with the soroban-rpc stuff. It's on this PR: stellar/stellar-docs#325 I found a couple people posting guides for similar stuff online, but I don't exactly recall which ones I used. I'll try to write down a "post-mortem" for how I did it (for future reference) today or tomorrow.
@overcat Is your Java example, already written and just "looking for a home" or will it need some time and iteration? My gut says go ahead and submit it here. We could target the |
We have already submitted and merged it. |
Hi there! That page should be available here: https://developers.stellar.org/network/anchor-platform/admin-guide/sep24/integration |
Since the Stellar Mainnet validators have affirmatively voted to upgrade the network to protocol version 20, now we begin the task of combining this documentation repository and the stellar/stellar-docs repository.
This issue will serve to track all the work needed to move content, as well as redirect where necessary.
The general process will be:
stellar-docs
repo that serves to put the content of a section of documentation from this repo into the new one.soroban-docs
repo that will redirect URLs and remove content (where applicable) from this repo.Once that PR is ready, rinse and repeat. Several of these changes may involve merging main back into the feature branch along the way.
Done
stellar-docs
that says "pardon our dust" or something. ([Soroban Merge] add announcement bar about the migration stellar/stellar-docs#311)soroban-docs
that says "we're moving" or something. ([Stellar Merge] Announcement Bar #742)In-Progress
v2
version (Docusaurus v3 upgrade preparation stellar/stellar-docs#405)v3
version (do this after the dapps challenge)The text was updated successfully, but these errors were encountered: