From e4535b759bb411d20b51645aa7ce26a9df11e270 Mon Sep 17 00:00:00 2001 From: marthanda93 Date: Fri, 1 Mar 2019 15:58:29 +0530 Subject: [PATCH] Update README.markdown --- README.markdown | 7 ------- 1 file changed, 7 deletions(-) diff --git a/README.markdown b/README.markdown index 96afe56b4..40680c9e7 100644 --- a/README.markdown +++ b/README.markdown @@ -1,10 +1,3 @@ -# Introduction - -Spring's project pages are based on [Jekyll](http://jekyllrb.com) and [GitHub Pages](http://pages.github.com/). This means that each project's website is stored within the project repo, in a special branch called "gh-pages". In order to keep everything looking similar across the many individual Spring projects, common elements of the Jekyll site layout, css, etc are stored in [a shared gh-pages repository](http://github.com/spring-projects/gh-pages). If you're seeing this README in the gh-pages branch of an actual Spring project, that's because this file, along with all the other common files get merged periodically into each project. - -This approach may sound a little funky (and it is), but it's way better than the misery of Git submodules. In fact, it's actually pretty easy. If you're just getting started, then follow the directions immediately below. If you're needing a refresher on how to keep things up to date, then head to the section at the bottom on "keeping up to date". - -> ***Note:*** Github changed their rendering (a lot) in April 2016. If you are seeing pages build failures since that time, then you probably need to merge some changes from this upstream. Follow the instructions below, and for testing locally use rubiy 2.x and don't forget to `bundle exec ...` everything.