[OTHER] Improved management of ISR revalidation intervals using a configuration file

[badrivlog]

What would you like to share?

Currently, Linkfree uses Incremental Static Regeneration (ISR) for some pages,
managing the revalidate values for different pages becomes crucial for customization and maintainability. I propose implementing a configuration file specifically for managing ISR revalidation intervals to enhance code organisation and provide more flexibility.

Benefits

• Centralized configuration: A dedicated configuration file consolidates all revalidate values in one place, providing a clear overview of regeneration intervals for different pages.
• Easy customization: The configuration file allows for simple adjustments of the regeneration intervals without modifying the code directly, offering flexibility as requirements evolve.
• Separation of concerns: Separating revalidate values from page-specific logic ensures a clear distinction between regeneration configuration and data fetching/rendering, improving code modularity.
• Scalability and maintainability: As the application expands with additional pages, a configuration file simplifies updates and modifications, contributing to code maintainability.
• Dynamic values: The configuration file approach supports dynamic revalidate values, enabling fetching from external sources, using environment variables, or calculating intervals based on conditions.
• Collaboration and team workflows: With a configuration file, developers can easily collaborate and make changes to regeneration intervals, ensuring consistency across the project.

Changes proposed

• Create a configuration file (e.g., isr.js) to store revalidate values for different pages.
• Import the configuration file into the getStaticProps function for each page and utilize the appropriate revalidate value from the configuration object.
• Update the configuration file as needed to reflect the desired revalidate intervals for each page.

This enhancement will improve the management of ISR revalidation intervals, leading to a more organized codebase, easier customization, and streamlined collaboration among team members.

Additional information

Happy to work on this 👍

Thanks

[github-actions]

To reduce notifications, issues are locked until they are https://github.com/EddieHubCommunity/LinkFree/labels/%F0%9F%8F%81%20status%3A%20ready%20for%20dev and to be assigned. You can learn more in our contributing guide https://github.com/EddieHubCommunity/LinkFree/blob/main/CONTRIBUTING.md

[SaraJaoude]

@badrivlog I have updated the labels so this shows status: ready for dev and I have assigned this to you

[eddiejaoude]

Thanks for the suggestion 👍 We could probably using the existing app config file config/app.json and add a new object to it with...

{
   // ...
   isr: {
      
   }
}