Often it happens that we either do not want to create OR it is just not feasible to create custom objects/metadata for storing configurations. Usually in such scenarios we prefer defining a mini JSON structure that act as a partial configuration/metadata that we then use in the code for business logic.
This does save us from few custom objects but the maintenance of such JSONs become cumbersome over time esp. large ones due to readability. Same goes for editing and updating the configuration. Also for integration projects we will typically have a log object where we store the Request/Response JSON for debugging/retrying etc. There too readability and editing of such JSONs from standard record editor is tedious. We then copy it and use some online JSON viewer tool to understand the configuration/structure.
To solve this challenge I have created this generic LWC component that can be added to any record layout where you save such JSON structures. Configure it with field api name that contains JSON values and tadam! - you can now view, edit and save the JSONs right within Salesforce and right within record.