Person menu changes

[Bradley Miller]

I’m at the point with revisions to runestone servers where I need to change several of the URL’s in the person  menu.  I think Andrew and I have talked about this at some point, but rather than having to coordinate PRs to modify pretext-runestone.xsl maybe its better for us to just build that menu in our Javascript?

I think that the template could then be reduced to <div class=“dropdown-content”></div> inside the #button.

Thoughts?

Brad

Brad Miller
Professor Emeritus, Luther College
Founder, Runestone Academy LTD
Blog: http://reputablejournal.com

Set up a time to meet with me.

[Andrew Scholer]

Yes, that is the line I was thinking along.

The Person menu would be a permanent thing to provide access to the much discussed reader options (light/dark mode switch could then move there). There would be a placeholder that RS can rip out and replace with whatever menu items it wants.

For accessibility purposes all of the menu options should be one list.

A native <ul> would be the most straightforward and semantic approach (as opposed to random elements with aria roles to identify them as list items). The only things valid in an <ul> are <li>, <script>, and <template>. So the placeholder that would go there for RS to replace should probably be a <template> within the <ul>. Which is exactly the kind of use <template>s are designed for.

I was probably going to tackle it next week if you can wait. If not, we could do a quicker PR that just sets up the basic replacement holder within the existing structure.

Andrew

--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/2E21A7A0-E3F2-46ED-B4D7-4906AF8E8D56%40runestone.academy.

[Bradley Miller]

That seems fine to me, and maybe we can plan on working on that plus harmonizing the different nav bars.

I’d like to make updating the user menu a priority though so we can get people using the new auth pages as soon as possible.

Brad

Brad Miller
Professor Emeritus, Luther College
Founder, Runestone Academy LTD
Blog: http://reputablejournal.com

Set up a time to meet with me.

To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/CACm44N9K%3DzhvS1y9BsRBxt%2BaoSwWQFhLt8hkJfOkjev59%2Brm0w%40mail.gmail.com.

[Rob Beezer]

I damn near had Claude just make a readability/customization/personalization
menu and hide it behind a debug switch, even though I have never written a
useful bit of production JS in my life. ;-) That how much I would like to move
the whole readability stuff forward.

So work on the "person" menu sounds great.

I just want to confirm that it will be "shared". Runestone JS will be able to
populate some parts (hosted, and non-hosted), and PreTeXt proper will be able to
populate other parts via PreTeXt JS. Is that where we are going?

Rob

On 6/11/26 05:44, Bradley Miller wrote:
> That seems fine to me, and maybe we can plan on working on that plus harmonizing
> the different nav bars.
>
> I’d like to make updating the user menu a priority though so we can get people
> using the new auth pages as soon as possible.
>
> Brad
>
> Brad Miller
> Professor Emeritus, Luther College
> Founder, Runestone Academy LTD
> Blog: http://reputablejournal.com
>

> Set up a time to meet <https://fantastical.app/bonelake-Gj2i/meet-with-
> brad> with me.

>> Blog: http://reputablejournal.com <http://reputablejournal.com/>
>>
>> Set up a time to meet <https://fantastical.app/bonelake-Gj2i/meet-with-
>> brad> with me.

>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "PreTeXt development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to pretext-dev...@googlegroups.com <mailto:pretext-
>> dev+uns...@googlegroups.com>.

>> To view this discussion visit https://groups.google.com/d/msgid/pretext-

>> dev/2E21A7A0-E3F2-46ED-B4D7-4906AF8E8D56%40runestone.academy <https://
>> groups.google.com/d/msgid/pretext-dev/2E21A7A0-E3F2-46ED-
>> B4D7-4906AF8E8D56%40runestone.academy?utm_medium=email&utm_source=footer>.

>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "PreTeXt development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to pretext-dev...@googlegroups.com <mailto:pretext-
>> dev+uns...@googlegroups.com>.

>> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/

>> CACm44N9K%3DzhvS1y9BsRBxt%2BaoSwWQFhLt8hkJfOkjev59%2Brm0w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/pretext-dev/
>> CACm44N9K%3DzhvS1y9BsRBxt%2BaoSwWQFhLt8hkJfOkjev59%2Brm0w%40mail.gmail.com?
>> utm_medium=email&utm_source=footer>.

>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email

> to pretext-dev...@googlegroups.com <mailto:pretext-
> dev+uns...@googlegroups.com>.

> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/

> E6A9E138-8D93-4B4D-A28D-601A342D66FD%40runestone.academy <https://
> groups.google.com/d/msgid/pretext-dev/E6A9E138-8D93-4B4D-
> A28D-601A342D66FD%40runestone.academy?utm_medium=email&utm_source=footer>.

[Bradley Miller]

Rob, Andrew,

Having two functions try to build the menu seems a bit fraught with potential race conditions.  But maybe we can structure the menu at a high level so each is responsible for a distinct part of what is defined in the template.

Brad

Brad Miller
Professor Emeritus, Luther College
Founder, Runestone Academy LTD
Blog: http://reputablejournal.com

Set up a time to meet with me.

To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAwOC5iZWV6ZXI.1781194026%40pnsh.

[Rob Beezer]

On 6/11/26 09:12, Bradley Miller wrote:
> Having two functions try to build the menu seems a bit fraught with potential
> race conditions.

I thought so. ;-)

> But maybe we can structure the menu at a high level so each is
> responsible for a distinct part of what is defined in the template.

Why not two menus? I know real estate is expensive, but if the "Embed" button
or the "Dark Mode" button goes away...

And we don't even show the Runestone menu when not hosted?

[Oscar Levin]

On fn, so more later....

Readability and accessibility menu are top on my list for when I get back.  Want to get modular js set up though before getting to far.

