Removing Patterns from Features page

Change-Id: I989f5578af09ab39f492092dd1d89cc9b1e93715
Signed-off-by: Florian Barbin <florian.barbin@obeo.fr>
diff --git a/features.html b/features.html
index ea0bff2..208e0e6 100644
--- a/features.html
+++ b/features.html
@@ -14,7 +14,7 @@
         ================================================== -->
         <meta name="format-detection" content="telephone=no">
         <meta name="viewport" content="width=device-width, initial-scale=1">
-        
+
         <!-- Template CSS Files
         ================================================== -->
         <!-- Twitter Bootstrs CSS -->
@@ -27,13 +27,13 @@
         <!-- responsive css -->
         <link rel="stylesheet" href="css/responsive.css">
         <link rel="stylesheet" href="css/latofonts.css">
-        
+
         <script src="https://use.fontawesome.com/b51f77a16a.js"></script>
-        
+
         <!-- Cookie content -->
         <link rel="stylesheet" type="text/css" href="//www.eclipse.org/eclipse.org-common/themes/solstice/public/stylesheets/vendor/cookieconsent/cookieconsent.min.css" />
         <script src="//www.eclipse.org/eclipse.org-common/themes/solstice/public/javascript/vendor/cookieconsent/default.min.js"></script>
-        
+
         <!-- Eclipse Foundation Google Tag Manager -->
 		<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
 		new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
@@ -41,14 +41,14 @@
 		'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
 		})(window,document,'script','dataLayer','GTM-5WLCZXC');</script>
 		<!-- End Google Tag Manager -->
-        
+
         <!-- Template Javascript Files
         ================================================== -->
 		<!-- Angular -->
 		<base href="/capella/">
 		<script src="js/angular-1.7.8.min.js"></script>
 		<script src="angular/capella.js"></script>
-	
+
         <!-- modernizr js -->
         <script src="js/vendor/modernizr-2.6.2.min.js"></script>
         <!-- jquery -->
@@ -89,7 +89,7 @@
                 </div>
             </div>
         </section><!--/#intro_banner-->
-        
+
         <!--
         ==================================================
         Main Content
@@ -114,10 +114,10 @@
 										Activities</b> to <b>Operational Entities</b>. Operational Processes
 									can be displayed as highlighted paths.
 								</p>
-								
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/OperationalArchitecture.png"><img alt="Operational Architecture" src="images/start/diagrams/OperationalArchitecture.png" width="60%">
 								</a></p>
-		
+
 								<h3>Capabilities</h3>
 								<p>
 									Capabilities diagrams are available in all Arcadia engineering
@@ -126,22 +126,22 @@
 									cases. They are illustrated by Dataflows, Functional Chains and
 									Sequence Diagrams.
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/Capabilities.png"><img alt="[MCB]" src="images/start/diagrams/Capabilities.png" width="60%">
 								</a></p>
-		
+
 								<h3>Dataflows</h3>
-								
+
 								<p>Dataflow diagrams are available in all Arcadia engineering
 									levels. They represent information dependency between functions.
 									These diagrams provide rich mechanisms to manage complexity:
 									Computed simplified links between high-level Functions,
 									categorization of Exchanges, etc. Functional Chains can be
 									displayed as highlighted paths.</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/dataflows.jpg"><img alt="Dataflows" src="images/start/diagrams/dataflows.jpg" width="60%">
 								</a></p>
-		
+
 								<h3>Architecture</h3>
 								<p>
 									Architecture diagrams are used in all Arcadia engineering phases.
@@ -151,40 +151,40 @@
 									contain one box representing the System under study plus the
 									Actors.
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/architecture_1.jpg"><img alt="Architecture" src="images/start/diagrams/architecture_1.jpg" width="60%">
 								</a></p>
-								 
+
 								<p>
 									In Logical Architecture, these diagrams show the building blocks
 									of the system. These are called <b>Logical Components</b>.
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/architecture_2.jpg"><img alt="Architecture" src="images/start/diagrams/architecture_2.jpg" width="60%">
 								</a></p>
-								 
+
 								<p>
 									In Physical Architecture, these diagrams also show the allocation
 									of <b>Behavioural Components</b> onto <b>Implementation
 										Components</b> (typically material, but not necessarily).
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/architecture_3.jpg"><img alt="Architecture" src="images/start/diagrams/architecture_3.jpg" width="60%">
 								</a></p>
-		
+
 								<h3>Trees</h3>
 								<p>
 									Tree diagrams represent breakdowns of either <b>Functions</b> or
 									<b>Components</b>. Each node can be folded / unfolded.
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/tree_1.jpg"><img alt="Trees" src="images/start/diagrams/tree_1.jpg" width="60%">
 								</a></p>
