🔧 Setup site publication - moves blogs + sitemap#14
Draft
JFWooten4 wants to merge 4 commits into
Draft
Conversation
✅ Deploy Preview for blocktransfer ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now this repo mostly houses compliance docs which are derived from what will be TIPS in the
TAD3repo. I'd like to keep it minimal since the access permissioning reviews around the Stellar TOMLs, and I want to set up independent async links between just here and Issuers.info. Those webhooks will take some work to standardize across agents, but that's fine.This PR moves the old blog posts by redirecting the canonical URLs within SEC references to
https://github.com/blocktransfer/org-docs. You can see the markdown outline in that repo right now, but we still need to finish setting everything up there, with the dev site, etc., as I rewrite the bylaws and finalize the full org accountability structure.It should all be a lot easier once I start writing the dev processes for transparent working arrangements. I am so excited to have strong externalizable links for new team members. This will go alongside the finalization of what will start the proper DUNA docs within the WhyDRS main discussion repo.