wuletawwonte / rmis Goto Github PK

• Create an admin account to test out the admin tasks of the project.
• Create a couple of sample research centers, thematic areas, researcher accounts for development purpose.

Start using ViewComponent for reusable part of the UI. It is easier to test and fater than partials.

• Create a toggle button to toggle the status of an email address in the subscribers table

• Create a GitHub action to run the test suite
• Remove stylelint because all styling is done using tailwind so it is not important

Change the header section of each page, that contains the title and add button, to a view component.

• Add email sending feature when a user subscribes to a research call on the homepage
• Add email sending feature to subscribers when a new research call is added

Create a CONTRIBUTION file in the root folder of the repository and add contribution guidelines in it. A widely used guideline of any sort would be fine.

Creation of a Research Center shall also create a user account with the role research_center. Having the email address of that research center.

• Create a string key to refer to a research call because the title may be identical.

Here is what the .env file should include

• The number of rails workers
• HTTPS toggle with a 0 and 1 value for each environment(dev or prod)
• Self signed certificate path

• Show active or inactive status of each call on the list page based on the deadline of the call.