I am requesting a REVIEW for a new MR. Thanks )
Thanks will do !
hello thanks for reaching out, sorry i was on PTO. Yes it sounds like a great idea, I still need a month to finalize as I am running some beta tests with developers. Within a month when its deployed i will use the suggested changes with with release. Thnx )
Hello ugintl, yes, the SEO CoPilot module is still in its early stages. We are currently beta testing it with developers and testers. It should be about a month away from being bug-free. Thank you for your interest!
The submission for this project can be found at : https://medium.com/@snorzang65/google-summer-of-code-drupal-7b06e2ff5c25
FYI: The initial milestone for my SEO CoPilot project has been completed, but I am now looking beyond the original scope. I'm working to bring together all SEO-related modules into a comprehensive platform for SEO CoPilot.
I took some feedbacks from senior Drupal dev and made some changes and after carefully reviewing it I think this version, is easier to read and understand. Standardized the example theme name across all sections, improving comprehension.
Reordered content to introduce the StarterKit theme immediately after general theme information, aligning with modern Drupal capabilities. The reason for its adoption, emphasizing flexibility and ease of customization.
@kushneet I was hoping the community could enable read access to the deck it is limiting our ability to review and provide feedback. Thanks!
@thursday_bw, I completely agree with you!
It would be great if the community could enable at least read access to the deck so we can all contribute effectively. At the moment, it’s still locked, which is limiting our ability to review and provide feedback.
Additionally, I cross-checked all the links to ensure they are correctly referenced and still point to the appropriate resources )
1. Introduction Section:
Change:
Updated the explanation of a Drupal theme to include a clearer definition of its role in the presentation layer, ensuring clarity for beginners.
2. Location of Themes:
Change:
Added a note that Bartik and Seven were the default themes in earlier versions of Drupal but have been replaced by Olivero and Claro in Drupal 10+.
Clarified that organizing themes into contrib and custom folders is best practice but optional.
3. Note on Subdirectories:
Change:
Included a note clarifying that themes can technically be placed directly in the themes directory, though organizing them into subfolders (contrib, custom) is preferred.
4. Directory Structure Example Update:
Change:
Updated the directory structure examples to include Olivero and Claro instead of Bartik and Seven.
5. Theme Folder Structure:
Change:
Revised the theme folder structure to reflect the latest standards, while maintaining clarity on typical files like .info.yml, .libraries.yml, and template files.
6. Templates Section Update:
Change:
Clarified that Twig files are used for templates and provided a link to the official Twig documentation for further guidance.
Added examples for overriding node and block templates with specific naming conventions.
7. Best Practices for Template Organization:
Change:
Added best practices for organizing templates into subfolders (e.g., block and views templates).
8. Core Theme Example Update:
Change:
Replaced the Bartik folder structure example with Olivero, aligning with the current default theme in Drupal 10.
Included a note on the deprecation of Bartik and Seven.
9. Deprecation Note:
Change:
Added a specific note stating that Bartik and Seven have been deprecated and replaced by Olivero and Claro in Drupal 10.
Clarification of YAML Formatting:"Tabs are NOT allowed. Use spaces ONLY," could be unclear to newcomers. I have rephrased it to: "Use only spaces for indentation. Tabs are not allowed, and YAML requires proper indentation for correct parsing," to make it clearer that YAML requires specific formatting rules.
Base Theme Clarification: The original sentence, "If you are changing the base theme of an already-enabled theme, and the base theme is not enabled, uninstall then reinstall the theme so it registers and enables the new base theme," was unclear and could confuse new contributors. I have rephrased it to: "If you change the base theme, uninstall and reinstall the theme to ensure that the new base theme is correctly registered and enabled," to simplify the instructions for easier understanding.
Thanks a lot for your input @mindaugasd! your expertise could be a game changer for this project. If this project takes off, I'd love for you to come aboard. I'll drop you a message. It is given that I find manual SEO tedious; I want to create a solution that scales across all levels of Drupal use. I believe that If we get this right, it could revolutionize SEO automation for everyone from small users to large enterprises using drupal .
You are the best )
Hey @mindaugasd. I thought we also need to emphasize on prompt engineering for better results. I would really appreciate your input on prompt engineering part since you are the maintainer of AI prompt engineering ) I believe effective prompt engineering is crucial when interfacing with AI models because it can significantly impact the quality of the outcomes.
I have outlined a HLD, it outlines a process flow for integrating an SEO automation module into a medical website as a example. This includes starting with a questionnaire to gather general questions about the project, processing this information through a Drupal real-time SEO analyzer, and then interacting with a openai to refine seo practices based on the data received from the 'about us' page of a medical website.
Hey @ubulinux that checks out, awesome you are good then. I was a little worried there )
Thanks @devandra for stepping in. I really appreciate it currently I am talking to few maintainers including SEO AI, adrian and other mentor whom we can onboard in this task if they have time. Having a good understanding of the AI and tuning the algorithm will be crucial for the project success. I am very excited for this, what do you think ?
Don't take my word for it, but I think as long as the proposal for this project is submitted on the official google summer of code portal it should be fine. That is @ubulinux task as a contributor to submit a proposal so the org admins can rank the projects and select them, as for the issue can be submitted thereafter, the point of having an issue queue is for the students and other mentors to browse through the idea list proposed for the summer project. You can entirely not submit a issue queue, and turn in the proposal that should do as well !
No actually I am just contributing to seo ai. This project was proposed after the April 2nd deadline for proposal submission so I was not aware of this project. I saw your conversation and you pointed out so many resources couldn't help it but check it out, I was just curious about your idea ! I learnt so much from this conversation. SO COOL ! For this year I have only applied for SEO ai. l thought your insights in ai and prompt engineering, and as a senior engineer will be highly valuable for the seo ai project )
thanks for your constructive feedback. I want to clarify my approach regarding the chatbot functionalities, which might seem to shift from the initial analytical focus to a more interaction driven approach.
direct user interaction, the chatbot to respond immediately to user queries, similar to how Slackbot operates, this reduces user frustration and improves satisfaction. This real-time interaction can significantly enhance the user experience by providing instant support and answers, which i think is so important for user retention and satisfaction.
current rrupal documentation is brutal, it is quite dense and intimidating for new users. having interactive tutorials, we can help both new and existing users navigate and maximize Drupal’s functionalities. This approach not only makes the platform more accessible and user-friendly but also encourages greater user retention and active participation
automating admin tasks, streamlining managing user permissions and content updates. by automating these tasks, we not only enhance site maintenance efficiency but also free up administrators to focus on strategic growth and improvement initiatives.
I was thinking more in terms of refining the chatbot's functionalities to extend the original analytical aspirations by providing tangible, immediate benefits to both users and administrators. I got carried away.
I look forward to your thoughts )
Hi @mindaugasd, I've proposed a Google Summer of Code project this year focused on AI-driven SEO automation for Drupal. Given your deep expertise in AI integrations and community projects, your involvement as a maintainer could be incredibly impactful.
I have secured a mentor for the project, and I understand you're quite busy, but having your support would be invaluable, especially if the project progresses well. Here's the project link : https://www.drupal.org/project/gsoc/issues/3425856 →
I've also discussed potential integration with the SEO AI team, led by Adrian, as they currently have a sandbox project that could benefit from this module integration, serving this module as a base for future innovations. I look forward to your thoughts! https://www.drupal.org/project/seo_ai →
Thanks for the detailed breakdown, @mindaugasd! I gotta say that I'm not deeply versed in AI chat or analytics platforms like Google Analytics or Matomo, but your points make a lot of sense. I agree that enhancing Drupal's integration with them, instead of duplicating, could be more efficient and address scalability and data privacy more effectively. Which I didn't think before ;)
However, even with my limited expertise, I can see that a well-integrated chatbot might significantly improve user engagement and streamline administrative tasks within Drupal, such integration could be a big win for a lot of folks including me.
Bdw now I am curious. Any chance you have examples of any platforms have successfully integrated similar technologies, or specific features you think we should consider when designing our chatbot?
@mindaugasd I been following this chat thread, i found the conversations very interesting. what are your thoughts on the primary challenges we might face in terms of scalability and data privacy? I mean I do see this integration will enhance the Drupal community's engagement and the overall user experience.
Hello @everyone, my aim was to inspire and guide valuable contributions towards the shared goals.
However, I've noticed that my attempt has led to an overwhelming influx of messages on our thread, deviating from its intended purpose. This was not my intention, and I sincerely apologize for any confusion or inconvenience it may have caused.
That said, I must emphasize the importance of keeping our discussions focused and relevant to the project at hand. This ensures that we can all benefit from constructive and informative exchanges, facilitating a more effective collaboration process.
Hello @Laiba Maryam this is not the thread for this. You should navigate to the right thread related to SEO. This is the thread for newsletter module and also I checked your PNG image it also doesn't point toward any resources. Ensure that you are not spamming threads. Thanks
Hello @devendrasingh. Since this is a fairly complex project, this module as per our conversations it will generate real-time content creation, which means it needs to analyze and optimize content based on multiple criteria simultaneously. I am thinking that this will involve potentially complex AI model training which I have yet to learn. I am hoping that this project allows two contributor who can apply to a single project. I have been advised by Nick that this project should be split in 2 with clear separate goals for two contributors to work. So no dependencies ! Can you help me with a proposed plan. Thanks
update: Reflecting on the community's insights, I have redefined the scope of this project with an emphasis on intelligent automation and optimization. With a focus on simplifying complex SEO workflows and bring a new level of integration within the Drupal ecosystem not yet available.
I have gone through the project details. The most challenging aspect of this project is what information we need to update that is totally dependent on fireBase authentication. Referring to the link, point No: 4 : Create a change firebase user email REST endpoint.
We have included this project for Google summer of code' 24. I am willing to take this project on, if necessary )
improvised nesting :)
How's this for D11?
Re-Rolling patch. I think #10 patch is failed due to unrelated failure.
Patch for V11
Rerolling Patch for V11 :)
Updated patch's EOL conversion to Unix (LF) & UTF-8 Encoding.
Patch for V11 :)
new patch for D11.
I think this patch would work.
rerolling #34 to make the test pass.
This is my first Patch. Just checking for encoding errors.
// Ignore this patch
I am new to env. Checking the patch works or not.
Hello mherchel, I have one doubt regarding to this project.
I know how to make patches for this project. All thanks to Slack channel, where i found old chats. I have doubt that, docker is necessary?, why can't we make the project run through other tools. Like Xampp, or something else. Can you introduce me the with docker & its importance for this project ?