Fab
@tvdeyen @kennyadsl we took a rather conservative stance on the PR. Do you have any particular legal information you would want to have contained in a second PR?
@alex-jansen the inverse of source code makes a lot of sense as usually the flow is I find a software and discover it's open source via a website and rarely...
1. Please restructure the form order as in attached image 2. contact email is missing on forms 3. Save button should be at right top and right bottom as in...
@rahulsingh321 in future PRs I kindly ask you to follow @tvdeyen more on the commit structure. Commit 1: Add Columns Commit 2: Add API and API Description Commit 3: Add...
@tvdeyen @kennyadsl looks good to me I know it looks like a huge commit but it's only a couple of columns on stores without any logic other than altering the...
@kennyadsl can we review this, it should be good to go.
> @fthobe please stop framing PRs and issues "your way" in the PR title. Thanks. @tvdeyen could you suggest a better name to get a hang of it? The resource...
> We should use the existing address form component, instead of introducing a second one. Also the PR adds a general new admin form for managing stores, which is very...
@tvdeyen replied to your comments
@tvdeyen I worked with the guys of schema to adjust the [Organization tags a little and complete them for European entities](https://github.com/schemaorg/schemaorg/pull/4387) as well and if no objections are raised that...