# Description Currently `Environments` page and the `Folders` view of environments in a folder are two separate pages, with different implementation, components and data-fetching. That provides a bad UX for our customers, as they have to learn two different ways the same type of data is represented. It also makes it harder to maintain and expand the functionality of the environments page, as we need to keep track, which new features are added to `Environments` page and make sure they are accessible for the folders view as well. ## Current implementation | Environments | Folders | | ------ | ------ | |  | | | | | # Proposed solution We need to use the same design and share the components between to pages. Ideally, we would end up with the same page component and just feed different data into it based on the URL route. This will bring us the following benefits: 1. Reused code will make the maintenance of these pages easier. 2. Feature parity will be achieved automatically 3. The users will have better UX as they'll work with the same page structure and components. 4. The UX can be improved even further, if we implement a single page navigation between the two. That will make page transitions faster, and given the caching and pre-fetching, even instantaneous.