Feature Request 👨🏼‍💻

We want to create a new BackgroundFiller atom to be used in our compositions

Use Case ✍🏼

We want to have a single atom where we can put the entire background of a video with an Image or a Lottie and where we can override the style for the animations and the few differences.

ℹ️ Once this is done, update the different templates

Feature Request 👨🏼‍💻

We want to let the user choose the font of the video. To do that we can create a font-picker atom that will allow the user to write the name of a font and then select it from a list.

Use Case ✍🏼

When users want to generate a video but the default font do not work for it.

Possible Solution 💡

An atom named FontPicker that is based on the one from the remotion doc (see : https://www.remotion.dev/docs/font-picker) but that use a datalist instead of a select input. The displayed list will not only show the font named but also the font itself on the style of the option (for example : on the list you have the option Roboto styled with the font Roboto to see how it looks).

Feature Request 👨🏼‍💻

It could be really useful to be able to pass a secondarySpeaker image url to generate talks.

Use Case 🫵🏼

Conference often host talks with 2 speakers (not more, or very few). It could be great to handle a custom animation for that

• Home page should gather examples of generated videos
• Those examples should be configured with a JSON file in order to let us add more examples in the futur
• Meetup page should move to a /meetup url

Feature Request 👨🏼‍💻

In our current components we sometimes have types that are not the right ones or that are indicated as any we want to have clean typescript code !

Feature Request 👨🏼‍💻

We want to test the components on the app

Use Case ✍🏼

At any modification on the code we want to be sure that everything work fine.

Possible Solution 💡

Create the test file and make the test using jest and react-testing-library

Feature Request 👨🏼‍💻

Implement responsive design for the SideBar component 📱

Use Case ✍🏼

As users, we want the SideBar component to adapt and provide a seamless user experience across different devices and screen sizes. By introducing a responsive design for the SideBar, we aim to enhance usability and ensure optimal navigation on both desktop and mobile devices.

Possible Solution 💡

1. Identify the breakpoints or screen sizes for responsive design.
2. Modify the SideBar component's CSS or styling to adapt its layout based on screen width.
3. Test the responsive behavior on various devices and screen resolutions.
4. Optimize touch interactions for mobile devices.

Feature Request 👨🏼‍💻

We want to create a new IconCaption atom to be used in our compositions

Use Case ✍🏼

In many compositions we currently display information for conferences in the form of an icon and a corresponding caption (e.g. Devoxx). We want to have a component that displays an icon and a text.

Possible Solution 💡

We don't know yet if we want to make one atom for the icon version and another for the lottie version. We should see if it is possible to make one for both. If it is not possible, or if the atom becomes too complex, we will make two different atoms

ℹ️ Once this is done, update the different templates

Feature Request 👨🏼‍💻

Refacto the function useInputDateChange that is almost the same as useInputChange but with a twist in the value assignation

Use Case ✍🏼

We don't want duplicated code and we want to use the same function everywhere

Possible Solution 💡

Add a condition on the type of the value passed that change the assignation if it's a Date

Describe the template 🎬

We sometimes have subject with company sponsor. In order to communicate we would need to ask for sponsoring/hosting.

Items to display 📺

• Sponsor name
• Sponsor logo

Describe the template 🎬

Items to display 📺

Sketch & Screenshots 🎨

Describe the bug 🐛

From time to time on the application when we have a player that displays lotties we have the application freezing. The problem comes from the display of our lotties and maybe more precisely from the hook. We need to find out where this is coming from and fix the problem

Expected behavior 🦾

The application should not freeze 🤷🏼‍♂️

Feature Request 👨🏼‍💻

In order to detach the project from the LyonJS graphic identity, we want to modify the design to adapt it to the new colours

Use Case ✍🏼

When a user visits the site it must be differentiated from the LyonJS graphic identity

Possible Solution 💡

Use the new colour variables and a new logo (although it may be modified later)

Feature Request 👨🏼‍💻

Use Case ✍🏼

Possible Solution 💡

Describe the template 🎬

Items to display 📺

Sketch & Screenshots 🎨

Feature Request 👨🏼‍💻

We want to add Dark Mode and Light Mode options to the application's user interface. 🌗

Use Case ✍🏼

As users, we want the ability to customize the application's appearance based on our preferences and environment lighting. By introducing Dark Mode and Light Mode options, we aim to enhance the user experience and provide a visually comfortable interface for both day and night usage.

Possible Solution 💡

To implement the Dark Mode and Light Mode functionality, we can follow these steps:

1. Identify the core components of the user interface that need to be modified for Dark Mode and Light Mode, such as backgrounds, text colors, and button styles.
2. Create all default variables for theme colors.
3. Based on the selected mode, dynamically apply the appropriate CSS styles to the relevant components.
4. Consider providing a default mode based on the system settings or user preferences if no explicit selection is made.

Feature Request 👨🏼‍💻

The public folder is a bit messy, there is a lot of images at the root of the folder that are used for different purposes.
The conferences folder is also messy, there is pictures at the root that could be put in folders.

Use Case ✍🏼

When you want to add a default picture you just drop it at the roots of the public folder

Possible Solution 💡

• Create an app folder and a default folder inside public/images/ and moves the corresponding images inside.
• Create folders for conferences under public/images/conferences.

Describe the template 🎬

Items to display 📺

Sketch & Screenshots 🎨

Feature Request 👨🏼‍💻

In the app as in the remotion preview, we need to have a default font. Today, its set every time we need a font.

Use Case ✍🏼

It will allow us to use the same default font everywhere, especially in the remotion preview, when you just want to see an atom, it's better with a good font.

Possible Solution 💡

Create a fontContext with by default the font 'noto-sans' and use it for the remotion preview and the app

Feature Request 👨🏼‍💻

We want to create a new Details molecule to be used in our compositions

Use Case ✍🏼

In many compositions a Details component is used which has been duplicated each time for some differences. We want to have a single component where we can override the style for the animations and the few differences.

Possible Solution 💡

Using the atom created with #215 we can juste make a component we can just make a component that displays three IconCaption for the date, time and location. These parameters will of course be optional

ℹ️ Once this is done, update the different templates

Github can host video in comment and issue.
The purpose of this issue is to store those videos for documentation.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): lock file maintenance

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update remotion to v4.0.159 (@remotion/bundler, @remotion/cli, @remotion/eslint-plugin, @remotion/google-fonts, @remotion/lottie, @remotion/noise, @remotion/player, @remotion/renderer, @remotion/shapes, @remotion/zod-types, remotion)
• chore(deps): update dependency @types/testing-library__jest-dom to v6
• chore(deps): update dependency eslint to v9
• chore(deps): update pnpm to v9
• chore(deps): update pnpm/action-setup action to v4
• chore(deps): update testing-library monorepo (major) (@testing-library/dom, @testing-library/react)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Describe the template 🎬

