This is the Schema App module for local caching of JSON-LD markup. It was developed for Schema App (https://www.schemaapp.com) customers to locally cache schema markup generated by our application.
The functionality of the application is to pull resources from the Schema App CDN and store them within the Drupal cache. Once in the cache it is stored for 24 hours before refreshing again from the CDN. These resources are then inserted in a script tag of type application/ld+json into the head for search engines to pick up resources.
Local caching is used to provide more reliable deployments of structured data so they can more easily be picked up by web wrawlers.
It does require a Schema App account to retrieve markup with an Account ID that we assign as well as the user's API key.
Project link
https://www.drupal.org/project/schemaapp
Git instructions
git clone --branch 8.x-1.x https://git.drupalcode.org/project/schemaapp.git
PAReview checklist
https://pareview.sh/pareview/https-git.drupal.org-project-schemaapp.git
Comments
Comment #2
avpadernoThank you for applying! I added the Git instructions for non-maintainer users and the PAReview checklist link. Reviewers will check the project and post comments to list what should be changed.
If you haven't done it, yet, please check the PAReview report and fix what needs to be fixed. There could be some false positives; verify that what reported is correct, before making any change.
Comment #3
avpadernoThe master branch is not correct. For Drupal 8, a branch like 8.x-1.x should be used.
It is also not clear if the account used to commit the code is a shared account, or an account used by a single person. The absence of first and last name, and the email associated with the account lead me to think this is a shared account.
Comment #4
SchemaApp commentedOk thank you for the quick response, sorry for my delay I'm still very new to Drupal. I have updated my master branch and re-ran that PAR review and I believe everything is passing. I think it was using an old branch before I had made those fixes, I have gone through and set a version 8 branch and it is now the default.
The account is shared yes, in the repo one developer has been working on it but Schema App is an organization.
Comment #5
SchemaApp commentedComment #6
avpadernoBasing on the Drupal.org Terms of Service, a shared account cannot be used for the following.
Each developer writing the code needs to use an account used only from that developer. The only way to continue this application is to give to the developer his/her account, and use that for continuing the application.
Comment #7
joelcummings commentedOk I have added myself and shawnhind to this project who are the developers at schema app, I hope this is acceptable and we can continue the application.
Comment #8
joelcummings commentedComment #9
vuilThank you for the contribution!
Please increase the project's page content, see more about Module documentation guidelines and Project page template. I created project issue about.
Comment #10
avpadernoComment #11
avpadernoWhile a better description of the module would help users who need the module, or are thinking to use the module, we review the files committed in the repository.
Comment #12
vuilThank you for the contribution!
I have not found any security related issues in the code.
Comment #13
klausiComment #14
klausiThanks for you contribution!
Otherwise looks good to me, did not see security issues.
Comment #15
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.
Comment #16
avpadernojoelcummings has not set a Git username, nor has he consented to the Git agreement. Without those steps, this application cannot be approved.
Comment #17
joelcummings commentedThank you all for reviewing! I have made some updates to address feedback and have updated my git username and accepted the agreement.
Comment #18
joelcummings commentedComment #19
avpaderno