Salem theme: conclusion of exercisegroup

[Chrissy Safranski]

Mostly for Andrew, I think. 

Paragraph

I don't think I've ever used a <conclusion> to an <exercisegroup> before, but I did here (inside a <worksheet> in case that matters), and I was surprised by the styling of it in the Salem theme.  I expected it to look more like plain text as the <introduction> does.  I checked the other themes without changing my source, and they all render the <conclusion> like text without styling.  

After I got over my surprise, I rather liked the styling - it draws your attention to the meaning behind what they were doing.  Although my students will be doing this on paper and won't see the styling anyway, but I figured I'd report it and see if the styling was intended or not.  

Chrissy

[Andrew Scholer]

Well, there is a specific rule that is triggering the "heading box" around conclusions, so it must have been intentional. However, I honestly don't remember making the decision. I must have thought that a conclusion deserved to be called out as important in the way you describe.

Especially inside something like an example or exploration, I think the conclusion is worthy of "this is special" styling.

I could see a case for leaving <conclusion> unstyled and requiring the use of <outcomes> inside the conclusion to get a box. But that does not appear to be valid in the schema.

Naked <p>s can be used for statements at the end of a worksheet or project-like that aren't a formal conclusion. They would remain unstyled.

My opinion here is not firmly held, but given those factors, I still hold the same opinion that I apparently did when setting up block styling for Salem. 

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/06c3778b-5411-48b7-abc5-c59577c238fbn%40googlegroups.com.

[Chrissy Safranski]

My section summaries, as in  Paragraph, are each authored as a titled <conclusion> inside a <section>.  The styling didn't surprise me there, and I think it looks and functions great.  I'm not sure I think that conclusion of an exercisegroup should always be emphasized in the same way, but if all conclusions are styled the same regardless of parent, then I agree that it's totally worth it. 

In any case, I'm not trying to lobby for a change; as I said, I liked the effect.

Chrissy 

[Rob Beezer]

I think of #introduction and #conclusion as bookends, and would style them
identically. #conclusion does not say #outcome or #warning or #alert to me.

But, of course, part of the beauty of themes is an opportunity to experiment.

I think a harder problem is to visually make a conclusion appear to be part of
the #exercisegroup and not just a trailing, unrelated #p. Something like less
vertical space above than normal, and more vertical space below than normal.

Aside: LaTeX has no real natural way to make a #conclusion to a #division
(partly because it lacks a begin/end mechanism for divisions), so even bigger
decisions get hard, such as how to "continue" numberings.

Rob

On 11/14/25 12:54, Chrissy Safranski wrote:
> My section summaries, as in Paragraph <https://tanaquil18.github.io/
> matrixcalculations/sec-LUdecomposition.html#subsec-LUdecomposition-
> summary-2>, are each authored as a titled <conclusion> inside a <section>.  The

> styling didn't surprise me there, and I think it looks and functions great.  I'm
> not sure I think that conclusion of an exercisegroup should always be emphasized
> in the same way, but if all conclusions are styled the same regardless of
> parent, then I agree that it's totally worth it.
>
> In any case, I'm not trying to lobby for a change; as I said, I liked the effect.
>
> Chrissy
>
> On Friday, November 14, 2025 at 11:35:38 AM UTC-5 asch...@chemeketa.edu wrote:
>
> Well, there is a specific rule that is triggering the "heading box" around
> conclusions, so it must have been intentional. However, I honestly don't
> remember making the decision. I must have thought that a conclusion deserved
> to be called out as important in the way you describe.
>
> Especially inside something like an example or exploration, I think the
> conclusion is worthy of "this is special" styling.
>
> I could see a case for leaving <conclusion> unstyled and requiring the use
> of <outcomes> inside the conclusion to get a box. But that does not appear
> to be valid in the schema.
>
> Naked <p>s can be used for statements at the end of a worksheet or project-
> like that aren't a formal conclusion. They would remain unstyled.
>
> My opinion here is not firmly held, but given those factors, I still hold
> the same opinion that I apparently did when setting up block styling for Salem.
>
> Andrew
>
>
> On Fri, Nov 14, 2025 at 5:53 AM Chrissy Safranski <tanaq...@gmail.com> wrote:
>
> Mostly for Andrew, I think.
>

> Paragraph <https://tanaquil18.github.io/matrixcalculations/sec-
> LUdecomposition.html#ws-LUdecomposition-3-1-5-1>

>
> I don't think I've ever used a <conclusion> to an <exercisegroup>
> before, but I did here (inside a <worksheet> in case that matters), and
> I was surprised by the styling of it in the Salem theme.  I expected it
> to look more like plain text as the <introduction> does.  I checked the
> other themes without changing my source, and they all render the
> <conclusion> like text without styling.
>
> After I got over my surprise, I rather liked the styling - it draws your
> attention to the meaning behind what they were doing.  Although my
> students will be doing this on paper and won't see the styling anyway,
> but I figured I'd report it and see if the styling was intended or not.
>
> Chrissy
>
>
> --
> 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/06c3778b-5411-48b7-abc5-c59577c238fbn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-dev/06c3778b-5411-48b7-abc5-
> c59577c238fbn%40googlegroups.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/8a5a5cd8-e0f8-4d09-bc70-e4c383500e0en%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-dev/8a5a5cd8-e0f8-4d09-bc70-
> e4c383500e0en%40googlegroups.com?utm_medium=email&utm_source=footer>.