Items to display 📺

Sketch & Screenshots 🎨

Feature Request 👨🏼‍💻

Add query params to the pages that contains a form to pre-fill it's field

Use Case ✍🏼

Save the page as a bookmark with custom params saved and pre-fill.

Possible Solution 💡

Add query to the pages under app/template/ on meetup, talk, sponsor andevent components.

Feature Request 👨🏼‍💻

Use Case ✍🏼

Possible Solution 💡

Describe the template 🎬

Following the discussion #301, we want to create a new showcase for this event

Items to display 📺

We want to create 3 videos, on for the event, one for the talks and one for the sponsors

Sketch & Screenshots 🎨

Describe the template 🎬

Items to display 📺

Sketch & Screenshots 🎨

Feature Request 👨🏼‍💻

Use Case ✍🏼

Possible Solution 💡

Feature Request 👨🏼‍💻

Use Case ✍🏼

Possible Solution 💡

Describe the template 🎬

We could generate a new composition for generating video to remind our community to submit talks to our Call For Paper

Items to display 📺

I don't think we need any dynamic items here, maybe a QR code to the CFP link

Feature Request 👨🏼‍💻

We want to test the components on the app

Use Case ✍🏼

At any modification on the code we want to be sure that everything work fine.

Possible Solution 💡

Create the test file and make the test using jest and react-testing-library

Feature Request 👨🏼‍💻

We want to create a SideBar component to facilitate navigation within the Template and Showcase pages 📁👀

Use Case ✍🏼

As users, we need a convenient way to navigate within the Template and Showcase sections of the application. By introducing a SideBar component, we aim to enhance the user experience and provide seamless access to different sections and subsections within these pages.

Possible Solution 💡

To implement the SideBar component for navigation within the Template and Showcase pages, we can follow these steps:

