GitHub user AhyoungRyu opened a pull request: https://github.com/apache/zeppelin/pull/1478
[ZEPPELIN-1514] Make atom, rss, sitemap file not to be searched ### What is this PR for? I excluded some docs pages from [search page](https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/search.html) in Zeppelin documentation site. This can be done by removing `title` value in [front matter](https://jekyllrb.com/docs/frontmatter/) as I did same for `pleasecontribute.md` in [here](https://github.com/apache/zeppelin/pull/1266/commits/6e775f5c28b80538fff1484b4eb1f66c795ca2c1). ### What type of PR is it? Bug Fix ### What is the Jira issue? [ZEPPELIN-1514](https://issues.apache.org/jira/browse/ZEPPELIN-1514) ### How should this be tested? ### Screenshots (if appropriate) The below pages shouldn't be searched <img width="861" alt="screen shot 2016-10-01 at 4 01 37 pm" src="https://cloud.githubusercontent.com/assets/10060731/19012559/80339cbe-87f4-11e6-8ee5-59405c048171.png"> <img width="539" alt="screen shot 2016-10-01 at 4 08 03 pm" src="https://cloud.githubusercontent.com/assets/10060731/19012560/82f32f3c-87f4-11e6-9c25-0f22eb723245.png"> <img width="558" alt="screen shot 2016-10-01 at 4 08 11 pm" src="https://cloud.githubusercontent.com/assets/10060731/19012561/8780398c-87f4-11e6-8446-39f0f8f8c994.png"> ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/AhyoungRyu/zeppelin fix/excludeNonDocs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1478.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1478 ---- commit da1eb845480cc2c691604885dd94eac7f49f037d Author: AhyoungRyu <ahyoung...@apache.org> Date: 2016-10-01T07:07:42Z Make atom, rss, sitemap file not to be searched ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---