Rename “Git Instructions” to something technical, like “Version Control”.

Create a “How To Install” tab with instructions to install and URL/download links.

#5 1164606_tab_rename.patch1.59 KBeliza411
#4 tab_case.png12.78 KBeliza411
Members fund testing for the Drupal project. Drupal Association Learn more


eliza411’s picture

Project: infrastructure » Project Git instructions
Version: » 6.x-1.x-dev
Component: Git » User interface

Moving this to the Git instructions queue.

Is the "How To Install" tab supposed to be a sub-tab of the "Version Control" tab?

Bojhan’s picture

Status: Active » Needs work

Can we rename this to "Version Control"? The How to install tab seems to be a new issue.

eliza411’s picture

Status: Needs work » Active

Not sure why this is set to needs work with no patch attached. Setting to active.

eliza411’s picture

12.78 KB

Should this be "Version control" or "Version Control"?

On, main level tabs are title case, while the sub-tabs seem to be title cased.


eliza411’s picture

Status: Active » Needs review
1.59 KB

The attached patch changes Git instructions to Version control.

helmo’s picture

It makes some sense to generalize this. But on the other hand the tab is very much geared to Git, which I don't expect to change anytime soon ;)

It might also be somewhat misleading.
Wouldn't you expect on a Version control tab to find the links "Repository viewer" and "View commits"?

eliza411’s picture

@helmo: I agree with what you've said, that renaming the tab to "Version control" is likely to mislead those who know what version control and Git are. I was guessing that the Usability people are willing to accept that in exchange for not actively misleading the Drupal users who think that 'Git instructions' means 'Get instructions.'

From what I can see, this two-word change will not give users the data they were seeking when they thought it said "Get instructions." It will contribute to making the experience for contributors and folks who work with version control a little more convoluted. It will invalidate screen casts, screen shots, documentation, and training. I'm not sure who is expected to update docs on what time line, nor do I know about any other change management related to this request.

That said, I posted a patch because it seemed to me like renaming the tab would address the specific confusion for the target users of the main project page on and that the contributor interface/experience is already so problematic, what's another misleading link?

Thanks for raising the issue. It probably warrants discussion.

webchick’s picture

Yeah, sorry. The original post was not 100% clear (my fault; the poster was following instructions).

The usability problem we ran into here was that newbies get overwhelmed at the sight of most project pages and their eyes dart frantically around the screen looking for anything to help. They've been trained through the use of Drupal to look at the tabs area for additional options. They also scan for keywords that make sense to them when they're lost.

At least two people, if not three, clicked "Git instructions" and said aloud "Oh, looks like here I can read some instructions" (it's a good thing we were in a sound-proof room, because the collective head-slapping and groaning was immense! ;)) I think the obvious way to fix this is to switch our version control system to Bazaar, because no one is going to click a tab called "Bazaar instructions" (I kid ;)).

But yes, this issue is about renaming that tab to something more technical so that it doesn't tempt new users to click it.

Dave Reid’s picture

Maybe to *support* more than one VCS, maybe we could do:
project/project-name/version-control = 'Version control' as local task
project/project-name/version-control/git = 'Git' as sub-local task

helmo’s picture

Well, supporting multiple version control systems would be a huge undertaking. Seeing how long it took us to go to Git I doubt this would anytime soon.

Also multiple vcs's would require a whole lot of documentation to be duplicated or be complicated with multiple vcs options.

webchick’s picture

Yeah, I really think that support for other VCSes is entirely out of scope. This issue is just about changing the label of the tab to be a little scarier, so newbies don't click it.

dcmistry’s picture

Sounds dumb in my head but I still ask, how about - "Git" instructions?

Bojhan’s picture

Status: Needs review » Reviewed & tested by the community

I am a bit disappointing about how long this takes, can we just change it to "Version control" already.

I am marking eliza's patch RTBC.

eliza411’s picture

It's @helmo's call on committing this. My domain is limited to the instructions themselves.

helmo’s picture

committed this.
I think I was waiting for some magical stamp of approval... anyway lets move forward.

Bojhan’s picture

Status: Reviewed & tested by the community » Fixed

fixed then?

helmo’s picture

Well sort of, it still needs to be deployed on d.o

eliza411’s picture

@Bojhan, do the usability folks have any plans to support updating the documentation that is invalidated by this change once is live on d.o.?

Bojhan’s picture

/me looks around for usability folks.

I don't think so, I am not involved in d.o docs.

eliza411’s picture

To actually get this deployed, *someone* who wants to see the change happen is supposed to be involved in docs, at least in theory. (See Step 12 at

At any rate, the change is in and deployment is a whole separate thing.

Bojhan’s picture

Status: Fixed » Needs work

So basically, we need someone who wants to change like at least 25 mentions of this in the docs. I will not be able to dedicate time for it, in the upcoming month (vacation + paper). If anyone else wants to step up, or knows the process to get others involved in doing so - I would greatly appreciate it.

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

I think this is a good change. It shouldn't take more than a minute each to change
Git instructions -> Version control
in each doc page. If there are only 25, that shouldn't be too difficult, and I'd be glad to help.

1) click Edit on the page
(2) Use browser control-F to find "Git instructions", and change each instance to "Version control".
(3) Paste a message into the log field (once you've made one message, make the others the same).
(4) Click Save.

And to find the pages that need updating, Search on d.o for "Git instructions" and narrow to Documentation pages. This shouldn't be too hard...

eliza411’s picture

fixing deployment tag per #1091722: Workflow for future updates and

I also opened an issue for the removal of the 'needs d.o deployment' so it will be less confusing in the future (hopefully). #1188194: Two deployment tags

drumm’s picture

Can someone do a tagged release of this module? Ideally, we don't use too many dev versions of modules on d.o.

helmo’s picture

OK, I just created a 6.x-1.1 release node.

drumm’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -needs deployment


webchick’s picture

Automatically closed -- issue fixed for 2 weeks with no activity.

alank-alank’s picture

Issue summary: View changes

cara belajar musik dari pemula sampai profesional.
semua ada disini

dhalbert’s picture

Issue summary: View changes

undo spammer change

  • Commit 7a3529b on 6.x-1.x, 7.x-1.x-dev by helmo:
    Issue #1164696 by eliza411 | raytiley: Fixed “Git instructions” is...
  • Commit c785275 on 7.x-1.x-dev by helmo:
    Issue #1164696 by eliza411 | raytiley: Fixed “Git instructions” is...