[Evergreen-documentation] Help with table formatting

[Blake Henderson]

Andrea,

I'd like to take a crack at it. If anyone else would like to do the 
same, feel free. I estimate 2-5 hours of work. It involves pulling the 
latest version of the UI and merging our changes onto it. There will be 
much fiddling as I would expect our changes to no merge cleanly given 
all of the new features and whatnot. This development work can be done 
separately from the production docs machine. It should be done on a 
personal development machine.

My timeline is realistically 1-2 months away as we are dealing with some 
time-sensitive and time-intensive projects/migrations right now.

-Blake-
Conducting Magic
Can consume data in any format
MOBIUS

On 9/15/2022 10:29 AM, Andrea Buntz Neiman wrote:
> Thanks, both, for your input.
>
> I'd be in favor of an upgrade to new Antora in general - and I know 
> this has been discussed at prior DIG meetings - what would that look 
> like in an implementation sense?
>
> On Thu, Sep 15, 2022 at 11:17 AM Blake Henderson via 
> Evergreen-documentation 
> <evergreen-documentation at list.evergreen-ils.org> wrote:
>
>     All,
>
>     Our presentation layer is derived from the antora UI:
>
>     https://gitlab.com/antora/antora-ui-default
>
>     Our implementation of it:
>
>     https://git.evergreen-ils.org/?p=working/eg-antora.git;a=summary
>
>     We're behind them by quite a bit. But we're also using an older
>     version of Antora (2.3) and the community has released 3.1. So,
>     there is some work to be done to rebase our Evergreen look and
>     feel over the default. And upgrade to 3.1.
>
>     Barring doing that, we could* change the CSS to widen out the page
>     to accommodate for wider content. However, I'm not certain how
>     much of that could break mobile but we can give it a whirl!
>     Though, upgrading to the latest version of everything might be
>     time better spent?
>
>
>     -Blake-
>     Conducting Magic
>     Can consume data in any format
>     MOBIUS
>
>     On 9/15/2022 9:52 AM, Terran McCanna via Evergreen-documentation
>     wrote:
>>     I haven't worked with asciidoc, but I think the problem could be
>>     fixed in the CSS for the whole site at once. Currently in
>>     https://docs.evergreen-ils.org/eg/_/css/site.css the .toc-menu
>>     has "position:sticky" which I believe is what is causing the
>>     contents box to stay in that spot floating over everything else.
>>     IMO, the contents box doesn't need to be sticky, having it stay
>>     at the top of the page would be fine.
>>
>>     	
>>
>>     Terran McCanna, PINES Program Manager
>>
>>     ------------------------------------------------------------------------
>>
>>     Georgia Public Library Service | University System of Georgia
>>
>>     2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341
>>
>>     (404) 235-7138| tmccanna at georgialibraries.org
>>
>>     http://help.georgialibraries.org | help at georgialibraries.org
>>
>>
>>     <https://www.facebook.com/georgialibraries><https://www.twitter.com/georgialibs><https://www.instagram.com/georgialibraries/><https://www.twitter.com/georgialibs>
>>
>>     Join our email list <http://georgialibraries.org>for stories of
>>     Georgia libraries making an impact in our communities.
>>
>>
>>
>>
>>     On Thu, Sep 15, 2022 at 9:46 AM Andrea Buntz Neiman via
>>     Evergreen-documentation
>>     <evergreen-documentation at list.evergreen-ils.org> wrote:
>>
>>         Hi DIGgers,
>>
>>         My colleague Erica Rohlfs wrote some great documentation on
>>         Global Flags (yay!), which I converted to asciidoc & added to
>>         the docs here:
>>
>>         https://docs.evergreen-ils.org/eg/docs/latest/admin/global_flags.html
>>
>>         The trouble is that the table is too wide, and in Chrome (but
>>         not Firefox) the right-hand Table of Contents navigation acts
>>         like a modal - allllll the way down the page, apparently -
>>         thus effectively blocking the hyperlinks in the rightmost
>>         "Other Information" column.
>>
>>         I've poked at asciidoctor docs (and Galen noted that there's
>>         a known bug related to stylesheets
>>         <https://github.com/asciidoctor/asciidoctor/issues/3833>
>>         about this) but I'm wondering if anyone with more experience
>>         with tables can recommend the best / easiest approach here
>>         before I start fiddling with display widths & static column
>>         widths, etc.
>>
>>         Thanks,
>>         Andrea
>>
>>         -- 
>>         Andrea Buntz Neiman
>>         Project Manager for Software Development
>>         Equinox Open Library Initiative
>>         abneiman at equinoxOLI.org <mailto:abneiman at equinoxoli.org>
>>         1-877-OPEN-ILS (673-6457) x5583
>>         _https://www.equinoxOLI.org/ <https://www.equinoxOLI.org/>_
>>         _______________________________________________
>>         Evergreen-documentation mailing list
>>         Evergreen-documentation at list.evergreen-ils.org
>>         http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-documentation
>>
>>
>>     _______________________________________________
>>     Evergreen-documentation mailing list
>>     Evergreen-documentation at list.evergreen-ils.org
>>     http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-documentation
>
>     _______________________________________________
>     Evergreen-documentation mailing list
>     Evergreen-documentation at list.evergreen-ils.org
>     http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-documentation
>
>
>
> -- 
> Andrea Buntz Neiman
> Project Manager for Software Development
> Equinox Open Library Initiative
> abneiman at equinoxOLI.org <mailto:abneiman at equinoxoli.org>
> 1-877-OPEN-ILS (673-6457) x5583
> _https://www.equinoxOLI.org/ <https://www.equinoxOLI.org/>_
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-documentation/attachments/20220916/79567135/attachment-0001.htm>