Project page refactoring features

[Billybobbonnet]

This issue is where we will discuss the features of the refactored project page. We can provide several "widgets" depending on the project type.

Following the features of the refactored project form, we will deal with some variations in the available fields at creation level. The idea here is, besides adapting it to the new field variations, to discuss what are the relevant elements to make the project page more appealing and fit more into the project type.

Another challenge is to ensure some consistency between the pages in terms of UI/UX to avoid misleading the user into thinking this is not the same "project" object/page.

As of now we have 2 widgets: the cite et the social share widgets. We have several leads for other ones:

• A calendar widget for events or calls in order to allow to add to calendar automatically the project with one click
• File attachments widget (to discuss considering that it would change WPRN approach, i.e. being a repository for projects)
• Similar projects section, for every project. I already know how to implement this and I believe it will be a much welcomed feature
• Inline content (videos hosted on youtube, online surveys or questionnaires, pdf?)
• A team widget with at most the team members firstname, lastname, institution, title, url, image
• A "projects from the same institution" button? Maybe too early
• A project picture

The refactoring will also include a rework of (to discuss):

• The continent/country fields that could be merged in a single location field accordingly to the behavior discussed here
• The title layout with the status badge, the back arrow, and the social widget FAB to behave better on every viewport
• the general layout behavior when many pills are set in one field (e.g. countries, thematics, disciplines)

If we agree on too many changes, I will split the work in 2 different iterations and we will have to decide what to prioritize for the first.

Also, consider that some of these widgets have an impact on the project creation process.

[sluck-IEA]

Discussed on the phone with Antoine: A two-step process with a very light 1st step risks causing registration of projects with too little info because 2nd step is never completed. But the idea of providing features and widgets to project leaders to personalize their project page and add info, documents, videos, etc. beyond the minimal elements currently proposed is an appealing functionality that could/should be developed later on.