[gtk-web/new-website: 87/180] added license.txt

From: Emmanuele Bassi <ebassi src gnome org>
To: commits-list gnome org
Cc:
Subject: [gtk-web/new-website: 87/180] added license.txt
Date: Mon, 11 Nov 2019 14:51:43 +0000 (UTC)
commit d401c4f782585c2593a12780bb03c3d6fab57a96
Author: ravgeetdhillon <ravgeetdhillon gmail com>
Date:   Sat Jul 13 18:46:06 2019 +0530

    added license.txt

 CONTRIBUTING.md                | 185 ++++++++++++++++++++++++++++++++++++++++-
 LICENSE.txt                    | 153 ++++++++++++++++++++++++++++++++++
 README.md                      | 120 ++++++++++++++++++++++++--
 assets/.bin/primer-migrate     |  15 ----
 assets/.bin/primer-migrate.cmd |   7 --
 assets/css/markdown.css        |   1 -
 6 files changed, 451 insertions(+), 30 deletions(-)
---
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e43d45c..131af15 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1 +1,184 @@
-# Will be updating it shortly.
\ No newline at end of file
+---
+permalink: /contributing
+---
+:+1::tada: Thanks for taking the time to contribute! :tada::+1:
+# Introduction
+
+### Write something nice here!
+
+>First off, thank you for considering contributing to Active Admin. It's people like you that make Active 
Admin such a great tool.
+
+[source: [Active Admin](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md)] **Need more 
inspiration?** [1] [Read The Docs](http://read-the-docs.readthedocs.org/en/latest/contribute.html) [2] 
[Mustache.js](https://github.com/janl/mustache.js/#contributing)
+
+### Tell them why they should read your guidelines.
+
+>Following these guidelines helps to communicate that you respect the time of the developers managing and 
developing this open source project. In return, they should reciprocate that respect in addressing your 
issue, assessing changes, and helping you finalize your pull requests.
+
+[source: [Hoodie](https://github.com/hoodiehq/hoodie/blob/master/CONTRIBUTING.md)]
+
+### Explain what kinds of contributions you are looking for.
+
+Keep an open mind! Improving documentation, bug triaging, or writing tutorials are all examples of helpful 
contributions that mean less work for you.
+
+> Elasticsearch is an open source project and we love to receive contributions from our community — you! 
There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, 
submitting bug reports and feature requests or writing code which can be incorporated into Elasticsearch 
itself.
+
+[source: [Elasticsearch](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md)] **Need more 
inspiration?** [1] [Devise](https://github.com/plataformatec/devise/wiki/Contributing) [2] 
[Geocoder](https://github.com/alexreisner/geocoder#known-issue) (“known issue”)
+
+### Explain contributions you are NOT looking for (if any).
+
+Again, defining this up front means less work for you. If someone ignores your guide and submits something 
you don’t want, you can simply close it and point to your policy.
+
+> Please, don't use the issue tracker for [support questions]. Check whether the #pocoo IRC channel on 
Freenode can help with your issue. If your problem is not strictly Werkzeug or Flask specific, #python is 
generally more active. Stack Overflow is also worth considering.
+
+[source: [Flask](https://github.com/pallets/flask/blob/master/CONTRIBUTING.rst)] **Need more inspiration?** 
[1] 
[cucumber-ruby](https://github.com/cucumber/cucumber-ruby/blob/master/CONTRIBUTING.md#about-to-create-a-new-github-issue)
 [2] [Read the Docs](http://read-the-docs.readthedocs.org/en/latest/open-source-philosophy.html#unsupported)
+
+# Ground Rules
+### Set expectations for behavior (yours, and theirs).
+This includes not just how to communicate with others (being respectful, considerate, etc) but also 
technical responsibilities (importance of testing, project dependencies, etc). Mention and link to your code 
of conduct, if you have one.
+
+> Responsibilities
+> * Ensure cross-platform compatibility for every change that's accepted. Windows, Mac, Debian & Ubuntu 
Linux.
+> * Ensure that code that goes into core meets all requirements in this checklist: 
https://gist.github.com/audreyr/4feef90445b9680475f2
+> * Create issues for any major changes and enhancements that you wish to make. Discuss things transparently 
and get community feedback.
+> * Don't add any classes to the codebase unless absolutely needed. Err on the side of using functions.
+> * Keep feature versions as small as possible, preferably one new feature per version.
+> * Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. See the [Python 
Community Code of Conduct](https://www.python.org/psf/codeofconduct/).
+
+[source: [cookiecutter](https://github.com/audreyr/cookiecutter/blob/master/CONTRIBUTING.rst)] **Need more 
inspiration?** [1] 
[Celery](https://github.com/celery/celery/blob/master/CONTRIBUTING.rst#community-code-of-conduct) [2] 
[geocoder](https://github.com/alexreisner/geocoder#contributing)
+
+# Your First Contribution
+Help people who are new to your project understand where they can be most helpful. This is also a good time 
to let people know if you follow a label convention for flagging beginner issues.
+
+> Unsure where to begin contributing to Atom? You can start by looking through these beginner and 
help-wanted issues:
+> Beginner issues - issues which should only require a few lines of code, and a test or two.
+> Help wanted issues - issues which should be a bit more involved than beginner issues.
+> Both issue lists are sorted by total number of comments. While not perfect, number of comments is a 
reasonable proxy for impact a given change will have.
+
+[source: [Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#your-first-code-contribution)] 
**Need more inspiration?** [1] [Read the 
Docs](http://docs.readthedocs.org/en/latest/contribute.html#contributing-to-development) [2] 
[Django](https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/#first-steps) (scroll 
down to "Guidelines" as well)
+
+### Bonus points: Add a link to a resource for people who have never contributed to open source before.
+Here are a couple of friendly tutorials you can include: http://makeapullrequest.com/ and 
http://www.firsttimersonly.com/
+
+> Working on your first Pull Request? You can learn how from this *free* series, [How to Contribute to an 
Open Source Project on 
GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
+
+[source: [React](https://github.com/facebook/react/blob/master/CONTRIBUTING.md#pull-requests)]  
+
+As a side note, it helps to use newcomer-friendly language throughout the rest of your document. Here are a 
couple of examples from [Active 
Admin](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md):
+
+>At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner at 
first :smile_cat:
+>
+>If a maintainer asks you to "rebase" your PR, they're saying that a lot of code has changed, and that you 
need to update your branch so it's easier to merge.
+
+# Getting started
+### Give them a quick walkthrough of how to submit a contribution.
+How you write this is up to you, but some things you may want to include:
+
+* Let them know if they need to sign a CLA, agree to a DCO, or get any other legal stuff out of the way
+* If tests are required for contributions, let them know, and explain how to run the tests
+* If you use anything other than GitHub to manage issues (ex. JIRA or Trac), let them know which tools 
they’ll need to contribute
+
+>For something that is bigger than a one or two line fix:
+
+>1. Create your own fork of the code
+>2. Do the changes in your fork
+>3. If you like the change and think the project could use it:
+    * Be sure you have followed the code style for the project.
+    * Sign the Contributor License Agreement, CLA, with the jQuery Foundation.
+    * Note the jQuery Foundation Code of Conduct.
+    * Send a pull request indicating that you have a CLA on file.
+
+[source: [Requirejs](http://requirejs.org/docs/contributing.html)] **Need more inspiration?** [1] [Active 
Admin](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md#1-where-do-i-go-from-here) [2] 
[Node.js](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-contributions) [3] 
[Ember.js](https://github.com/emberjs/ember.js/blob/master/CONTRIBUTING.md#pull-requests)
+
+### If you have a different process for small or "obvious" fixes, let them know.
+
+> Small contributions such as fixing spelling errors, where the content is small enough to not be considered 
intellectual property, can be submitted by a contributor as a patch, without a CLA.
+>
+>As a rule of thumb, changes are obvious fixes if they do not introduce any new functionality or creative 
thinking. As long as the change does not affect functionality, some likely examples include the following:
+>* Spelling / grammar fixes
+>* Typo correction, white space and formatting changes
+>* Comment clean up
+>* Bug fixes that change default return values or error codes stored in constants
+>* Adding logging messages or debugging output
+>* Changes to ‘metadata’ files like Gemfile, .gitignore, build scripts, etc.
+>* Moving source files from one directory or package to another
+
+[source: [Chef](https://github.com/chef/chef/blob/master/CONTRIBUTING.md#chef-obvious-fix-policy)] **Need 
more inspiration?** [1] 
[Puppet](https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md#making-trivial-changes)
+
+# How to report a bug
+### Explain security disclosures first!
+At bare minimum, include this sentence:
+> If you find a security vulnerability, do NOT open an issue. Email XXXX instead.
+
+If you don’t want to use your personal contact information, set up a “security@” email address. Larger 
projects might have more formal processes for disclosing security, including encrypted communication. 
(Disclosure: I am not a security expert.)
+
+> Any security issues should be submitted directly to security travis-ci org
+> In order to determine whether you are dealing with a security issue, ask yourself these two questions:
+> * Can I access something that's not mine, or something I shouldn't have access to?
+> * Can I disable something for other people?
+>
+> If the answer to either of those two questions are "yes", then you're probably dealing with a security 
issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, 
so if you're unsure, just email us at security travis-ci org.
+
+[source: [Travis CI](https://github.com/travis-ci/travis-ci/blob/master/CONTRIBUTING.md)] **Need more 
inspiration?** [1] [Celery](https://github.com/celery/celery/blob/master/CONTRIBUTING.rst#security) [2] 
[Express.js](https://github.com/expressjs/express/blob/master/Security.md)
+
+### Tell your contributors how to file a bug report.
+You can even include a template so people can just copy-paste (again, less work for you).
+
+> When filing an issue, make sure to answer these five questions:
+>
+> 1. What version of Go are you using (go version)?
+> 2. What operating system and processor architecture are you using?
+> 3. What did you do?
+> 4. What did you expect to see?
+> 5. What did you see instead?
+> General questions should go to the golang-nuts mailing list instead of the issue tracker. The gophers 
there will answer or ask you to file an issue if you've tripped over a bug.
+
+[source: [Go](https://github.com/golang/go/blob/master/CONTRIBUTING.md#filing-issues)] **Need more 
inspiration?** [1] [Celery](https://github.com/celery/celery/blob/master/CONTRIBUTING.rst#other-bugs ) [2] 
[Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#reporting-bugs) (includes template)
+
+# How to suggest a feature or enhancement
+### If you have a particular roadmap, goals, or philosophy for development, share it here.
+This information will give contributors context before they make suggestions that may not align with the 
project’s needs.
+
+> The Express philosophy is to provide small, robust tooling for HTTP servers, making it a great solution 
for single page applications, web sites, hybrids, or public HTTP APIs.
+>
+> Express does not force you to use any specific ORM or template engine. With support for over 14 template 
engines via Consolidate.js, you can quickly craft your perfect framework.
+
+[source: [Express](https://github.com/expressjs/express#philosophy)] **Need more inspiration?** [Active 
Admin](https://github.com/activeadmin/activeadmin#goals)
+
+### Explain your desired process for suggesting a feature.
+If there is back-and-forth or signoff required, say so. Ask them to scope the feature, thinking through why 
it’s needed and how it might work.
+
+> If you find yourself wishing for a feature that doesn't exist in Elasticsearch, you are probably not 
alone. There are bound to be others out there with similar needs. Many of the features that Elasticsearch has 
today have been added because our users saw the need. Open an issue on our issues list on GitHub which 
describes the feature you would like to see, why you need it, and how it should work.
+
+[source: 
[Elasticsearch](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#feature-requests)] 
**Need more inspiration?** [1] 
[Hoodie](https://github.com/hoodiehq/hoodie/blob/master/CONTRIBUTING.md#feature-requests) [2] 
[Ember.js](https://github.com/emberjs/ember.js/blob/master/CONTRIBUTING.md#requesting-a-feature)
+
+# Code review process
+### Explain how a contribution gets accepted after it’s been submitted.
+Who reviews it? Who needs to sign off before it’s accepted? When should a contributor expect to hear from 
you? How can contributors get commit access, if at all?
+
+> The core team looks at Pull Requests on a regular basis in a weekly triage meeting that we hold in a 
public Google Hangout. The hangout is announced in the weekly status updates that are sent to the puppet-dev 
list. Notes are posted to the Puppet Community community-triage repo and include a link to a YouTube 
recording of the hangout.
+> After feedback has been given we expect responses within two weeks. After two weeks we may close the pull 
request if it isn't showing any activity.
+
+[source: [Puppet](https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md#submitting-changes)] 
**Need more inspiration?** [1] [Meteor](https://meteor.hackpad.com/Responding-to-GitHub-Issues-SKE2u3tkSiH ) 
[2] [Express.js](https://github.com/expressjs/express/blob/master/Contributing.md#becoming-a-committer)
+
+# Community
+If there are other channels you use besides GitHub to discuss contributions, mention them here. You can also 
list the author, maintainers, and/or contributors here, or set expectations for response time.
+
+> You can chat with the core team on https://gitter.im/cucumber/cucumber. We try to have office hours on 
Fridays.
+
+[source: 
[cucumber-ruby](https://github.com/cucumber/cucumber-ruby/blob/master/CONTRIBUTING.md#talking-with-other-devs)]
 **Need more inspiration?**
+ [1] [Chef](https://github.com/chef/chef/blob/master/CONTRIBUTING.md#-developer-office-hours) [2] 
[Cookiecutter](https://github.com/audreyr/cookiecutter#community)
+
+# BONUS: Code, commit message and labeling conventions
+These sections are not necessary, but can help streamline the contributions you receive.
+
+### Explain your preferred style for code, if you have any.
+
+**Need inspiration?** [1] [Requirejs](http://requirejs.org/docs/contributing.html#codestyle) [2] 
[Elasticsearch](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase)
+
+### Explain if you use any commit message conventions.
+
+**Need inspiration?** [1] 
[Angular](https://github.com/angular/material/blob/master/.github/CONTRIBUTING.md#submit) [2] 
[Node.js](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#step-3-commit)
+
+### Explain if you use any labeling conventions for issues.
+
+**Need inspiration?** [1] 
[StandardIssueLabels](https://github.com/wagenet/StandardIssueLabels#standardissuelabels) [2] 
[Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#issue-and-pull-request-labels)
\ No newline at end of file
diff --git a/LICENSE.txt b/LICENSE.txt
new file mode 100644
index 0000000..cf6d8b6
--- /dev/null
+++ b/LICENSE.txt
@@ -0,0 +1,153 @@
+Creative Commons Attribution-ShareAlike 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and 
conditions of this Creative Commons Attribution-
+ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be 
interpreted as a contract, You are granted the
+Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants 
You such rights in consideration of benefits the
+Licensor receives from making the Licensed Material available under these terms and conditions.
+
+Section 1 – Definitions.
+
+a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based 
upon the Licensed Material and in which the
+Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring 
permission under the Copyright and Similar
+Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical 
work, performance, or sound recording, Adapted
+Material is always produced where the Licensed Material is synched in timed relation with a moving image.
+b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions 
to Adapted Material in accordance with the
+terms and conditions of this Public License.
+c. BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by 
Creative Commons as essentially the
+equivalent of this Public License.
+d. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright 
including, without limitation, performance, broadcast,
+sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or 
categorized. For purposes of this Public License, the
+rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
+e. Effective Technological Measures means those measures that, in the absence of proper authority, may not 
be circumvented under laws fulfilling
+obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar 
international agreements.
+f. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to 
Copyright and Similar Rights that applies to Your use
+of the Licensed Material.
+g. License Elements means the license attributes listed in the name of a Creative Commons Public License. 
The License Elements of this Public License
+are Attribution and ShareAlike.
+h. Licensed Material means the artistic or literary work, database, or other material to which the Licensor 
applied this Public License.
+i. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public 
License, which are limited to all Copyright and Similar
+Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
+j. Licensor means the individual(s) or entity(ies) granting rights under this Public License.
+Donate
+k. Share means to provide material to the public by any means or process that requires permission under the 
Licensed Rights, such as reproduction, public
+display, public performance, distribution, dissemination, communication, or importation, and to make 
material available to the public including in ways that
+members of the public may access the material from a place and at a time individually chosen by them.
+l. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the 
European Parliament and of the Council of 11
+March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially 
equivalent rights anywhere in the world.
+m. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a 
corresponding meaning.
+
+Section 2 – Scope.
+
+a. License grant.
+1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, 
royalty-free, non-sublicensable, non-exclusive,
+irrevocable license to exercise the Licensed Rights in the Licensed Material to:
+A. reproduce and Share the Licensed Material, in whole or in part; and
+B. produce, reproduce, and Share Adapted Material.
+2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your 
use, this Public License does not apply, and
+You do not need to comply with its terms and conditions.
+3. Term. The term of this Public License is specified in Section 6(a).
+4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed 
Rights in all media and formats whether now
+known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives 
and/or agrees not to assert any right or
+authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, 
including technical modifications necessary to
+circumvent Effective Technological Measures. For purposes of this Public License, simply making 
modifications authorized by this Section 2(a)(4) never
+produces Adapted Material.
+5. Downstream recipients.
+A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically 
receives an offer from the Licensor to exercise
+the Licensed Rights under the terms and conditions of this Public License.
+B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You 
automatically receives an offer from the Licensor
+to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You 
apply.
+C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions 
on, or apply any Effective Technological
+Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of 
the Licensed Material.
+6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or 
imply that You are, or that Your use of the
+Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or 
others designated to receive attribution as
+provided in Section 3(a)(1)(A)(i).
+b. Other rights.
+1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are 
publicity, privacy, and/or other similar personality rights;
+however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the 
Licensor to the limited extent necessary to
+allow You to exercise the Licensed Rights, but not otherwise.
+2. Patent and trademark rights are not licensed under this Public License.
+3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of 
the Licensed Rights, whether directly or through a
+collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other 
cases the Licensor expressly reserves any
+right to collect such royalties.
+
+Section 3 – License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the following conditions.
+a. Attribution.
+1. If You Share the Licensed Material (including in modified form), You must:
+A. retain the following if it is supplied by the Licensor with the Licensed Material:
+i. identification of the creator(s) of the Licensed Material and any others designated to receive 
attribution, in any reasonable manner requested by
+the Licensor (including by pseudonym if designated);
+ii. a copyright notice;
+iii. a notice that refers to this Public License;
+iv. a notice that refers to the disclaimer of warranties;
+v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
+B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
+C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI 
or hyperlink to, this Public License.
+2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, 
and context in which You Share the
+Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or 
hyperlink to a resource that includes the required
+information.
+3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to 
the extent reasonably practicable.
+b. ShareAlike.
+In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following 
conditions also apply.
+1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this 
version or later, or a BY-SA Compatible
+License.
+2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may 
satisfy this condition in any reasonable manner
+based on the medium, means, and context in which You Share Adapted Material.
+3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective 
Technological Measures to, Adapted Material that
+restrict exercise of the rights granted under the Adapter's License You apply.
+
+Section 4 – Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed 
Material:
+a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share 
all or a substantial portion of the contents of the
+database;
+b. if You include all or a substantial portion of the database contents in a database in which You have Sui 
Generis Database Rights, then the database in
+which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including 
for purposes of Section 3(b); and
+c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the 
contents of the database.
+For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this 
Public License where the Licensed Rights include
+other Copyright and Similar Rights.
+
+Section 5 – Disclaimer of Warranties and Limitation of Liability.
+
+a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the 
+Licensor offers the Licensed Material as-is and as-available,
+and makes no representations or warranties of any kind concerning the Licensed Material, whether express, 
implied, statutory, or other. This
+includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, 
non-infringement, absence of latent or other
+defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where 
disclaimers of warranties are not allowed
+in full or in part, this disclaimer may not apply to You.
+b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, 
without limitation, negligence) or otherwise
+for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, 
expenses, or damages arising out of this
+Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of 
such losses, costs, expenses, or
+damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to 
You.
+c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner 
that, to the extent possible, most closely
+approximates an absolute disclaimer and waiver of all liability.
+
+Section 6 – Term and Termination.
+
+a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if 
You fail to comply with this Public License, then Your
+rights under this Public License terminate automatically.
+b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
+1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your 
discovery of the violation; or
+2. upon express reinstatement by the Licensor.
+For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek 
remedies for Your violations of this Public License.
+c. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or 
conditions or stop distributing the Licensed Material
+at any time; however, doing so will not terminate this Public License.
+d. Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
+
+Section 7 – Other Terms and Conditions.
+
+a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You 
unless expressly agreed.
+b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are 
separate from and independent of the terms and
+conditions of this Public License.
+
+Section 8 – Interpretation.
+
+a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, 
restrict, or impose conditions on any use of the
+Licensed Material that could lawfully be made without permission under this Public License.
+b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be 
automatically reformed to the minimum extent necessary
+to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License 
without affecting the enforceability of the remaining
+terms and conditions.
+c. No term or condition of this Public License will be waived and no failure to comply consented to unless 
expressly agreed to by the Licensor.
+d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any 
privileges and immunities that apply to the Licensor
+or You, including from the legal processes of any jurisdiction or authority.
\ No newline at end of file
diff --git a/README.md b/README.md
index 0a3eb84..d499aee 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,117 @@
-# Redesign of GNOME Toolkit's Official Website
+---
+permalink: /readme
+# layout: default
+---
 
-* Original website: [https://gtk.org](https://gtk.org)
-* New and upcoming website: [GTK Website](https://ravgeetdhillon.pages.gitlab.gnome.org/gtk-web)
+# GTK's Official Website
 
-All the valid  information about the redesign process is present here.
-[Wiki for GTK Website Redesign](https://wiki.gnome.org/Projects/GTK/WebsiteRedesign).
+We are soon going to replace the [current website](https://gtk.org) with this one: [Upcoming GTK 
Website](https://ravgeetdhillon.pages.gitlab.gnome.org/gtk-web)
 
-To report any bugs or request new features, report 
[here](https://gitlab.gnome.org/ravgeetdhillon/gtk-web/issues).
\ No newline at end of file
+## About
+
+GTK.org is a official website for GTK Project. The site is developed with and maintained using 
[Jekyll][official-jekyll], a Static Site Generator developed with Ruby. The site uses following types of 
files for the content generation:
+* HTML files with extension `.html`
+* Markdown files with extension `.md`
+
+The data used by the site is stored in the form of following files:
+* YAML files with extension `.yml`
+* JSON files with extension `.json`
+
+## Project Structure
+
+    ...
+    ├── _data                               #contains site's data files
+    │   ├── apps.yml                        #list of apps to show on index.html slider section
+    │   ├── navigation.yml                  #links to be added to the site's header and footer sections
+    │   ├── sample_codes.yml                #update this
+    │   ├── stuff.yml                       #site's global variables
+    │   └── usecases.yml                    #update this
+    ├── _includes                           #contains site's include files
+    │   ├── footer.html                     #the footer of the site
+    │   └── header.html                     #the header of the site
+    ├── _layouts                            #contains layout designs for site's pages
+    │   └── documentation.html              #layout design for pages that belong to GTK documentation
+    ├── _posts
+    ├── assets                              #contains site's valuable entities
+    │   ├── css                             #contains site's stylesheets
+    │   │   ├── colorful.css                #stylesheet for syntax highlighting
+    │   │   ├── index.css                   #stylesheet for user defined styles
+    │   │   ├── markdown.css                #stylesheet for styling the markdown content
+    │   │   ├── theme.css                   #stylesheet for website's theme. Generated from Bootstrap
+    │   │   └── theme.css.map
+    │   ├──img                              #contains site's images and illustrations
+    │   ├── js                              #contains site's javascripts
+    │   ├── scss                            #contains site's preprocessor stylesheets
+    │   │   └── theme.scss
+    ├── collections
+    │   └── _docs
+    ├── _config.yml                         #contains Jekyll settings for the site
+    ├── .gitignore
+    ├── .gitlab-ci.yml                      #for Gitlab Continuous Integration and Deployment
+    ├── 404.html
+    ├── CONTRIBUTING.md
+    ├── docs.html
+    ├── features.html
+    ├── Gemfile                             #contains gem dependencies for the site.
+    ├── Gemfile.lock
+    ├── index.html
+    ├── package-lock.json
+    ├── package.json                        #contains node dependencies for the site.
+    └── README.md
+
+## Contributing
+
+We always welcome people who want to contribute towards our project. For suitable information on how can you 
contribute to the website, on how to report bugs, on how to request new features or anything that can make 
the website a better experience for the end users, please read on [how to contribute][contributing].
+
+## Develop the website locally
+
+If you want to get the site up and running locally, here's the TLDR:
+
+```
+git clone https://gitlab.gnome.org/ravgeetdhillon/gtk-web.git
+cd gtk-web
+npm install
+bundle install
+```
+
+## Dependencies
+
+GTK.org relies on the dependencies as well. These dependencies are provided in the Ruby `Gemfile` or NPM's 
`package.json`. Following table shows the list of dependencies used by this project:
+
+Package | Version | File
+--- | --- | ---
+bootstrap | `4.3.1` | [package.json][package.json]
+@fortawesome/fontawesome-free | `5.8.2` | [package.json][package.json]
+jquery | `3.4.1` | [package.json][package.json]
+popper.js | `1.15.0` | [package.json][package.json]
+slick-carousel | `1.8.1` | [package.json][package.json]
+jekyll | `3.8.5` | [Gemfile][Gemfile]
+
+## Maintainers
+
+You can reach out to the following individuals if you have any doubt or suggestion regarding the GTK.org:
+
+**Ravgeet Dhillon**
+* You can contanct me via my [email](mailto:ravgeetdhillon gmail com).
+* You can also find me on IRC. I am `ravgeetdhillon` on `irc.gnome.org` in the `#gtk` or
+  `#gnome-hackers` channels.
+
+**Emmanuele Bassi**
+* You can contact me via my [email](mailto:ebassi gnome org).
+
+## Code of Conduct
+
+GTK is an open source project with a contributor community that spans across the globe. We want everyone in 
our community to feel safe and encourage the participation of people from all forms of backgrounds, 
regardless of experience level, age, gender, identity, race, religion, or nationality.
+We expect all contributors to uphold the [Code of Conduct][code-of-conduct].
+
+## License Information
+
+GTK.org is licensed under the [Creative Commons BY-SA-4.0][license].
+
+<!-- markdown variables -->
+[contributing]: CONTRIBUTING.MD
+[code-of-conduct]: CODE_OF_CONDUCT.MD
+[official-jekyll]: https://jekyllrb.com
+[package.json]: package.json
+[Gemfile]: Gemfile
+[license]: LICENSE.md
\ No newline at end of file
diff --git a/assets/css/markdown.css b/assets/css/markdown.css
index f2a47be..6d29e06 100644
--- a/assets/css/markdown.css
+++ b/assets/css/markdown.css
@@ -191,7 +191,6 @@
     padding: 0 16px;
     margin-bottom: 16px;
 }
-
 .markdown-body table {
     display: block;
     width: 100%;
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]