Alternative Hreflang for SEO is a Drupal module that allows the language code in hreflang attributes to be customized, without writing any code and without altering the registered langcode used in the website's URLs. This might be needed when you (or a previous developer) have added a custom language to the site with a custom langcode and you have since been advised there is a more suitable ISO language code for the hreflang attribute, but you do not want to repoint all of your existing pages.
The module provides an admin settings form which lists all of the languages enabled on the website and allows the language codes to be customised for the hreflang attribute only. The settings form enables a site owner or SEO agency, when granted the relevant permissions, to make changes to the hreflang language codes without needing a developer to add code to a custom module.
Similar modules
The key difference between this project and https://www.drupal.org/project/hreflang is that if you want to alter the language code in the hreflang element, then Hreflang requires code to be written in a custom module whereas this module does not. Hreflang might be a better starting point for developers who want full control over the code and would like to do more with the hooks they are writing; this is a simple implementation to assist non-developers.
Comments
Comment #2
kewesley commentedComment #3
vishal.kadamThank you for applying!
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.
The important notes are the following.
phpcs --standard=Drupal,DrupalPracticeon the project, which alone fixes most of what reviewers would report.To the reviewers
Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.
The important notes are the following.
For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.
Comment #4
vishal.kadamComment #5
kewesley commentedThank you Vishal.
I have run phpcs as suggested and have also added the Gitlab CI template.
Comment #6
vishal.kadamUsually, after reviewing a project, we allow the developer to opt projects into security advisory coverage.
This project is too small for us and it doesn't contain enough PHP code to really assess your skills as a developer.
Have you created any other project on drupal.org (module, theme, distribution) we could instead review? The project needs to have most of the commits (preferable all the commits) done by you.
Comment #7
kewesley commentedUnfortunately, I don't have any other projects on drupal.org yet where I have committed the majority of the code to the project. I will keep this in mind when creating projects in future.
Thank you for your time.
Comment #8
kewesley commented