Anyway, I think we want at the very least flexibility with what things go in which menus.  In particular, the accessibility menu (which might contain a lot of readibility settings) should be a first class citizen and not hidden as part of a user menu.

--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAwOS5iZWV6ZXI.1781194756%40pnsh.

[Andrew Scholer]

Also on phone...

Short term plan of action: 

Add data attribute "deprecated" to existing menu items and a template element with format for menu item as mini pr.

Then we can add JS to RS to rip out existing items and append preferred items.

Once that is in place we can remove old menu items from PTX HTML with no worries about tightly timing releases.

Then we get to work on adding other reader options/features and enable menu for non RS HTML.

Race condition will not be an issue if PTX items are built in. Or if there are clearly defined areas for each set of items instead of everyone just appending to end.

I think I disagree that accessibility should be new to level construct. Feels like person menu should have all personal preference/management stuff. "Reading Options" menu item to open a dialog for them. But we can experiment with ideas for those features once RS quick fix is done.

To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/CAOU9BaU7_E0mZDVs%2B8gJsZ93s_1dv7SZ5FCmxT1M0Hmges1FdQ%40mail.gmail.com.

[Bradley Miller]

OK,

The sample-book on Runestone now has a person menu that is generated by JS when the page is loaded.

The rest of the PreTeXt books should follow this weekend.

Brad

Brad Miller
Professor Emeritus, Luther College
Founder, Runestone Academy LTD
Blog: http://reputablejournal.com

Set up a time to meet with me.

To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/CACm44N8cv%2B0pqgYQWG2Hs%2B129F2RYkcU5KuUX8yRrZPu5uBekQ%40mail.gmail.com.

[Rob Beezer]

Very good! Keep me posted if you need anything on the PreTeXt side. (You know my schedule the next few days.)

Rob

On June 19, 2026 8:37:29 AM EDT, Bradley Miller <br...@runestone.academy> wrote:
>OK,
>
>The sample-book on Runestone now has a person menu that is generated by JS when the page is loaded.
>
>The rest of the PreTeXt books should follow this weekend.
>
>Brad
>
>Brad Miller
>Professor Emeritus, Luther College
>Founder, Runestone Academy LTD
>Blog: http://reputablejournal.com
>

>Set up a time to meet <https://fantastical.app/bonelake-Gj2i/meet-with-brad> with me.

>
>
>> On Jun 11, 2026, at 1:25 PM, Andrew Scholer <asch...@chemeketa.edu> wrote:
>>
>> Also on phone...
>>
>> Short term plan of action:
>> Add data attribute "deprecated" to existing menu items and a template element with format for menu item as mini pr.
>>
>> Then we can add JS to RS to rip out existing items and append preferred items.
>>
>> Once that is in place we can remove old menu items from PTX HTML with no worries about tightly timing releases.
>>
>> Then we get to work on adding other reader options/features and enable menu for non RS HTML.
>>
>> Race condition will not be an issue if PTX items are built in. Or if there are clearly defined areas for each set of items instead of everyone just appending to end.
>>
>> I think I disagree that accessibility should be new to level construct. Feels like person menu should have all personal preference/management stuff. "Reading Options" menu item to open a dialog for them. But we can experiment with ideas for those features once RS quick fix is done.
>>

>> On Thu, Jun 11, 2026, 9:56 AM Oscar Levin <oscar...@gmail.com <mailto:oscar...@gmail.com>> wrote:
>>> On fn, so more later....
>>>
>>> Readability and accessibility menu are top on my list for when I get back. Want to get modular js set up though before getting to far.
>>>
>>> Anyway, I think we want at the very least flexibility with what things go in which menus. In particular, the accessibility menu (which might contain a lot of readibility settings) should be a first class citizen and not hidden as part of a user menu.
>>>
>>> On Thu, Jun 11, 2026, 10:19 AM 'Rob Beezer' via PreTeXt development <prete...@googlegroups.com <mailto:prete...@googlegroups.com>> wrote:
>>>> On 6/11/26 09:12, Bradley Miller wrote:
>>>> > Having two functions try to build the menu seems a bit fraught with potential
>>>> > race conditions.
>>>>
>>>> I thought so. ;-)
>>>>
>>>> > But maybe we can structure the menu at a high level so each is
>>>> > responsible for a distinct part of what is defined in the template.
>>>> Why not two menus? I know real estate is expensive, but if the "Embed" button
>>>> or the "Dark Mode" button goes away...
>>>>
>>>> And we don't even show the Runestone menu when not hosted?
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.

>>>> To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com <mailto:pretext-dev%2Bunsu...@googlegroups.com>.

>>>> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAwOS5iZWV6ZXI.1781194756%40pnsh.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.

>>> To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com <mailto:pretext-dev...@googlegroups.com>.
>>> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/CAOU9BaU7_E0mZDVs%2B8gJsZ93s_1dv7SZ5FCmxT1M0Hmges1FdQ%40mail.gmail.com <https://groups.google.com/d/msgid/pretext-dev/CAOU9BaU7_E0mZDVs%2B8gJsZ93s_1dv7SZ5FCmxT1M0Hmges1FdQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups "PreTeXt development" group.

>> To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com <mailto:pretext-dev...@googlegroups.com>.
>> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/CACm44N8cv%2B0pqgYQWG2Hs%2B129F2RYkcU5KuUX8yRrZPu5uBekQ%40mail.gmail.com <https://groups.google.com/d/msgid/pretext-dev/CACm44N8cv%2B0pqgYQWG2Hs%2B129F2RYkcU5KuUX8yRrZPu5uBekQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>

[Rob Beezer]

And just to verify, I am seeing the sample book menu that looks different than another book, so all seems well from public-facing access.

Thanks,
Rib