-								
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/tree_2.jpg"><img alt="Trees" src="images/start/diagrams/tree_2.jpg" width="60%">
-								</a></p>		
-		
-		
+								</a></p>
+
+
 								<h3>Sequence Diagrams</h3>
 								<p>Capella provides several kinds of sequence diagrams:
 									Functional Scenarios (lifelines are Functions), Exchange
@@ -193,28 +193,28 @@
 									Scenarios (lifelines are Components/Actors while sequence
 									messages are Interface Operations). Modes, States and Functions
 									can also be displayed on these diagrams.</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/scenario.jpg"><img alt="Sequence Diagrams" src="images/start/diagrams/scenario.jpg" width="60%">
 								</a></p>
-		
+
 								<h3>Modes and States</h3>
-								
+
 								<p>Modes and States diagrams are UML-inspired state machines.
 									Modes / States / Transitions can be related to Functions,
 									Functional Exchanges, Interface Operations, etc.</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/modesstates.jpg"><img alt="Modes and States" src="images/start/diagrams/modesstates.jpg" width="60%">
 								</a></p>
-		
+
 								<h3>Classes and Interfaces</h3>
-								
+
 								<p>Capella provides advanced mechanisms to model bit-precise
 									data structures and relate them to Functional Exchanges,
 									Component or Function Ports, Interfaces, etc.</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/classesinterfaces_1.jpg"><img alt="Classes Interfaces" src="images/start/diagrams/classesinterfaces_1.jpg" width="60%">
 								</a></p>
-								
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/start/diagrams/classesinterfaces_2.jpg"><img alt="Classes Interfaces" src="images/start/diagrams/classesinterfaces_2.jpg" width="60%">
 								</a></p>
 							</div>
@@ -232,15 +232,15 @@
 								</p>
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/overview.png"><img src="images/features/overview.png" alt="" width="60%">
 								</a></p>
-								
+
 								<h3>Semantic Colormap</h3>
 								<p>As graphical
 									representations of elements play a key role in communication,
 									Capella relies on a consistent colour scheme. This favours
 									enhanced model readability for all stakeholders (architects, V&amp;V
 									practitioners, specialty engineers, managers, etc.).</p>
-		
-								
+
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/colormap.png"><img src="images/features/colormap.png" alt="" width="60%">
 								</a></p>
 								<h3>Semantic Browser</h3>
@@ -251,8 +251,8 @@
 									preferred way to navigate in models and diagrams and to quickly
 									analyse the relationships between model elements.
 								</p>
-		
-								
+
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/semantic_browser.png"><img src="images/features/semantic_browser.png" alt="" width="60%">
 								</a></p>
 								<h3>Computed Links</h3>
@@ -266,30 +266,30 @@
 									maintaining consistency between several levels of abstraction.
 									Capella also provides tag-based mechanisms allowing the graphical
 									grouping of semantically close exchanges.
-		
+
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/complexity_0.png"><img src="images/features/complexity_0.png" alt="" width="60%">
 								</a></p>
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/complexity_1.png"><img src="images/features/complexity_1.png" alt="" width="60%">
 								</a></p>
-		
+
 								<h3>Advanced Diagram Management</h3>
-		
+
 								<p>
 									<b>Automated contextual diagrams</b>: Content is automatically
 									updated according to preselected elements and predefined semantic
 									rules  <b>Synchronization/unsynchronization of
 										diagrams</b>: Gives a fine level of control on the elements which
 									are systematically displayed or not (Ports of Functions,
-									Exchanges between Components, Properties of Classes, etc.) 
+									Exchanges between Components, Properties of Classes, etc.)
 									<b>Filters</b> help improve readability of diagrams by selecting
-									display options and automatically hiding / showing elements. 
+									display options and automatically hiding / showing elements.
 									<b>Layers</b> are means to customise the graphical rendering of
 									elements in a diagram based on different concerns (e.g.
 									speciality viewpoints).
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/filters.png"><img src="images/features/filters.png" alt="" width="60%">
 								</a></p>
 								<h3>Model Validation</h3>
@@ -300,14 +300,14 @@
 									aspects. Whenever possible, <b>quick fixes</b> provide quick and
 									automated solutions.
 								</p>
-		
-								
+
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/quickfixes.png"><img src="images/features/quickfixes.png" alt="" width="60%">
 								</a></p>
 								<h3>Semantic delete with preview</h3>
 								<p>Capella provides
 									instant impact analysis of deletions.</p>
-								
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/del_preview.png"><img src="images/features/del_preview.png" alt="" width="60%">
 								</a></p>
 								<h3>Replicable elements and libraries</h3>
