Hi Flavelle

To amend try adding the following to the Custom CSS field of your templates parameters (Extensions -> Templates -> [YourTemplateStyle] -> Custom CSS)....

h2, .content-category h1, .registration h1 {

    text-transform: none;

}

Ciaran

That fixed some of them, but in the Recent Articles, which uses the Joomla51 News module, the titles are still fully upper case (screenshot attached).

Hello

To amend could you also try adding the followig to your Custom CSS field...

.item-title, .page-header, h3 {

    text-transform: none !important;

}

Ciaran

First of all, thanks - that code worked. My Custom CSS is getting larger



In this screenshot, you can see that the second row of articles starts in the middle. How do I get that second row to start on the left?

And finally (I hope), is there a way to change the format of the date for the articles (and everything else) to be Aug-02-2020? In other words an Mmm-dd-yyyy format.

Please keep up the good work. Your templates are making this so much easier to work with Joomla.

Hi Flavelle

1. Would you have a URL to an example of your screenshot?

2. You will need to create an override for your blog. If you are not familiar with Joomla overrides, may I suggest sending temporary administration access to your Joomla installation to info@joomla51.com and we will create the override for you. For our reference please paste a link to this post in your email.

Ciaran

I'm making good progress. I am using h3 for titles within my articles - wonderful. How do I make .h4 to be small caps as well? I have discovered that if I use .h3 and .h4 formats within the individual articles, that seems to work well within my site.

This is my current Custom CSS:
h2, .content-category .content-heading h1, .registration h1 {
text-transform: none;
font-variant: small-caps;
}
.item-title, .page-header, h3 {
text-transform: none !important;
font-variant: small-caps;
}

Hi Flavelle

To amend try adding the following to the Custom CSS field of your templates parameters (Extensions -> Templates -> [YourTemplateStyle] -> Custom CSS)....

h4 {

    text-transform: initial;

    font-variant: small-caps;

}

Ciaran

Thanks so much. The only change that I made to your suggestion was to change the text-transform to none, which is consistent with my other headers. I do hope that you are keeping safe and well.

Thanks to your help, my website is nearly perfect - the link is attached. I have two remaining questions:

1. The menu items are still showing in all caps and I have not been able to figure out how to make them small-caps. I would really appreciate your help. Other than that, the website is looking nearly perfect.
   
2. I have to maintain three copies of the template - one for default, the second for English (Canada) and the third for French. I think that there might be a more efficient way. You provide a note that, "Note: If you find you have a large amount of Custom CSS in the field above, you can copy it's contents to your templates custom.css (../templates/[YourTemplate]/css/custom.css) with the same effect. Ensure to first enable the custom.css option below." I am assuming that if there are updates, the custom.css file will not be replaced.
   

My current custom CSS looks as follows:

h1, h2, h3, h4, h5, h6, h3.mod_standard, h3.page-header {
text-transform: none;
font-variant: small-caps;
}
table {
width: 100%;
border-color: #536982;
border-style: solid;
margin-bottom: 1em;
}
th {
padding: 1em;
test-transform: none;
border-color: #536982;
border-style: solid;
font-variant: small-caps;
color: #536982;
vertical-align: bottom;
text-align: left;
}
td {
padding: 1em;
vertical-align: top;
border-color: #536982;
border-style: solid;
text-align: left;
}

Hi Flavelle

All good on this end. I hope you are also keeping safe.

1. To amend try adding the following to the end of your Custom CSS field...

.hornav > ul > li > a {

    text-transform: inherit;

}

2. The same custom.css file will be loaded by all template styles (if enabled) so it is a good place for CSS that is shared throughout your site. This file is not replaced if your template is updated. Regardless always good practice to make a backup when updating.

Ciaran