Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upURL for new documentation #15
Comments
|
My initial gut feel was "what does Nick think?" That said, I like the idea of keeping http://docs.archivesunleashed.io and having it bring us to a basic Jekyll page of the Archives Unleashed Toolkit documentation. And the status quo works for me otherwise. But what do you think, @ruebot ? |
|
We use archivesunleashed.io for our Java/Scala namespace (and it's what's registered with Maven Central). Ideally, we'd do the third option. But, we don't really have that many projects setup, and since all of our code projects/repos are in some way or another offshoots of Really, I just wanted to put it all out there on the table to make sure we had a conversation about it again, and it's better documented |
|
@SamFritz can we put this one on the agenda for tomorrow? My suggestion is going to be docs.archivesunleashed.org or docs.archivesunleashed.org/aut if I can swing it on github pages. I rather not use the io tld given the baggage that comes with it. |
|
or, aut.docs.archivesunleashed.org. That's actually doable with gh-pages. |
|
https://aut.docs.archivesunleashed.org/ it is thanks to @ruebot! |
What do we want to URL for this documentation we're working on to be? Do we want to keep http://docs.archivesunleashed.io?
Currently:
Or, do:
autdocumentation)Or, do we box ourselves in by assuming only
autdocumentation lives on archivesunleashed.io, so we do:autdocumentation)Also, we do we do with the stub page for
auton archivesunleashed.org? Just leave it as is?What are y'all's thoughts on how we should structure things once we're ready to "publish" these new docs. Might help with planning out/sketching out future of Notebooks, the Cloud, GraphPass, etc.