@@ -320,15 +320,17 @@
 									instantiation of a REC. RECs can be packaged in libraries, which
 									can be shared between several projects.
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/rec_rpl.png"><img src="images/features/rec_rpl.png" alt="" width="60%">
 								</a></p>
+								<!--
 								<h3>Modelling Patterns</h3>
 								<p>Recurring
 									modelling schemes can be captured with patterns.</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/patterns.png"><img src="images/features/patterns.png" alt="" width="40%">
 								</a></p>
+								-->
 								<h3>Transition System/Subsystems</h3>
 								<p>
 									The <b>automated and iterative transition between system and
@@ -338,7 +340,7 @@
 									involved in co-engineering activities at system level before the
 									transition occurs.
 								</p>
-		
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/transition_system_subsystem.png"><img src="images/features/transition_system_subsystem.png" alt="" width="60%">
 								</a></p>
 								<h3>Multi-Viewpoint</h3>
@@ -349,7 +351,7 @@
 									evaluate the performance of candidate architectures according to
 									different concerns.
 								</p>
-								
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/multi_vp.png"><img src="images/features/multi_vp.png" alt="" width="60%">
 								</a></p>
 								<h3>HTML output</h3>
@@ -359,7 +361,7 @@
 									models helps <b>make models THE reference of all engineering
 										activities</b>.
 								</p>
-								
+
 								<p class="text-center"><a rel="gallery" class="fancybox" href="images/features/html.jpg"><img src="images/features/html.jpg" alt="" width="60%">
 								</a></p>
 							</div>
@@ -368,38 +370,38 @@
 								<p>
 									<b>Embedded methodological guidance</b>
 								</p>
-	
+
 								<iframe width="560" height="315" src="//www.youtube.com/embed/WtwAzftHd4A?rel=0&amp;autoplay=0&amp;loop=0&amp;wmode=opaque&amp;controls=1&amp;showinfo=0&amp;theme=light&amp;vq=hd720&amp;color=white" frameborder="0" allowfullscreen=""></iframe>
 								<p>
 									<b>Manage model complexity</b>
 								</p>
-	
+
 								<iframe width="560" height="315" src="//www.youtube.com/embed/UiOiBomTU1c?rel=0&amp;autoplay=0&amp;loop=0&amp;wmode=opaque&amp;controls=1&amp;showinfo=0&amp;theme=light&amp;vq=hd720&amp;color=white" frameborder="0" allowfullscreen=""></iframe>
 								<p>
 									<b>Browsing the model</b>
 								</p>
-	
+
 								<iframe width="560" height="315" src="//www.youtube.com/embed/HKMaGc99Zh8?rel=0&amp;autoplay=0&amp;loop=0&amp;wmode=opaque&amp;controls=1&amp;showinfo=0&amp;theme=light&amp;vq=hd720&amp;color=white" frameborder="0" allowfullscreen=""></iframe>
 								<p>
 									<b>Productivity tools</b>
 								</p>
-	
+
 								<iframe width="560" height="315" src="//www.youtube.com/embed/cT43CmZM2go?rel=0&amp;autoplay=0&amp;loop=0&amp;wmode=opaque&amp;controls=1&amp;showinfo=0&amp;theme=light&amp;vq=hd720&amp;color=white" frameborder="0" allowfullscreen=""></iframe>
 								<p>
 									<b>Multi-viewpoint trade-off analysis</b>
 								</p>
-								
+
 								<iframe width="560" height="315" src="//www.youtube.com/embed/zvIzyDxAj1c?rel=0&amp;autoplay=0&amp;loop=0&amp;wmode=opaque&amp;controls=1&amp;showinfo=0&amp;theme=light&amp;vq=hd720&amp;color=white" frameborder="0" allowfullscreen=""></iframe>
 								<p>
 									<b>Creation of viewpoint with Capella Studio 1.1.0</b>
 								</p>
-								
+
 							</div>
-					</div>	
+					</div>
                 </div>
             </div>
         </section> <!-- #how -->
-		
+
 		<div id="back-to-top" data-spy="affix" data-offset-top="100"
 			class="back-to-top hidden-xs hidden-sm affix-top">
 			<button class="btn btn-default" title="Back to Top">
@@ -414,14 +416,14 @@
 				}, 500);
 				return false;
 			});
-		</script>       
-       
+		</script>
+
         <!--
         ==================================================
         Call To Action Section Start
         ================================================== -->
 		<ng-include src="'angular/blocks/call2action.html'"></ng-include>
-       	
+
         <!--
         ==================================================
         Footer Section