-
Notifications
You must be signed in to change notification settings - Fork 103
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
Community #60
Community #60
Conversation
…uests, updating the source in an image, community guidelines and social media (not sure that last one needs a page)
tasks people can do Conflicts: source/community/index.html.haml
… request (mostly documenting my learning experience)
|
||
We want the ManageIQ community to be a nice place to hang out and we | ||
expect community members to treat each other with courtesy and respect. | ||
Please familiarise yourself with our |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
US English uses the 'z': familiarize
Do you think we could commit this and integrate your changes in a different commit? Seems like a valuable addition and I really am not sure how to propose an alternative version. I agree with most of your changes. |
Hmmm... just realised this change is now proposed twice - once on this branch, and once as a separate pull request. Clearly I'm still confused by this pull request thing... I should be reading the docs, not writing them ;-) I did find this good answer (at least, it looked good to me) in Stack Overflow: http://stackoverflow.com/a/15055649/334301 |
Issues with the headersI don't like the headers:
We can't say "People" and "Developers". So what do we say? (Continued below) Rewording?Well, we can turn around the headings and talk about the tasks people will be doing with the software.
...but then it gets a bit wordy. Also, it's usually best to not have gerunds (those things that usually end in '-ing') in headlines.
...like above, are both redundant, as this is on a site about ManageIQ. "Use" and "Develop" are too short, and "use" isn't really what those links are about. Most everything in the "Use" section is actually about communication. Rethinking the section splitIt's really about communication.
So, really, we have competing things inside of the current "Users & Admins" section (more real-time communication and then communicating usage). It might be better to split these currently-two sections into three sections: "Communicate", "Educate", and "Develop". (Educate could be "Document", but the goal with documentation is education, really. Educate is an obvious action word, where as "Document" could be interpreted as either a verb or a noun... but really, either could be fine.) Summary: I suggest to split into "Communicate", "Educate", and "Develop". AdditionallyAlso, it would be best to have the content displayed on this page in a different manner. Rather than simply lists of links; we should make it stand out more. This can be achieved by several different means, including text rewording and formatting or perhaps some graphical elements. (However, tossing graphics at something doesn't necessarily help and it also takes time.) However... build uponThese changes are probably a little bit larger than this pull request. We already have too many things going on here. For example, when I will rewrite this commit to make it more acceptable to inclusion, I will be sure to split out the documentation on patches as a separate commit from the editing of the community front page. Therefore, I think it's acceptable to merge in the patch with some minor edits (squash & split) and then, afterward, build on top of the commit with the suggestions I have made here. |
I've manually merged in the changes as worked on in this branch as two different commits. As such, the content has been merged as intended in this pull request, so I'm closing the issue. |
Opened #62 for working on the content further. |
I would have preferred a squashed commit here... the end result is the important thing.
This is modelled on what JM and myself came up with, and there are some lminks in here twice, since they're relevant both for users & developers. Working on several of the empty pages/dead links now.