Skip to content

Documentation cleanup #3484

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Nov 16, 2017
Merged

Documentation cleanup #3484

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e325b0
Kill the FAQ
smarter Nov 16, 2017
a49ee2c
Remove references to the mailing-list
smarter Nov 16, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,6 @@ This is the process for committing code to the Scala project. There are of cours
1. Make sure you have signed the [Scala CLA](http://typesafe.com/contribute/cla/scala), if not, sign it.
2. Before starting to work on a feature or a fix, it's good practice to ensure that:
1. There is a ticket for your work in the project's [issue tracker](https://github.com/lampepfl/dotty/issues);
2. If not, create it first (perhaps given a thumbs up from the dotty-internals mailing list first);
2. The ticket has been discussed and prioritized by the team.
3. You should always perform your work in its own Git branch. The branch should be given a descriptive name that explains its intent. Some teams also like adding the ticket number and/or the [GitHub](http://github.com) user ID to the branch name, these details is up to each of the individual teams. (See below for more details on branch naming.)
4. When the feature or fix is completed you should open a [Pull Request](https://help.github.com/articles/using-pull-requests) on GitHub.
Expand Down
2 changes: 0 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ Community build: [![Community Build Status](https://travis-ci.org/lampepfl/dotty

* [Homepage](http://dotty.epfl.ch)
* [Documentation](http://dotty.epfl.ch/docs)
* [FAQ](http://dotty.epfl.ch/#why-dotty)
* [Mailing list](https://groups.google.com/forum/#!forum/dotty-internals)

Try it out
==========
Expand Down
124 changes: 0 additions & 124 deletions docs/_includes/faq.html
View file
Open in desktop

This file was deleted.

10 changes: 0 additions & 10 deletions docs/_includes/logo-page.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,6 @@
Try it now
</a>
</li>
<li class="nav-item">
<a class="nav-link" href="#why-dotty">
FAQ
</a>
</li>
<li class="nav-item">
<a class="nav-link" href="{{ site.baseurl }}/blog/index.html">
Blog
Expand Down Expand Up @@ -48,11 +43,6 @@
Try it now
</a>
</li>
<li class="nav-item">
<a class="nav-link" href="#why-dotty">
FAQ
</a>
</li>
<li class="nav-item">
<a class="nav-link" href="{{ site.baseurl }}/blog/index.html">
Blog
Expand Down
1 change: 0 additions & 1 deletion docs/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,5 +14,4 @@
{% include logo-page.html %}
{% include getting-started.html %}
{% include features.html %}
{% include faq.html %}
</div>