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.
Posted2 weeks 4 days ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Weekly Meetings
Recent comments
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
If there's some time left in the dev meeting - although it might rather be a topic for the PMC:
We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
You can edit this View (/admin/structure/views) to suit your needs. The MORE link is used to display additional results, which can sometimes be useful.
Hello,
I have a question about the block “Recent blog posts”.
I've set it up so that the five most recent blog posts are always displayed on the page (mybackdrop.de/blog) at the TOP...
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