Hi @Shashank_Shah, please join our Slack community ( https://www.drupal.org/join-slack → ) to get in touch with mentors.
royalpinto007 → created an issue.
Adding @gauravvvv as a mentor for this project after consulting him!
An example of such integration is the Firebase Authentication module ( https://www.drupal.org/project/firebase_authentication → ), which enables Drupal sites to authenticate users via Firebase authentication methods. We can follow a similar approach for integrating Supabase authentication with Drupal.
royalpinto007 → created an issue.
royalpinto007 → created an issue.
Missed this comment, attaching a screenshot for all the details!
@fjgarlin
I am using Chrome's latest version and it's 100%.
Attaching a screenshot for your reference-
I've cleared my cache to rule out any issues on my end. This problem seems to be specific to my OS.
Here are my OS details:
Name: Ubuntu 22.04.03 LTS
OS Type: 64-bit
GNOME Version: 42.9
royalpinto007 → created an issue.
royalpinto007 → made their first commit to this issue’s fork.
@PratikSolanki
I thought the same about building a floating window at first, but since this project involves providing extensive documentation and onboarding resources, I believe a full separate page for the chatbot interface would be more suitable.
A full separate page would allow us to create a more immersive and engaging experience for users, with plenty of space to display information and integrate the creative-commons licensed Drupal documentation.
Furthermore, a full separate page would enable us to use Drupal's built-in functionality to create custom templates and styles for the chatbot interface. This would allow us to design a unique and visually appealing interface that complements the rest of the website.
In terms of attribution, using the revision history to identify contributors to the docs is a responsible and effective approach that can help ensure proper citation of sources.
I've created a user interface for the project. Drawing inspiration from ChatGPT's graphics and icons, I've included similar elements to help users identify different conversation options. My UI design is distinct and tailored to the project's needs, aiming to make the conversation engaging and easy to navigate.
I'm eager to receive feedback to refine and improve the design.
royalpinto007 → made their first commit to this issue’s fork.
Hello @nick_vh, @yashn_99!
My name is Royal, and I am currently a sophomore student at the National Institute of Technology Karnataka, Surathkal. I am thrilled to see the initiative to develop a chat-bot style interface for asking common questions about Drupal. I believe this will greatly benefit those who are new to Drupal and are looking for a quick and easy way to learn Drupal basics. Additionally, I appreciate the effort to incorporate attribution by using the revision history to identify contributors to the docs, which is a responsible approach to address AI plagiarism concerns.
As a beginner, I too encountered certain difficulties when setting up Drupal on my local system, despite the availability of documentation and drupal-slack-support. However, I was able to overcome these obstacles. In such a scenario, a chatbot could provide prompt assistance.
Apart from my situation, some examples of how a chatbot can be useful specifically for Drupal:
- Troubleshooting: Can be programmed to provide assistance with Drupal troubleshooting, helping users resolve issues they encounter while setting up or managing a Drupal website.
- Documentation: Provide quick and easy access to Drupal documentation, making it easier for users to find the information they need to resolve issues or complete tasks.
- Training: Assistance with Drupal training, helping users learn how to use Drupal effectively and efficiently.
- Support: Chatbots can provide support for Drupal-related issues, helping users resolve technical issues or errors they encounter while using Drupal.
- Best Practices: Chatbots can provide guidance on Drupal best practices, helping users optimize their Drupal websites for performance, security, and user experience. (like I faced, when I was searching about the development checks that are present or established prior on Drupal, in order to fix coding standards or resolve phpcs error, etc)
Some ideas to achieve the project goals could be:
- Create an API that provides access to Drupal documentation and community resources. This API could be used to develop new chat-bot interfaces and other AI-powered resources that make it easier for users to learn Drupal and participate in the Drupal community.
- Use Drupal APIs to create a platform that allows users to track their contributions to the Drupal community.
- Develop an AI-powered chat-bot interface that can answer common questions about Drupal using Drupal APIs to retrieve and present relevant information from the Drupal community.
As a novice in this field, I am fully aware that this project may require some guidance and mentorship, but I am eager to put in the effort and time required to learn and contribute to the project. I am highly motivated to gain new skills and knowledge that would enable me to make a meaningful contribution to the project's success.
In case you need more information from me, I will definitely provide it. I am excited about the opportunity to work on this project and contribute to the Drupal community.
I would like to propose that the project be categorized under the 350-hour limit, given its experimental nature and the potentially substantial amount of time required to work on it. By keeping the project within this scope, we can ensure that sufficient time is allocated to research and develop it thoroughly while maintaining a reasonable and achievable timeline.
Hello @Nick_vh,
My name is Royal, and I am currently a sophomore student at the National Institute of Technology Karnataka, Surathkal. I am very interested in the project to implement a secure system for automatically installing updates in Drupal. I believe this project can significantly improve the security of Drupal sites and lower the total cost of ownership for maintaining a Drupal site, making it more accessible for users.
As a beginner, I understand that this project may require some guidance, but I am willing to put in the time and effort to learn and contribute to the project. I have experience with Git and some knowledge of Drupal and Composer, which I believe will be helpful in completing this project. I have also contributed to some of the novice issues in Drupal, which has made me more comfortable in working with Drupal.
In case you need more information from me, I will definitely provide it. I am excited about the opportunity to work on this project and contribute to the Drupal community. I believe that the final deliverables, a proof of concept automated update system and clear documentation for other contributors, will be valuable assets to the Drupal community.
royalpinto007 → made their first commit to this issue’s fork.
The use of the term "blacklist" in technology has been criticized for perpetuating negative connotations and associations with blackness. By removing this term from our code and documentation, we are taking a small but important step towards creating a more welcoming and inclusive environment for all users.
This commit updates the documentation for the Drupal API page to provide more clarity on accessing the original entity object in a multi-language context. It also suggests alternative methods for retrieving the original translation if $entity->original does not refer to the expected translation. This should help improve understanding for developers working with Drupal in a multi-language context.
royalpinto007 → made their first commit to this issue’s fork.
Previously, the isMethodType function in the HTTP Request class compared the HTTP method type case-sensitively. This made it difficult to match method types that were entered in a different case from the expected value. This commit updates the function to use strtoupper on both the $method_type parameter and the $method property, allowing for case-insensitive comparison.
As a beginner, it was good to learn from the statements provided above in the problem/motivation section.
Thanks!
royalpinto007 → made their first commit to this issue’s fork.
Hello,
I would like to inform you that I have made all the required changes in MR #7. I hope you find the modifications satisfactory.
Could you please take the time to review the changes and provide your feedback?
I would greatly appreciate it.
royalpinto007 → made their first commit to this issue’s fork.
royalpinto007 → made their first commit to this issue’s fork.
Thank you for reviewing and identifying the mistakes in the parameter definition. I have now updated the definition to fix those mistakes. I appreciate your help in making this better!
Quite unsure about the YAML plugins, can be added MR later on.
Sure, I will make the required changes.
This change ensures that the margin of the node__submitted class only affects the top margin, which can improve consistency and readability. By using margin-top instead of margin, we can also reduce the potential for unintended side effects or conflicting styles that may arise from using the shorthand margin property.
royalpinto007 → made their first commit to this issue’s fork.
I updated the margin values of .form-actions .action-link to match the 0.5rem margin used for .dropbutton-wrapper in the Claro theme's dropbutton.css file. This will ensure that the margins are consistent across both types of buttons.
We can even think of updating the margin values of the .dropbutton-wrapper CSS to match the 1rem margin used for .form-actions .action-link in the Claro theme's form.css file.
royalpinto007 → made their first commit to this issue’s fork.
I've built the file and ran some local tests, and it looks like everything is working as expected. No errors were encountered during testing.
This refactor has been a long time coming, and I'm glad we finally got around to making these changes.
The system-admin panel is a critical component of Claro, and it's important that it looks and works its best.
I hope these changes make the experience for our users smoother and more enjoyable.
If you have any questions or concerns about these changes, please let me know.
Thanks!
Please review the latest commit with the original file.
Changes done:
- Replaced physical properties (left, right, etc.) with their logical equivalents (inline-start, inline-end, etc.)
- Combined multiple tablesort classes into one
If you have any feedback or questions, please let me know.
I would also like to contribute further by solving additional issues to align with the latest coding standards, if this works.
Hi @quietone,
With this commit, I've refactored the ConfigController class by implementing the ContainerInjectionInterface and utilizing dependency injection to pass in its required dependencies. This change improves the code maintainability and flexibility.
Please let me know if you have any questions or concerns.
Thanks!
Oops, I didn't notice that it was already assigned to someone else. I apologize for the same.
Also, I made changes in the code taking some reference from the Stack Overflow website.
This change was made to enhance the user experience and improve page performance. By utilizing AJAX, we are able to retrieve and update data asynchronously, allowing the user to interact with the page while data is being loaded. The Gridstack container children serve as a perfect candidate for this functionality, as they require frequent updates to their contents.
royalpinto007 → made their first commit to this issue’s fork.
Got it, thanks for the review @cliefen.
I have made the required modifications and reverted back my old commit.
To fix the return type, we need to make sure that the return value of the method is always an int or a string.
If the return value is not set, we can either set it to a default value (such as 0 or an empty string) or generate a new identifier for the entity.
royalpinto007 → made their first commit to this issue’s fork.
Kindly review the previously submitted merge request. I regret to inform that a new one was created in error.
https://git.drupalcode.org/project/drupal/-/merge_requests/3408/diffs?co... Can someone check the current problem now?
It would be really helpful.
(Made an API definition for the function, which allows other modules to alter the condition definitions.
However, the function inside needs further updates to meet the requirements.)
royalpinto007 → made their first commit to this issue’s fork.
It fails for 1 test, how to fix that?
I just wanted to inform you that I have removed the use of FormattableMarkup in log messages and have instead passed the message as the first parameter and the parameters as the second. This change ensures a more consistent and efficient logging system. Let me know if there are any questions or concerns.
Please check if it's correct- https://git.drupalcode.org/issue/entity_hierarchy-3295326/-/commit/fb5a8...
Could you kindly assign this issue to me?