Conference Module Design / General

[furilo]

Part of #3709

Ok, here we go with the first shots... Some introductory comments:

• I'm proposing a one-pager. All info about the conference would be in the same page. It may seem it's too much information, but I think given the user needs of browsing the info about a conference, it makes sense to have it all in the same page (if we don't like the idea of a one-pager, it would be easy to breake each section into its own page).
• We'd have a fixed sidebar, that would let you easily jump from one section to another (and since it's on the same page, it would be fast)
• In the header we point out the conference title, dates, city and main CTAs: register and programme.
• The first two blocks (intro + details) would support inline images, videos, etc.
• For entities, I'm proposing two different sizes for the logos (see both screens)
• For speakers:
  • also two options regarding size
  • when you hover one of them, you would get the extended info (bio, links, sessions...). In the future, we may have permalinks for speakers (don't know if that's the idea already)
• Programme: you can see how you'd browse between days, and if a session (really, a slot) is multitrack, to browse between tracks. Content and streaming sections might/should not appear until they have content.
• Permalinks for sessions: I'll design this although it's not for the MVP (as some other things in these designs!)
• Registration: I've asked a question here about it.

cc @decidim/product @decidim/lot-core @decidim/lot-mods

One-pager or not, we can open individual issues to discuss about details for each section.

[isaacmg410]

Great job @furilo!!
I really like the design you propose, but I would like to make some comments on this design. 😄

I'm proposing a one-pager. All info about the conference would be in the same page. It may seem it's too much information, but I think given the user needs of browsing the info about a conference, it makes sense to have it all in the same page (if we don't like the idea of a one-pager, it would be easy to breake each section into its own page).
We'd have a fixed sidebar, that would let you easily jump from one section to another (and since it's on the same page, it would be fast)

I think there is a lot of information for the user to have everything on the same page. Although we have the sidebar to navigate. I would separate it in these three sections:

• Main information of the conference, (Introduction, details, promoters and locations)
• Speakers
• Program

The registration part, could it be a modal? As it is now done at meetings. What do you think?
(Just keep in mind, that in the future the registration will be by type of entry.)

Header

In the header we point out the conference title, dates, city and main CTAs: register and programme.
The first two blocks (intro + details) would support inline images, videos, etc.

Just a couple of things about the header.
Do you want to make the design different from the other participatory spaces that are already made?
Have you considered that other types of components can be enabled? (like Proposals, Debates, Blog, etc.) I think we need a second menu for these components.
What do you think?

Another thing about the header, we don't have any field in admin to write the "Main Location". Should this field be created? @decidim/product

Sponsors

For entities, I'm proposing two different sizes for the logos (see both screens)

Just as an idea, Can we make the sponsors have a different logo size according to the category? That is, if you are a promoter group, the logo will be larger than if you are a collaborator.

What do you think?

Speakers

For speakers:
also two options regarding size
when you hover one of them, you would get the extended info (bio, links, sessions...). In the future, we may have permalinks for speakers (don't know if that's the idea already)

I like the idea and the design! 👏 Only, that I would separate it on a different page

Programme

Programme: you can see how you'd browse between days, and if a session (really, a slot) is multitrack, to browse between tracks. Content and streaming sections might/should not appear until they have content.
Permalinks for sessions: I'll design this although it's not for the MVP (as some other things in these designs!)

Do you know that sessions are meetings not?
Currently, meetings do not have any system to include tracks. (I mean to do this "Track#Labs") and it was said that the functionality of Meetings could not be changed ... Could we reuse the system of Categories to do that?
Will there be a show page for the meeting/session?

What do you mean when you say "Permalinks for sessions"?

General Impressions

Why do I include the section to subscribe to the newsletter? I think that this system does not exist on the platform. Since to be able to subscribe to the newsletter you must be a registered user. no?

As I said before! Great Job @furilo 🎉 🎉 👏 👏

[arnaumonty]

Hi @furilo, great job!

Some comments below:

I'm proposing a one-pager. All info about the conference would be in the same page. It may seem it's too much information, but I think given the user needs of browsing the info about a conference, it makes sense to have it all in the same page (if we don't like the idea of a one-pager, it would be easy to break each section into its own page).

I like the idea in terms of design but we should evaluate it in terms of integrity. If conferences is a new participatory space then we should try to take care that the design doesn't break the structure of components. For example, new items of the menu could be new components (example: proposals), and I imagine that proposals can't be easy to show in a full page view with the rest of the elements.

We'd have a fixed sidebar, that would let you easily jump from one section to another (and since it's on the same page, it would be fast)

The design it really likes me, but I'm not sure if it's compatible with other components. Maybe we could have 2 menus, one for the navigation of the components and other to navigate for the elements of the home page. Let's discuss this.

