From d7dc45bfe0cb3d4e725a495c4a227ceb220056c0 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sun, 22 Nov 2020 23:04:01 +0545 Subject: [PATCH 01/21] Intial nav-bar setup Signed-off-by: Pratik Karki --- css/style.css | 14 ++++++++++++-- index.html | 27 +++++++++++++++++---------- 2 files changed, 29 insertions(+), 12 deletions(-) diff --git a/css/style.css b/css/style.css index a2750f9..33b5aba 100644 --- a/css/style.css +++ b/css/style.css @@ -2,6 +2,16 @@ html { font: 16px/1 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; } +body { + padding-top: 56px; + } + +section { + padding-top: 5rem; + padding-bottom: 5rem; +} + + li a { font-size: .875em; } @@ -118,9 +128,9 @@ nav { padding: 0 1.3em; } -nav h1 { +/* nav h1 { float: left; -} +} */ nav ul, footer a { diff --git a/index.html b/index.html index 50e4712..1d3284e 100644 --- a/index.html +++ b/index.html @@ -6,24 +6,32 @@ Git for Windows + + - + + -
-

Tools & Features

From d61611634e5d42878648a473b59ffb5e2027a5b9 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Mon, 23 Nov 2020 22:20:36 +0545 Subject: [PATCH 02/21] Fix section Signed-off-by: Pratik Karki --- index.html | 39 ++++++++++++++++++++++++++++++--------- 1 file changed, 30 insertions(+), 9 deletions(-) diff --git a/index.html b/index.html index 1d3284e..11b498e 100644 --- a/index.html +++ b/index.html @@ -28,17 +28,38 @@
  • Repository
  • Mailing List
    • -
    - Download -
    -
    -
    - Git Logo - Git Logo +
    +
    +
    +
    + Git Logo +

    We bring the awesome Git SCM to Windows

    +

    + Download + Contribute +

    + + +
    +
    +
    +

    We bring the awesome Git SCM to Windows

    +

    + Download + Contribute +

    +
    +
    + +
    +
    -
    +
    From 4434e4a37d6e7835ff7b922d187433c6ccbe9c7c Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 28 Nov 2020 21:40:19 +0545 Subject: [PATCH 03/21] Fix align of logo and text Signed-off-by: Pratik Karki --- index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 11b498e..5182c41 100644 --- a/index.html +++ b/index.html @@ -33,13 +33,13 @@
    -
    +
    Git Logo -

    We bring the awesome Git SCM to Windows

    + - +
    -->
    -
    -
    -

    Tools & Features

    -
    -
    +
    +
    +

    Tools & Features

    +

    Git for Windows focuses on offering a lightweight, native set of tools that bring the full feature set of the Git SCM to Windows while providing appropriate user interfaces for experienced Git users and novices alike.

    +
    +
    + Git BASH +

    Git BASH

    +

    Git for Windows provides a BASH emulation used to run Git from the command line. *NIX users should feel right at home, as the BASH emulation behaves just like the "git" command in LINUX and UNIX environments.

    +
    +
    + Git GUI +

    Git GUI

    +

    As Windows users commonly expect graphical user interfaces, Git for Windows also provides the Git GUI, a powerful alternative to Git BASH, offering a graphical version of just about every Git command line function, as well as comprehensive visual diff tools.

    +
    +
    + Gitk: Exploring Commits +

    Shell Integration

    +

    Simply right-click on a folder in Windows Explorer to access the BASH or GUI.

    +
    +
    + +
    -
    + +
    +
    +
    +

    Contribute

    +

    As an open source project, Git for Windows benefits greatly from both the volunteer work of helpful developers and good bug reports made by Git for Windows' users.

    +

    Governance Model

    +

    If you are interested in contributing to the Git for Windows project, have a look at the current governance model. There the roles of those involved in driving this project further down the road are described in detail.

    +

    Bug Reports & Feature Requests

    +

    If you've noticed a bug or simply have an idea that you'd like to see become real, why not work on it? Bug reports and feature requests are typically submitted to the issue tracker on our GitHub repository.

    + Issue Tracker +
    + Git for Windows Logo +

    Git for Windows SDK : Contributing Code

    +

    The Git for Windows SDK is a build environment that includes all the tools necessary for developers who want to contribute by writing code for Git for Windows.

    +

    Please look at the technical overview of the Git for Windows packaging and how to include your changes in your own custom installer.

    + Download Git for Windows SDK +

    To contribute/update this web page, see its Repository.

    +
    -
    +
    +
    +
    +
    +

    + +

    +

    +
    +
    + + +
    +
    + + - - - + \ No newline at end of file From 3b2db006b4c992ee6cbe2fc5a09b785ddbc97554 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sun, 29 Nov 2020 15:37:37 +0545 Subject: [PATCH 07/21] Add nojekyll file so that github doesn't imply jekyll Signed-off-by: Pratik Karki --- .nojekyll | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 .nojekyll diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 From 31ca1b75cae56630ecec7864f7c300ca5bb09cc4 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sun, 29 Nov 2020 17:26:45 +0545 Subject: [PATCH 08/21] Fix dangling id to contribute button --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index e93f0d4..43b4320 100644 --- a/index.html +++ b/index.html @@ -99,7 +99,7 @@

    Shell Integration

    -
    +

    Contribute

    As an open source project, Git for Windows benefits greatly from both the volunteer work of helpful @@ -167,4 +167,4 @@

    Git for Windows SDK : Contributing Code

    - \ No newline at end of file + From 1783ea385c537b5835ecbce34aadc98333d4b7fe Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Mon, 30 Nov 2020 11:23:58 +0545 Subject: [PATCH 09/21] Format css and remove commented out css Signed-off-by: Pratik Karki --- css/custom.css | 152 ++++++++++++++++++++++++------------------------- 1 file changed, 76 insertions(+), 76 deletions(-) diff --git a/css/custom.css b/css/custom.css index 795cf87..2cb402b 100644 --- a/css/custom.css +++ b/css/custom.css @@ -1,101 +1,101 @@ body { - padding-top: 56px; - } - - section { - padding-top: 5rem; - padding-bottom: 5rem; - } - - .lnr { - display: inline-block; - fill: currentColor; - width: 1em; - height: 1em; - vertical-align: -0.05em; - stroke-width: 1; - } - - .services-icon { - margin-bottom: 20px; - font-size: 30px; - } - - .quote-icon { - font-size: 40px; - margin-bottom: 20px; - } - - .gittext { - color: #646464; - font-weight: bold; - } - - .lowercase { - text-transform: lowercase; + padding-top: 56px; +} + +section { + padding-top: 5rem; + padding-bottom: 5rem; +} + +.lnr { + display: inline-block; + fill: currentColor; + width: 1em; + height: 1em; + vertical-align: -0.05em; + stroke-width: 1; +} + +.services-icon { + margin-bottom: 20px; + font-size: 30px; +} + +.quote-icon { + font-size: 40px; + margin-bottom: 20px; +} + +.gittext { + color: #646464; + font-weight: bold; +} + +.lowercase { + text-transform: lowercase; } h1, h2, h3, h4 { - font-weight: 300; + font-weight: 300; } h1 { - font-size: 2.500em; + font-size: 2.5em; } h1 span { - color: #969696; - font-size: .42em; - margin-left: .476em; + color: #969696; + font-size: 0.42em; + margin-left: 0.476em; } h2 { - font-size: 3em; - line-height: 1.3; + font-size: 3em; + line-height: 1.3; } h3 { - font-size: 1.875em; - line-height: 1.3; + font-size: 1.875em; + line-height: 1.3; } h4 { - font-size: 1.5em; - line-height: 1.1; + font-size: 1.5em; + line-height: 1.1; } -/* p { - margin-top: 0em ; - margin-bottom: 10em ; -} */ - li.borderless { - border-top: 0 none; - border-bottom: 0 none; - border-right: 0 none; - border-left: 0 none; - } - - .copyright { - padding: 28px 0; - margin-top: 55px; - background-color: #202020; } - .copyright span, - .copyright a { - color: #878787; - -webkit-transition: all 0.3s linear; - -o-transition: all 0.3s linear; - transition: all 0.3s linear; } - .copyright a:hover { - color:#007bff; } - - .copyright-menu ul { - text-align: right; - margin: 0; } - - .copyright-menu li { - display: inline-block; - padding-left: 20px; } + border-top: 0 none; + border-bottom: 0 none; + border-right: 0 none; + border-left: 0 none; +} + +.copyright { + padding: 28px 0; + margin-top: 55px; + background-color: #202020; +} +.copyright span, +.copyright a { + color: #878787; + -webkit-transition: all 0.3s linear; + -o-transition: all 0.3s linear; + transition: all 0.3s linear; +} +.copyright a:hover { + color: #007bff; +} + +.copyright-menu ul { + text-align: right; + margin: 0; +} + +.copyright-menu li { + display: inline-block; + padding-left: 20px; +} From 8c0a745ba9910af1d1369cff0f3934655505ad24 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 13 Nov 2021 13:22:27 +0545 Subject: [PATCH 10/21] Retire style.css Signed-off-by: Pratik Karki --- css/style.css | 361 -------------------------------------------------- 1 file changed, 361 deletions(-) delete mode 100644 css/style.css diff --git a/css/style.css b/css/style.css deleted file mode 100644 index 33b5aba..0000000 --- a/css/style.css +++ /dev/null @@ -1,361 +0,0 @@ -html { - font: 16px/1 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; -} - -body { - padding-top: 56px; - } - -section { - padding-top: 5rem; - padding-bottom: 5rem; -} - - -li a { - font-size: .875em; -} - -a { - color: #4B8CD2; - text-decoration: none; -} - -.gittext { - color: #646464; - font-weight: bold; -} - -.lowercase { - text-transform: lowercase; -} - -h1, -h2, -h3, -h4 { - font-weight: 300; -} - -h1 { - font-size: 3.125em; -} - -h1 span { - color: #969696; - font-size: .42em; - margin-left: .476em; -} - -h2 { - font-size: 3em; - line-height: 1.3; -} - -h3 { - font-size: 1.875em; - line-height: 1.3; -} - -h4 { - font-size: 1.5em; - line-height: 1.1; -} - -.content { - margin-left: auto; - margin-right: auto; - width: 65%; - min-width: 33em; - max-width: 56.25em; -} - -header { - background-color: #E1E1E1; - background-image: -webkit-gradient(radial, center center, 0px, center center, 100%, color-stop(0%, rgba(235, 235, 235, 0.7)), color-stop(50%, rgba(200, 200, 200, 0.3)), color-stop(100%, rgba(30, 30, 30, 0.25))); /* Chrome,Safari4+ */ - background-image: -webkit-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* FF3.6+ */ - background-image: -ms-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* IE10+ */ - background-image: -o-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* Opera 12+ */ - background-image: radial-gradient(ellipse at center, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#B3EBEBEB', endColorstr='#401E1E1E',GradientType=1); /* IE6-9 fallback on horizontal gradient */ - background-repeat: repeat; - height: 30.3125em; - padding-top: 0.6em; -} - -header h1 { - margin-top: .18em; -} - -header h2 { - font-size: 2.5em; - margin-top: 0; -} - -footer { - background-color: #C8C8C8; /* Old browsers */ - background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #C8C8C8), color-stop(100%, #FFFFFF)); /* Chrome,Safari4+ */ - background-image: -webkit-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* FF3.6+ */ - background-image: -ms-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* IE10+ */ - background-image: -o-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* Opera 11.10+ */ - background-image: linear-gradient(to bottom, #C8C8C8 0%, #FFFFFF 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#c8c8c8', endColorstr='#ffffff',GradientType=0); /* IE6-9 */ - border-top: solid 1px #F0F0F0; -} - -footer div { - padding-top: 0.9375em; -} - -footer h1 { - font-size: 1.375em; - margin-top: -0.273em; -} - -footer .gittext { - color: #969696; -} - -nav { - border-bottom: solid 1px #C8C8C8; - -webkit-box-sizing: border-box; - -moz-box-sizing: border-box; - box-sizing: border-box; - height: 4.375em; - margin-bottom: 2em; - padding: 0 1.3em; -} - -/* nav h1 { - float: left; -} */ - -nav ul, -footer a { - float: right; -} - -nav ul { - margin-top: 2.375em; -} - -nav li, -footer li { - text-transform: uppercase; - float: left; - margin-left: 1.5625em; -} - -div.version { - position: absolute; - margin-top: 5em; - text-transform: uppercase; - color: #646464; -} - -.feature article { - position: relative; - padding-right: 0px; - width: 49.2%; - margin-left: auto; - margin-right: 0em; - height: 20em; -} - -.feature h2 { - border-bottom: solid 1px #BEBEBE; - color: #828282; - line-height: 1.625em; - margin-bottom: 0.375em; - padding: 0.125em 0.375em; -} - -.button { - background-color: #4B8CE9; /* Old browsers */ - background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#4B8CE9), color-stop(100%,#2C66B8)); /* Chrome,Safari4+ */ - background-image: -webkit-linear-gradient(top, #4B8CE9 0%,#2C66B8 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-linear-gradient(top, #4B8CE9 0%, #2C66B8 100%); /* FF3.6+ */ - background-image: -ms-linear-gradient(top, #4B8CE9 0%,#2C66B8 100%); /* IE10+ */ - background-image: -o-linear-gradient(top, #4B8CE9 0%,#2C66B8 100%); /* Opera 11.10+ */ - background-image: linear-gradient(to bottom, #4B8CE9 0%,#2C66B8 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#4B8CE9', endColorstr='#2C66B8',GradientType=0); /* IE6-9 */ - -webkit-box-shadow: inset 0 1px 0 hsla(0, 100%, 100%, 0.2), inset 0 0 2px hsla(0, 100%, 100%, 0.2), 0 1px 2px hsla(0, 0%, 0%, 0.29); - -moz-box-shadow: inset 0 1px 0 hsla(0, 100%, 100%, 0.2), inset 0 0 2px hsla(0, 100%, 100%, 0.2), 0 1px 2px hsla(0, 0%, 0%, 0.29); - box-shadow: inset 0 1px 0 hsla(0, 100%, 100%, 0.2), inset 0 0 2px hsla(0, 100%, 100%, 0.2), 0 1px 2px hsla(0, 0%, 0%, 0.29); - -webkit-border-radius: 0.238em; - -moz-border-radius: 0.238em; - border-radius: 0.238em; - border: 1px solid #0A3A7D; - color: white; - display: inline-block; - font-size: 1.3125em; - padding: 0.476em 3%; - text-align: center; - text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.4); -} - -.featurebutton { - float: left; - margin: 0 1%; - width: 41%; -} - -.imagerollover { - float: left; - position: relative; - width: 46.5%; -} - -.imagerollover img { - position: absolute; - -webkit-transition: opacity 1s ease-in-out; - -moz-transition: opacity 1s ease-in-out; - -o-transition: opacity 1s ease-in-out; - transition: opacity 1s ease-in-out; - width: 100%; - height: auto; -} - -.imagerollover .top:hover { - opacity: 0; -} - -.vcentercontainer { - display: table; - height: 100%; -} - -.vcentercontainer div { - display: table-cell; -} - -.vcentercontainer div, -.vcentercontainer img { - vertical-align: middle; -} - -.vcentercontainer img { - margin: 2.8125em auto; -} - -.details { - background-color: #2C66B8; -} - -.details article { - border-bottom: solid 0.3125em #00478F; - border-top: solid 0.3125em #00478F; -} - -.details .gittext { - color: #FFFFFF; -} - -.details p { - margin-top: 0; -} - -.details p a { - color: #A3CFFF; - text-decoration: underline; -} - -.details h2 { - background-color: #4A7CC2; - border-bottom: solid 0.104em #7198C1; - border-top: solid 0.104em #7198C1; - -webkit-box-shadow: 0 0 0.8333em rgba(0, 0, 0, 0.4); - -moz-box-shadow: 0 0 0.8333em rgba(0, 0, 0, 0.4); - box-shadow: 0 0 0.8333em rgba(0, 0, 0, 0.4); - clear: both; - color: #FFFFFF; - margin-bottom: 0.625em; - margin-top: 0.9375em; - padding: 0.1875em 0; - text-align: center; - text-shadow: 0 -1px rgba(0, 0, 0, 0.5); -} - -.details h3 { - color: #F5F5F5; - margin-bottom: 0; - margin-top: 0.8333em; - text-shadow: 0 -1px rgba(0, 0, 0, 0.35); -} - -.details h4 { - color: #F5F5F5; - margin-bottom: 0; - margin-top: 0.75em; - text-shadow: 0 -1px rgba(0, 0, 0, 0.35); -} - -.details .button { - border: 1px solid #464646; - background-color: #E0E0E0; /* Old browsers */ - background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#E0E0E0), color-stop(100%,#A3A3A3)); /* Chrome,Safari4+ */ - background-image: -webkit-linear-gradient(top, #E0E0E0 0%,#A3A3A3 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-linear-gradient(top, #E0E0E0 0%, #A3A3A3 100%); /* FF3.6+ */ - background-image: -ms-linear-gradient(top, #E0E0E0 0%,#A3A3A3 100%); /* IE10+ */ - background-image: -o-linear-gradient(top, #E0E0E0 0%,#A3A3A3 100%); /* Opera 11.10+ */ - background-image: linear-gradient(to bottom, #E0E0E0 0%,#A3A3A3 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#E0E0E0', endColorstr='#A3A3A3',GradientType=0); /* IE6-9 */ - margin-right: 1%; - text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.6); -} - -.details .content { - height: 39.0625em; -} - -.details p { - color: #EBEBEB; - line-height: 1.9375em; - margin-bottom: 0.3125em; - text-shadow: 0 -1px rgba(0, 0, 0, 0.35); -} - -.details .vcentercontainer:first-child { - margin-right: 5%; -} - -.verticalgallery { - float: none; - text-align: center; -} - -.verticalgallery img { - border: solid 0.3125em #5881BD; - -webkit-box-shadow: 0 0 2.8125em rgba(0, 0,0, 0.17); - -moz-box-shadow: 0 0 2.8125em rgba(0, 0, 0, 0.17); - box-shadow: 0 0 2.8125em rgba(0, 0, 0, 0.17); - margin: 1.875em auto; - width: 100%; - height: auto; -} - -.detailstext { - float: left; - width: 58%; -} - -.detailsimg { - float: left; - width: 35%; -} - -.contributecontent .detailsimg * { - width: 100%; - height: auto; -} - -.list-unstyled { - list-style-type: none; - padding-left: 0; -} - -.stud { - clear: both; -} From 102cebc6dc073bee66ef6a200ff5d8fa6d1031a5 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 13 Nov 2021 13:25:07 +0545 Subject: [PATCH 11/21] Update index html and css * Fix for navbar while on small device * Add version of git for windows available * Other minor UI fixes Signed-off-by: Pratik Karki --- css/custom.css | 23 ++++++++++++++++------- index.html | 36 ++++++++++++++++++------------------ 2 files changed, 34 insertions(+), 25 deletions(-) diff --git a/css/custom.css b/css/custom.css index 2cb402b..da313aa 100644 --- a/css/custom.css +++ b/css/custom.css @@ -1,5 +1,5 @@ body { - padding-top: 56px; + padding-top: 5%; } section { @@ -44,6 +44,7 @@ h4 { h1 { font-size: 2.5em; + text-align: center; } h1 span { @@ -74,28 +75,36 @@ li.borderless { border-left: 0 none; } -.copyright { +.img-git-logo { + width: 40%; +} + +.img-other-logos { + width: 90% +} + +.footer { padding: 28px 0; margin-top: 55px; background-color: #202020; } -.copyright span, -.copyright a { +.footer span, +.footer a { color: #878787; -webkit-transition: all 0.3s linear; -o-transition: all 0.3s linear; transition: all 0.3s linear; } -.copyright a:hover { +.footer a:hover { color: #007bff; } -.copyright-menu ul { +.footer-menu ul { text-align: right; margin: 0; } -.copyright-menu li { +.footer-menu li { display: inline-block; padding-left: 20px; } diff --git a/index.html b/index.html index 43b4320..fd6c27f 100644 --- a/index.html +++ b/index.html @@ -1,7 +1,7 @@ - + Git for Windows @@ -18,9 +18,9 @@ - + - +
    - -
    @@ -78,21 +81,21 @@

    Tools & Features

    providing appropriate user interfaces for experienced Git users and novices alike.

    - Git BASH + Git BASH

    Git BASH

    Git for Windows provides a BASH emulation used to run Git from the command line. *NIX users should feel right at home, as the BASH emulation behaves just like the "git" command in LINUX and UNIX environments.

    - Git GUI + Git GUI

    Git GUI

    As Windows users commonly expect graphical user interfaces, Git for Windows also provides the Git GUI, a powerful alternative to Git BASH, offering a graphical version of just about every Git command line function, as well as comprehensive visual diff tools.

    - Gitk: Exploring Commits + Gitk: Exploring Commits

    Shell Integration

    Simply right-click on a folder in Windows Explorer to access the BASH or GUI.

    @@ -116,7 +119,7 @@

    Bug Reports & Feature Requests

    Issue Tracker
    - Git for Windows Logo +

    Git for Windows SDK : Contributing Code

    The Git for Windows SDK is a build environment that includes all the tools necessary for developers who want to contribute by writing code for Git for Windows.

    @@ -130,12 +133,8 @@

    Git for Windows SDK : Contributing Code

    href=" https://github.com/git-for-windows/git-for-windows.github.io">Repository.

    - - - -
    -
    +
    @@ -143,7 +142,7 @@

    Git for Windows SDK : Contributing Code

    -
    +
    • All Releases @@ -158,13 +157,14 @@

      Git for Windows SDK : Contributing Code

    -
    -
    -
    + + + + From 2a10050af7b1ffb599a8acefd466207d55fef2e5 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 13 Nov 2021 13:26:27 +0545 Subject: [PATCH 12/21] Update templates as per the new design Signed-off-by: Pratik Karki --- governance-model.html | 342 +++++++++++++++++++++++------------------ markdown-template.html | 113 ++++++++------ requirements.html | 97 +++++++----- 3 files changed, 324 insertions(+), 228 deletions(-) diff --git a/governance-model.html b/governance-model.html index 5f737c2..fa7070b 100644 --- a/governance-model.html +++ b/governance-model.html @@ -6,166 +6,210 @@ Git for Windows - - - + + + + + + + - -
    + + +
    +
    -

    Git for Windows governance model

    -

    Overview

    -

    Git for Windows is led by a benevolent dictator (Johannes Schindelin) and managed by the community. That is, -the community actively contributes to the day-to-day maintenance of the project, but the general strategic -line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the -benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to -progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent -dictator through active engagement and contribution.

    -

    Roles and responsibilities

    -

    Benevolent dictator (project lead)

    -

    Typically, the benevolent dictator, or project lead, is self-appointed. However, because the community -always has the ability to fork, this person is fully answerable to the community. The project lead’s role is a -difficult one: -they set the strategic objectives of the project and communicate these clearly to the -community. They also have to understand the community as a whole and strive to satisfy as many -conflicting needs as possible, while ensuring that the project survives in the long term.

    -

    In many ways, the role of the benevolent dictator is less about dictatorship and more about -diplomacy. The key is to ensure that, as the project expands, the right people are given influence -over it and the community rallies behind the vision of the project lead. The lead’s job is then to ensure -that the committers (see below) make the right decisions on behalf of the project. Generally speaking, -as long as the committers are aligned with the project’s strategy, the project lead will allow them to -proceed as they desire.

    -

    Committers

    -

    Committers are contributors who have made several valuable contributions to the project and are -now relied upon to both write code directly to the repository and screen the contributions of others. In -many cases they are programmers but it is also possible that they contribute in a different -role. Typically, a committer will focus on a -specific aspect of the project, and will bring a level of expertise and understanding that earns them -the respect of the community and the project lead. The role of committer is not an official one, it is -simply a position that influential members of the community will find themselves in as the project lead -looks to them for guidance and support.

    -

    Committers have no authority over the overall direction of the project. However, they do have the ear -of the project lead. It is a committer’s job to ensure that the lead is aware of the community’s needs -and collective objectives, and to help develop or elicit appropriate contributions to the project. Often, -committers are given informal control over their specific areas of responsibility, and are assigned -rights to directly modify certain areas of the source code. That is, although committers do not have -explicit decision-making authority, they will often find that their actions are synonymous with the -decisions made by the lead.

    -

    Contributors

    -

    Contributors are community members who either have no desire to become committers, or have not -yet been given the opportunity by the benevolent dictator. They make valuable contributions, such as -those outlined in the list below, but generally do not have the authority to make direct changes to the -project code. Contributors engage with the project through communication tools, such as the -mailing list, -GitHub, via reports of issues -and via pull requests in the issue tracker, as detailed in our -how to participate document.

    -

    Anyone can become a contributor. There is no expectation of commitment to the project, no specific -skill requirements and no selection process. To become a contributor, a community member simply -has to perform one or more actions that are beneficial to the project.

    -

    Some contributors will already be engaging with the project as users, but will also find themselves -doing one or more of the following:

    -
      -
    • supporting new users (current users often provide the most effective new user support)
      • -
    • reporting bugs
      • -
    • identifying requirements
      • -
    • supplying graphics and web design
      • -
    • programming
      • -
    • assisting with project infrastructure
      • -
    • writing documentation
      • -
    • fixing bugs
      • -
    • adding features
      • -
    -

    As contributors gain experience and familiarity with the project, they may find that the project lead -starts relying on them more and more. When this begins to happen, they gradually adopt the role of -committer, as described above.

    -

    Users

    -

    Users are community members who have a need for the project. They are the most important -members of the community: without them, the project would have no purpose. Anyone can be a user; -there are no specific requirements.

    -

    Users should be encouraged to participate in the life of the project and the community as much as -possible. User contributions enable the project team to ensure that they are satisfying the needs of -those users. Common user activities include (but are not limited to):

    -
      -
    • evangelising about the project
      • -
    • informing developers of project strengths and weaknesses from a new user’s perspective
      • -
    • providing moral support (a ‘thank you’ goes a long way)
      • -
    • providing financial support
      • -
    -

    Users who continue to engage with the project and its community will often find themselves becoming -more and more involved. Such users may then go on to become contributors, as described above.

    -

    Support

    -

    All participants in the community are encouraged to provide support for new users within the project -management infrastructure. This support is provided as a way of growing the community. Those -seeking support should recognise that all support activity within the project is voluntary and is -therefore provided as and when time allows. A user requiring guaranteed response times or results -should therefore seek to purchase a support contract from a vendor. (Of course, that vendor should -be an active member of the community.) However, for those willing to engage with the project on its -own terms, and willing to help support other users, the community support channels are ideal.

    -

    Contribution process

    -

    Anyone can contribute to the project, regardless of their skills, as there are many ways to contribute. -For instance, a contributor might be active on the project mailing list and issue tracker, or might supply -pull requests. The various ways of contributing are described -in more detail in our how to participate document.

    -

    The Git for Windows issue tracker is the most appropriate -place for a contributor to ask for help when making their first contribution. Please also read the projects -issue reporting guidelines

    -

    Decision-making process

    -

    The benevolent dictatorship model does not need a formal conflict resolution process, since the -project lead’s word is final. If the community chooses to question the wisdom of the actions of a -committer, the project lead can review their decisions by checking the email archives, and either -uphold or reverse them.

    +

    Git for Windows governance model

    +

    Overview

    +

    Git for Windows is led by a benevolent dictator (Johannes Schindelin) and managed by the + community. That is, + the community actively contributes to the day-to-day maintenance of the project, but the general + strategic + line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the + benevolent dictator’s job to resolve disputes within the community and to ensure that the project is + able to + progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the + benevolent + dictator through active engagement and contribution.

    +

    Roles and responsibilities

    +

    Benevolent dictator (project lead)

    +

    Typically, the benevolent dictator, or project lead, is self-appointed. However, because the community + always has the ability to fork, this person is fully answerable to the community. The project lead’s + role is a + difficult + one: + they set the strategic objectives of the project and communicate these clearly to the + community. They also have to understand the community as a whole and strive to satisfy as many + conflicting needs as possible, while ensuring that the project survives in the long term.

    +

    In many ways, the role of the benevolent dictator is less about dictatorship and more about + diplomacy. The key is to ensure that, as the project expands, the right people are given influence + over it and the community rallies behind the vision of the project lead. The lead’s job is then to + ensure + that the committers (see below) make the right decisions on behalf of the project. Generally speaking, + as long as the committers are aligned with the project’s strategy, the project lead will allow them to + proceed as they desire.

    +

    Committers

    +

    Committers are contributors who have made several valuable contributions to the project and are + now relied upon to both write code directly to the repository and screen the contributions of others. In + many cases they are programmers but it is also possible that they contribute in a different + role. Typically, a committer will focus + on a + specific aspect of the project, and will bring a level of expertise and understanding that earns them + the respect of the community and the project lead. The role of committer is not an official one, it is + simply a position that influential members of the community will find themselves in as the project lead + looks to them for guidance and support.

    +

    Committers have no authority over the overall direction of the project. However, they do have the ear + of the project lead. It is a committer’s job to ensure that the lead is aware of the community’s needs + and collective objectives, and to help develop or elicit appropriate contributions to the project. + Often, + committers are given informal control over their specific areas of responsibility, and are assigned + rights to directly modify certain areas of the source code. That is, although committers do not have + explicit decision-making authority, they will often find that their actions are synonymous with the + decisions made by the lead.

    +

    Contributors

    +

    Contributors are community members who either have no desire to become committers, or have not + yet been given the opportunity by the benevolent dictator. They make valuable contributions, such as + those outlined in the list below, but generally do not have the authority to make direct changes to the + project code. Contributors engage with the project through communication tools, such as the + mailing list, + GitHub, via reports of issues + and via pull requests in the issue tracker, + as detailed in our + how to participate + document.

    +

    Anyone can become a contributor. There is no expectation of commitment to the project, no specific + skill requirements and no selection process. To become a contributor, a community member simply + has to perform one or more actions that are beneficial to the project.

    +

    Some contributors will already be engaging with the project as users, but will also find themselves + doing one or more of the following:

    +
      +
    • supporting new users (current users often provide the most effective new user support)
      • +
    • reporting bugs
      • +
    • identifying requirements
      • +
    • supplying graphics and web design
      • +
    • programming
      • +
    • assisting with project infrastructure
      • +
    • writing documentation
      • +
    • fixing bugs
      • +
    • adding features
      • +
    +

    As contributors gain experience and familiarity with the project, they may find that the project lead + starts relying on them more and more. When this begins to happen, they gradually adopt the role of + committer, as described above.

    +

    Users

    +

    Users are community members who have a need for the project. They are the most important + members of the community: without them, the project would have no purpose. Anyone can be a user; + there are no specific requirements.

    +

    Users should be encouraged to participate in the life of the project and the community as much as + possible. User contributions enable the project team to ensure that they are satisfying the needs of + those users. Common user activities include (but are not limited to):

    +
      +
    • evangelising about the project
      • +
    • informing developers of project strengths and weaknesses from a new user’s perspective
      • +
    • providing moral support (a ‘thank you’ goes a long way)
      • +
    • providing financial support
      • +
    +

    Users who continue to engage with the project and its community will often find themselves becoming + more and more involved. Such users may then go on to become contributors, as described above.

    +

    Support

    +

    All participants in the community are encouraged to provide support for new users within the project + management infrastructure. This support is provided as a way of growing the community. Those + seeking support should recognise that all support activity within the project is voluntary and is + therefore provided as and when time allows. A user requiring guaranteed response times or results + should therefore seek to purchase a support contract from a vendor. (Of course, that vendor should + be an active member of the community.) However, for those willing to engage with the project on its + own terms, and willing to help support other users, the community support channels are ideal.

    +

    Contribution process

    +

    Anyone can contribute to the project, regardless of their skills, as there are many ways to contribute. + For instance, a contributor might be active on the project mailing list and issue tracker, or might + supply + pull requests. The various ways of + contributing are described + in more detail in our how to + participate document.

    +

    The Git for Windows issue tracker is + the most appropriate + place for a contributor to ask for help when making their first contribution. Please also read the + projects + issue reporting + guidelines

    +

    Decision-making process

    +

    The benevolent dictatorship model does not need a formal conflict resolution process, since the + project lead’s word is final. If the community chooses to question the wisdom of the actions of a + committer, the project lead can review their decisions by checking the email archives, and either + uphold or reverse them.

    -
    -
    +
    +
    +
    +
    +
    + Copyright © 2020 Johannes Schindelin and contributors. All rights reserved. +
    + +
    +
    + +
    +
    +
    -
    - - + + + + + }); + diff --git a/markdown-template.html b/markdown-template.html index eccfdd1..3d6421d 100644 --- a/markdown-template.html +++ b/markdown-template.html @@ -1,63 +1,90 @@ + Git for Windows - - - + + + + + + + - -
    -
    - <%= document %> -
    -
    - + + + + + + - - - + + + From d7677859ea6c0974dbb548cbf7391a06bddbf5df Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Fri, 19 Nov 2021 21:40:00 +0545 Subject: [PATCH 17/21] Introduce blue again Signed-off-by: Pratik Karki --- css/custom.css | 2 +- index.html | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/css/custom.css b/css/custom.css index 3826895..23464df 100644 --- a/css/custom.css +++ b/css/custom.css @@ -91,7 +91,7 @@ li.borderless { .footer { padding: 28px 0; margin-top: 55px; - background-color: #202020; + background-color: #00478f; } .footer span, .footer a { diff --git a/index.html b/index.html index 2335d50..86e027d 100644 --- a/index.html +++ b/index.html @@ -23,7 +23,7 @@ -
    -
    +

    Tools & Features

    Git for Windows focuses on offering a lightweight, native set of tools that bring From 35229225d4bfc8f46fe3c4f5acbb941d6f610d99 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Fri, 19 Nov 2021 23:42:59 +0545 Subject: [PATCH 18/21] Experimental designs for feedback Signed-off-by: Pratik Karki --- css/custom.css | 1 - index.html | 80 +++++++++++++++++++++++++++++++++++--------------- 2 files changed, 56 insertions(+), 25 deletions(-) diff --git a/css/custom.css b/css/custom.css index 23464df..bff6b2d 100644 --- a/css/custom.css +++ b/css/custom.css @@ -28,7 +28,6 @@ section { .gittext { color: #646464; - font-weight: bold; font-family: 'Open Sans', sans-serif; } diff --git a/index.html b/index.html index 86e027d..0efddc3 100644 --- a/index.html +++ b/index.html @@ -24,10 +24,8 @@

    -
    -
    - Git Logo +
    + + + +
    +

    +

    Git for Windows

    +

    -
    -
    -

    -

    We bring Git to Windows

    -

    -

    - Download - Contribute -

    -

    - - Version 2.34.0 - -

    -
    +
    +
    +
    +

    + Download + Contribute +

    +

    + + Version 2.34.0 + +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    From 28b175651754138ff2f385a4a5e20d4714f367e7 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 20 Nov 2021 22:48:47 +0545 Subject: [PATCH 19/21] Fix formatting for small and large screens Signed-off-by: Pratik Karki --- index.html | 45 +++++---------------------------------------- 1 file changed, 5 insertions(+), 40 deletions(-) diff --git a/index.html b/index.html index 0efddc3..3fc27ca 100644 --- a/index.html +++ b/index.html @@ -49,18 +49,15 @@
    -
    - - - -
    -

    +

    +
    +

    Git for Windows

    -
    -
    +
    +

    Git for Windows

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    From 5de28e8155cbc804e8baf56c4f7007261a7a66e3 Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 20 Nov 2021 23:14:39 +0545 Subject: [PATCH 20/21] Fix colors per contrast ratio adjustment Signed-off-by: Pratik Karki --- css/custom.css | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/css/custom.css b/css/custom.css index bff6b2d..eb01a77 100644 --- a/css/custom.css +++ b/css/custom.css @@ -2,6 +2,10 @@ body { padding-top: 5%; } +.navbar-dark .navbar-nav .nav-link { + color: #b2b8bd; +} + section { padding-top: 5rem; padding-bottom: 5rem; @@ -94,11 +98,11 @@ li.borderless { } .footer span, .footer a { - color: #878787; + color: #BBBBBB; -webkit-transition: all 0.3s linear; -o-transition: all 0.3s linear; transition: all 0.3s linear; } .footer a:hover { - color: #007bff; + color: #80BDFF; } From 98c98c9e1395b99580c0dd9791edf7f7cb7f579c Mon Sep 17 00:00:00 2001 From: Pratik Karki Date: Sat, 20 Nov 2021 23:37:52 +0545 Subject: [PATCH 21/21] Link color contrast fixes Signed-off-by: Pratik Karki --- css/custom.css | 8 ++++++++ index.html | 19 ++++++++++--------- 2 files changed, 18 insertions(+), 9 deletions(-) diff --git a/css/custom.css b/css/custom.css index eb01a77..bed33f3 100644 --- a/css/custom.css +++ b/css/custom.css @@ -6,6 +6,14 @@ body { color: #b2b8bd; } +.lcolor{ + color: #07488f; +} + +.ncolor { + color: #0b6bd3; +} + section { padding-top: 5rem; padding-bottom: 5rem; diff --git a/index.html b/index.html index 3fc27ca..0648374 100644 --- a/index.html +++ b/index.html @@ -65,7 +65,8 @@

    Git for Windows

    Contribute

    - + Version 2.34.0

    @@ -73,11 +74,11 @@

    Git for Windows

    -
    +

    Tools & Features

    -

    Git for Windows focuses on offering a lightweight, native set of tools that bring - the full feature set of the Git SCM to Windows while +

    Git for Windows focuses on offering a lightweight, native set of tools that bring + the full feature set of the Git SCM to Windows while providing appropriate user interfaces for experienced Git users and novices alike.

    @@ -106,31 +107,31 @@

    Shell Integration

    Contribute

    As an open source project, Git for Windows benefits greatly from both the volunteer work of helpful - developers and good bug + developers and good bug reports made by Git for Windows' users.

    Governance Model

    If you are interested in contributing to the Git for Windows project, have a look at the current - governance model. There the roles of those involved in driving this + governance model. There the roles of those involved in driving this project further down the road are described in detail.

    Bug Reports & Feature Requests

    If you've noticed a bug or simply have an idea that you'd like to see become real, why not work on it? Bug reports and feature requests are typically submitted to the issue tracker on our GitHub repository. + target="_blank" class="ncolor">issue tracker on our GitHub repository.


    Git for Windows SDK : Contributing Code

    The Git for Windows SDK is a build environment that includes all the tools necessary for developers who want to contribute by writing code for Git for Windows.

    -

    Please look at the technical +

    Please look at the technical overview of the Git for Windows packaging and how to include your changes in your own custom installer.

    Download Git for Windows SDK

    To contribute/update this web page, see its Repository.

    + href=" https://github.com/git-for-windows/git-for-windows.github.io" class="ncolor">Repository.