Skip to content

Conversation

@martinyde
Copy link

https://jira.itkdev.dk/browse/LOOP-738
Add info block paragraph

@martinyde martinyde requested a review from rimi-itk May 18, 2021 10:09
Copy link

@rimi-itk rimi-itk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works and looks good, but I have some suggestions on how

  1. I think we should have a header on an info block
  2. I think we should use buttons (rather than list) to add a new paragraph
  3. I think “Attributes” should be replaced with a dropdown list with semantic categories, e.g. “default” and “highlight”. Contentwise “Bordered” doesn't really mean anything, whereas “highlight” (and “Did you know?” and the like) have a semantic meaning that we can use to style the content, e.g. with a border if the designer chooses to do so.

bundle: os2loop_section_page_info_block
label: 'Information block'
description: ''
required: false

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the text be required? I vote “Yes!”

Copy link
Author

@martinyde martinyde May 18, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just let the user decide if they want to add text?
They may want to just add a section with a h2 . There will often be a h1 right above it.
I vote "no!"

bundle: os2loop_section_page_info_block
label: Title
description: ''
required: false

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the title be required? I vote “Yes!”

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just let the user decide if they want to add a h2 or not above the text?
Not all content needs a header. There will often be a h1 right above it.
I vote "no!"

field_name: os2loop_section_page_attribute
entity_type: paragraph
bundle: os2loop_section_page_info_block
label: Attributes

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should rename the field to os2loop_section_page_attribute – or at least change the label to “Type” (which I think is a better name for what it is).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed label

<div{{ item.attributes }}>{{ item.content }}</div>
{% endfor %}
</div>
{% for item in items %}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've wanted to make this change, but I didn't have the guts to do it – or the overview of the templates.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I too am unsure if it will break something, but i think it needs to be done to have proper html for a default field

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will have to look out for weird label styling

@martinyde martinyde merged commit 9f6c690 into develop May 18, 2021
@martinyde martinyde deleted the feature/info-block branch May 18, 2021 13:07
rimi-itk pushed a commit that referenced this pull request Aug 12, 2022
rimi-itk added a commit that referenced this pull request Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants