updatge readme and docs #1263
Merged
updatge readme and docs #1263
+92
−22
Conversation
This file contains 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
W95Psp
approved these changes
Jan 21, 2025
Yes, I think moving and linking is the right thing to do. To have only the most interesting things in the readme. Let's file follow ups. |
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.
@W95Psp there's more for developer documentation in the readme that's not on the docs yet. How about moving all of that to the dev docs?
There's a little duplication now in the readme and the website. We could solve that by reducing the amount of information in the readme (it's a bit much) and move some of it purely to the website.
@karthikbhargavan when the vstte paper is up, this should be added to the list of publications too.