-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simpler way of proposing changes to documentation needed #312
Comments
There are tools available which can help you, @robbiejackson started with one and now is the main contributor so. |
Hi Roger, |
only 4 months later! Thanks @robbie I did just join the mattermost - I think I might be rogerco on there if rogercreagh doesn't exist. But in simple terms I have cloned this repo, do I just make changes in my copy and then generate a PR? I'm back here because I found another page which misses a key piece of very useful information that I managed to find eventually, and it would seem sensible to share it (its on https://manual.joomla.org/docs/general-concepts/javascript/js-library/joomla-dialog/) |
@rogercreagh I think I found you on mattermost and sent you a message there. You can find it if you look for Direct Messages from me. Robbie |
I am hopelessly lost in trying to propose improvements and corrections to the manual.
As per instructions I have created a fork of this repository and made changes there. But when I try to make a pull request it just says
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
and I have no idea what to do, not can I find any instructions within the manual itself.Part of the problem is that I have never used GitHub for anything other than personal use - not collaborating with anyone else so I probably don't understand how to make pull requests (or even what they really are).
I appreciate GitHub is a very powerful tool for projects with multiple contributors - but I really dont have the time or the inclination to learn how to use it. I've tried but the learning curve seems incredibly steep and off putting.
However I do find the Joomla dev manual a potentially very useful resource but it is full of errors, typos and incomplete or completely missing bits which sometimes I could easily correct.
Is there not someone to whom I could simply email some proposed changes and they could press whatever obscure combination of buttons is needed to make the magic happen and get corrections published. It is very frustrating to see a work with easily fixable mistakes but not have any simple way of correcting them.
Just a suggestion.
For now I will continue to annotate my fork of the manual as I see fit and just have to live with the fact that I can't contribute back to the community. Is this sensible (I don't think so). Could the process not be made simpler (it probably does seem simple to those of you who use it regularly, but to an outsider it is very obscure)
Thanks for listening.
The text was updated successfully, but these errors were encountered: