I always do a separate summary field for these reasons:
Avoids the UI cludge of having either a summary or a trimmed value of body
Allows summary to be mandatory
Allows a fixed length that adheres to the need for the meta description which combined with a module to show a countdown helps to focus the mind of the editor.
Ensures that a suitable summary is added to help Google (and other services using this data) understand the content of the page.
CSS - font-weight: bold.
If in the future you want to remove the bold for that field on all pages of the site, changing the formatting of all pages is very difficult, unlike changing the CSS style.
Hi Kevin
I am interested assisting you developing a theme by cloning feature from existing WordPress website.
Please let me know your suitable time to discuss further...
Posted1 week 1 day ago by Deep Vyas (deepvyas) on:
I've updated the Zulip link in both places I found it. No need to post again, unless you have something new to say. We'll pull together feedback from all the sources.
Should we post here again, what we posted over there? Or would that unnecessarily duplicate things?
The link to a Zulip thread in this initial post leads to an internal one, but there's...
This is a really good idea. I nearly always search on GitHub if I'm not sure of the name.
That said, there is still room for improvement in GitHub as many repos have a useless description...
Posted1 week 4 days ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Comments
It seems that while the summary field does not have a WYSIWYG editor. It does have the same text format as the main body field.
Cutting and pasting content from the body field does not always work to keep formatting, unless you cut and paste from the source.
I am wondering if there is a module that adds a WYSIWYG editor to the summary field.
Here is a draft module, but I don't want to push this to contrib until I am sure there is no alternative already.
https://github.com/stpaultim/summary_editor
I always do a separate summary field for these reasons:
I agree with @yorkshirepudding for new sites. Existing sites that use this "long text with summary" functionality already... not sure.
There is an old core issue around this, too, it looks like. (And another related to potentially removing "long text with summary".)
CSS - font-weight: bold.
If in the future you want to remove the bold for that field on all pages of the site, changing the formatting of all pages is very difficult, unlike changing the CSS style.
The simple way is
- View source code
- Copy and paste what you need
- Bold can be easily added with <b> or <strong> tags