Oops, forgot:
We should probably talk about the landing page:
https://docs.evergreen-ils.org/ <https://docs.evergreen-ils.org/>
probably needs to mention 3.7?
And I wonder if we should edit the line to say "Evergreen 3.6+" and just
link to the latest documentation. Then let the user select the Evergreen
version from the dropdown menu in the antora site?
And I think we should address the "main page" "Topic Manuals":
https://docs.evergreen-ils.org/eg/docs/3.6/
<https://docs.evergreen-ils.org/eg/docs/3.6/>
The site is configured to make that the "home" page (known as start
page). Topic manuals are something we used to have with the old
documentation. It was something that Remington started to flesh out, but
as you can see from that page, it's not.
1. We should change the home page to:
https://docs.evergreen-ils.org/eg/docs/3.6/shared/about_this_documentation.html
<https://docs.evergreen-ils.org/eg/docs/3.6/shared/about_this_documentation.html>
or
2. We should try to make topic manuals?
-Blake-
Conducting Magic
Can consume data in any format
MOBIUS
On 4/16/2021 12:07 PM, Blake Henderson wrote:
All,
I just wanted to let everyone know that I updated the site with a
couple of things:
1. I merged our footer onto the site template so that each page
displays the email link for the DIG mailing list.
2. I updated the search index (the search box in the top right) - so
that the search results only show results from "latest" - to prevent
the multiple search results for each version of Evergreen. The commit
is here:
https://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9eae8a68f3012f2016dfe9c5ab3fc23e818307b3
<https://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9eae8a68f3012f2016dfe9c5ab3fc23e818307b3>
3. I synced the Antora community UI templates over to our customized
ones, thereby including all the new features since June 2020. A list
of updates from their repository is detailed here:
https://gitlab.com/antora/antora-ui-default/-/commits/master/
<https://gitlab.com/antora/antora-ui-default/-/commits/master/>
Our resulting document site looks basically the same. The most notable
difference is the existence of 3.7! The Antora UI skin received
several internal updates. Most of them were variable naming
conversions (no end change to the UI). And cleanups to the CSS. It's a
good idea to keep in sync with that repository as much as we can
because when the new version of Antora comes out, the UI pieces will
likely receive updates as well. And having our repository closer to
master makes it easier to reconcile the changes.
I am thinking about writing some documentation about the documentation
:) - A technical write-up of how to merge the antora community UI
repository over to our eg-antora repository. Should that have a home
in our Evergreen docs? Or doku wiki? I favor the Evergreen docs
because it's easier to find and is likely to be maintained by us.
_______________________________________________
Evergreen-documentation mailing list
Evergreen-documentation@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-documentation