1. Identify the different sections and subsections within the Template and Showcase pages that should be included in the SideBar navigation. Maybe try to use a config file with only the template and the basic showcase (for the moment the settings part... is not necessary)
2. Create a SideBar component that displays the navigation options for these sections and subsections.
3. Implement functionality to handle the navigation within the Template and Showcase pages based on the user's selection in the SideBar.
4. Ensure that the active section or subsection in the SideBar is visually highlighted to provide feedback to the user about their current location within the page.
5. Consider adding additional features to the SideBar, such as collapsible sections or expandable menus, to improve usability and make it easier for users to navigate through the content.
6. Test the SideBar component thoroughly to ensure it functions correctly and seamlessly integrates with the Template and Showcase pages 🧪

Describe the template 🎬

Items to display 📺

Sketch & Screenshots 🎨

Feature Request 👨🏼‍💻

We want to create a new Title atom to be used in our compositions

Use Case ✍🏼

In many compositions a Title component is used which has been duplicated each time for some differences. We want to have a single Title atom where we can override the style for the animations and the few differences.

Possible Solution 💡

Create a new Title component, give it a default style, a default font, make sure to take into account all title lengths (ellipsis)... The style should be overloadable for the animation part

ℹ️ Once this is done, update the different templates

Feature Request 👨🏼‍💻

We want to update the design of the application's footer

Possible Solution 💡

You can take the example of what has been done on the wireframe for the new design

Feature Request 👨🏼‍💻

We want to test the components on the app

Use Case ✍🏼

At any modification on the code we want to be sure that everything work fine.

Possible Solution 💡

Create the test file and make the test using jest and react-testing-library

Feature Request 👨🏼‍💻

We want to test the components on the app

Use Case ✍🏼

At any modification on the code we want to be sure that everything work fine.

Possible Solution 💡

Create the test file and make the test using jest and react-testing-library

Feature Request 👨🏼‍💻

We want to test the components on the app

Use Case ✍🏼

At any modification on the code we want to be sure that everything work fine.

Possible Solution 💡

Create the test file and make the test using jest and react-testing-library

Feature Request 👨🏼‍💻

Use Case ✍🏼

Possible Solution 💡

Feature Request 👨🏼‍💻

In the context of adding our atoms and molecules, we want to add tests to avoid breaking these components later on

Migrate the current CSS usage to Tailwind.

Feature Request 👨🏼‍💻

We want to test the components on the app

Use Case ✍🏼

At any modification on the code we want to be sure that everything work fine.

Possible Solution 💡

Create the test file and make the test using jest and react-testing-library

Feature Request 👨🏼‍💻

We want to create a new Avatar molecule to be used in our compositions

Use Case ✍🏼

In many compositions a Speakers component is used which has been duplicated each time for some differences. We want to have a single Avatar molecule where we can override the style for the animations and the few differences.

Possible Solution 💡

Create a new Avatar component with a default style. This component should display an avatar atom containing an image and also a caption atom if the corresponding props are passed to the component

ℹ️ Once this is done, update the different templates

Feature Request 👨🏼‍💻

We want eslint to return a warn or an error if a file contains unused imports

Use Case ✍🏼

when you do a refacto and you forget to remove the imports

Possible Solution 💡

add the rule to the .eslintrc file

Describe the template 🎬

It's a template for an event that will be reusable.

Items to display 📺

It display a speaker with information about it, a big logo, a title, a date range and a time range

Sketch & Screenshots 🎨

Logo :

Feature Request 👨🏼‍💻

We want to update the design of the application's navbar with responsive 😅

Use Case ✍🏼

In order to redesign the application we want to reorganise the different pages of the application. The first step will be to separate the templates from the showcases. To do this we want to add a navbar that will allow us to have Template, Showcase, Docs and Contact.

⚠️ The purpose of this US is not to remove the current navigation but to separate it into two

Possible Solution 💡

You can take the example of what has been done on the wireframe for the new design

Feature Request 👨🏼‍💻

Implement React Testing Library for project testing 🧪

Use Case ✍🏼

As developers, we want to ensure the stability and reliability of our project by implementing a robust testing framework. By introducing React Testing Library, we aim to facilitate the testing process and improve the overall quality of our codebase.

Possible Solution 💡

1. Install React Testing Library as a project dependency.
2. Create separate folders for the tests.
3. Integrate testing into the project's development workflow.
4. List all current components that need to be tested (make US 🏷️)