In the header we point out the conference title, dates, city and main CTAs: register and programme.

It is a good Idea, they are the main points to highlight in a conference.

The first two blocks (intro + details) would support inline images, videos, etc.

ok

For entities, I'm proposing two different sizes for the logos (see both screens)

ok. The name should be customizable for each one category and optional to have both, just one or none.

For speakers:

I would prefer to use the card that we have for Members in Assemblies. I think that the component used is the same right @isaacmg410 ?

when you hover one of them, you would get the extended info (bio, links, sessions...).

ok

Programme: you can see how you'd browse between days, and if a session (really, a slot) is multitrack, to browse between tracks.

We should locate Programme before the speakers and not after. As pointed @isaacmg410 We don't have tracks for a moment. Let's leave this for the next iteration, not for MVP.

Other comments to @isaacmg410:

Just a couple of things about the header.
Do you want to make the design different from the other participatory spaces that are already made?

I think that this could help to give relevance to conferences

Have you considered that other types of components can be enabled? (like Proposals, Debates, Blog, etc.) I think we need a second menu for these components.

+1

Another thing about the header, we don't have any field in admin to write the "Main Location". Should this field be created? @decidim/product

Yes, we should add it in the Information page in Admin.

Do you know that sessions are meetings not?

This is very important. The program is a collection of meetings and has to be built form the meetings.

Currently, meetings do not have any system to include tracks. (I mean to do this "Track#Labs") and it was said that the functionality of Meetings could not be changed ... Could we reuse the system of Categories to do that?

Could be a solution yes!

Will there be a show page for the meeting/session?

The same that we have for any meeting. The programme should drive you to the full page meeting.

[isaacmg410]

I would prefer to use the card that we have for Members in Assemblies. I think that the component used is the same right @isaacmg410 ?

@arnaumonty It can be different, since it is another entity having more fields than Members. You can check in my staging. http://isaac.decidim.int.coditdev.net/conferences/est-hic/speakers

[furilo]

Thanks for your comments and compliments! Glad you like it. Replies to your concerns (I think I'm not missing anything!)

One-pager or not

OK, we'll go with individual pages to accommodate components. I would avoid having two navigation menus - but, all menu items for a conference will be a component? Can we mix conference features and components? Maybe, if we have conference specific-items (like Information, Speakers, Programme, Addres - that we know always be present for a conferent) we can show them by default, and then if you activate other components, they will be listed after in the menu. Here is a test:

Speakers - I would prefer to use the card that we have for Members in Assemblies.

Since speakers in a conference are one of the attractives, I thought giving more prominence to the photo would make sense...

Programme

I forgot to say: this design is for the 1st iteration. From the issue specs, I understand that for the MVP we'll just use the current event cards without any modification. Also, I understand that for the 1st iteration we'll have to develop the track feature.

Registration - modal or not

It could be a modal, but first I'll like to understand what we need from registrations/how they'll work. See #3709 (comment)

Sponsors - various sizes

Perfect if when creating sponsor groups, we can define its size (medium, large), since it makes sense to show different sizes.

Newsletter

In #3709 there is a reference to "Selective newsletter". Thinking now, I don't really know what is that, but I imagined it is a newsletter you can subscribe about specific parts of the application. Anyway, showing the subscribe widget or not doesn't break anything.

[arnaumonty]

OK, we'll go with individual pages to accommodate components. I would avoid having two navigation menus - but, all menu items for a conference will be a component? Can we mix conference features and components? Maybe, if we have conference specific-items (like Information, Speakers, Programme, Addres - that we know always be present for a conferent) we can show them by default, and then if you activate other components, they will be listed after in the menu.

It looks a good solution. What do you think @isaacmg410 ?

[isaacmg410]

@arnaumonty Perfect It's just like the MVP of conferences and assemblies is now working.

[mrcasals]

I feel like the design in the first comment is very long, shows too much information. Would it be possible to split each section in different pages? Eg. the conference homepage would show intro + details, then each other section goes in a different page.

Also, how would the speakers section be implemented for mobile? This hover doesn't seem feasible, and most important hides the next speaker, so you need to move the mouse/click around a few times if you want to read the next speaker in the row.

[furilo]

Here is another round of the screens incorporating feedback.

• Various pages instead of the long one. We would have to choose what info we show on the home page of a conference, and see if some elements are shown on every page as the conference footer.
• Sponsors: showing two sizes.
• Sign up for the conference: when you are logged out, and logged in.
• Mobile version: header + speakers.

Conference home

Programme

Speakers

Mobile

[furilo]

@Crashillo you can HTML the screens from the previous comment.

[Crashillo]

PR design in #3931

[isaacmg410]

Design must be reassessed to fit the components correctly. Check: #4135

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. @carolromero & @xabier feel free to chime in.