-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
where to put binary assets #11
Comments
Regarding the tutorials: I have them somewhat converted but only for my own use when searching the documentation, see fork, since I think you wanted to keep them in the Word format. The major missing points for the tutorials are the images with annotations of the original Word files. The annotations are not extracted by pandoc, hence all images must be recreated/ transferred by screenshot. |
I think having the tutorials converted would be pretty convenient; there's probably a way to export the figures as SVG. I wouldn't bother putting the tutorial PDF's/Word Documents in a new asset repo for now anyway, though, since they are already in the ReleaseSupport repo. |
Would it help if I submit the work in my fork? PR workflow is going to fail. Unfortunately, I won't have time to do any work on the tutorials to make them compliant. |
If you could open a draft PR, that would be helpful! That will make it obvious that the task has been started, and easier to coordinate if needed. |
I just uploaded all of the PDFs to the last Soar release and linked there. I'm thinking that that will be the easiest way to go long-term; the Soar release process is not fully automated, but I can at least add a note in the instructions that we should get the built tutorials and manual from here (once those builds are ready). |
We have:
I like keeping this repository light, so I'm inclined to keep them out of here. I'm thinking another repository dedicated to binary assets would be ideal.
The text was updated successfully, but these errors were encountered: