diff --git a/404.html b/404.html
index bf087a4..bd7e6e9 100644
--- a/404.html
+++ b/404.html
@@ -197,6 +197,10 @@
   <p>Maybe you want one of these?</p>
   
   <ul>
+    <li><a href="https://polarsys.org/time4sys/">Polarsys Time4Sys</a><span class="lead">(Wed, Nov 28, 2018)</span></li>
+  </ul>
+  
+  <ul>
     <li><a href="https://polarsys.org/time4sys/about/">About</a><span class="lead">(Fri, Nov 17, 2017)</span></li>
   </ul>
   
@@ -213,10 +217,6 @@
   </ul>
   
   <ul>
-    <li><a href="https://polarsys.org/time4sys/">Polarsys Time4Sys</a><span class="lead">(Fri, Nov 17, 2017)</span></li>
-  </ul>
-  
-  <ul>
     <li><a href="https://polarsys.org/time4sys/videos/">Videos</a><span class="lead">(Fri, Nov 17, 2017)</span></li>
   </ul>
   
@@ -241,7 +241,7 @@
   </ul>
   
   <ul>
-    <li><a href="https://polarsys.org/time4sys/">Time4Sys</a><span class="lead">(Fri, Nov 17, 2017)</span></li>
+    <li><a href="https://polarsys.org/time4sys/">Time4Sys</a><span class="lead">(Wed, Nov 28, 2018)</span></li>
   </ul>
   
 </div>
diff --git a/downloads/index.html b/downloads/index.html
index 5644b21..be44a01 100644
--- a/downloads/index.html
+++ b/downloads/index.html
@@ -203,10 +203,28 @@
 
 <hr />
 
-<h3 id="current-release-version-2017-03-0">Current Release (version - 2017-03-0)</h3>
+<h3 id="current-release-version-2018-01-25">Current Release (version - 2018-01-25)</h3>
+
+<p>Version 1.0.0</p>
 
 <h5 id="products">Products</h5>
 
+<p><a href="https://download.polarsys.org/time4sys/stable/v0.8.0/products/?d">https://download.polarsys.org/time4sys/stable/v0.8.0/products/?d</a></p>
+
+<h5 id="update-site">Update Site</h5>
+
+<p><a href="https://download.polarsys.org/time4sys/stable/v0.8.0/updateSite/">https://download.polarsys.org/time4sys/stable/v0.8.0/updateSite/</a></p>
+
+<p>Version 0.8.0</p>
+
+<h5 id="products-1">Products</h5>
+
+<p><a href="https://download.polarsys.org/time4sys/stable/v0.8.0/products/?d">https://download.polarsys.org/time4sys/stable/v0.8.0/products/?d</a></p>
+
+<h5 id="update-site-1">Update Site</h5>
+
+<p><a href="https://download.polarsys.org/time4sys/stable/v0.8.0/updateSite/">https://download.polarsys.org/time4sys/stable/v0.8.0/updateSite/</a></p>
+
 <ul>
 <li>Time4Sys - version for <strong>Windows (64 Bit)</strong> - [[Zip-archive]()(317.7 MB)</li>
 </ul>
diff --git a/images/MARTE_foundations.png b/images/MARTE_foundations.png
new file mode 100644
index 0000000..c96ab5f
--- /dev/null
+++ b/images/MARTE_foundations.png
Binary files differ
diff --git a/images/MARTE_logo.png b/images/MARTE_logo.png
new file mode 100644
index 0000000..bbcb5cb
--- /dev/null
+++ b/images/MARTE_logo.png
Binary files differ
diff --git a/images/OMG_logo.png b/images/OMG_logo.png
new file mode 100644
index 0000000..290d988
--- /dev/null
+++ b/images/OMG_logo.png
Binary files differ
diff --git a/index.html b/index.html
index 0058db1..8cee4e5 100644
--- a/index.html
+++ b/index.html
@@ -259,6 +259,36 @@
 
 <p>Note: The MARTE meta-model can be downloaded as a separate and independent package. Time4sys aims to be the official repository for the MARTE meta-model.</p>
 
+<h2 id="marte">MARTE</h2>
+
+<p>
+<img src="images/MARTE_logo.png" class="img-responsive"> <img src="images/OMG_logo.png" class="img-responsive">
+<br />
+</p>
+
+<p>MARTE (Modeling and Analysis of Real-Time and Embedded systems) is a standard defined at <a href="https://www.omg.org">OMG</a>. You can find also the fill specification of this standard at the <a href="https://www.omg.org/omgmarte/">official MARTE website</a>.</p>
+
+<p>MARTE consists in defining foundations for model-based description of real time and embedded systems. These core concepts are then refined for both modeling and analyzing concerns. Modeling parts provides support required from specification to detailed design of real-time and embedded characteristics of systems. MARTE concerns also model-based analysis. In this sense, the intent is not to define new techniques for analyzing real-time and embedded systems, but to support them. Hence, it provides facilities to annotate models with information required to perform specific analysis. Especially, MARTE focuses on performance and schedulability analysis. But, it defines also a general framework for quantitative analysis which intends to refine/specialize any other kind of analysis.</p>
+
+<p>Among others, the benefits of using this MARTE language are thus:</p>
+
+<ul>
+<li>Providing a common way of modeling both hardware and software aspects of a RTES in order to improve communication between developers.</li>
+<li>Enabling interoperability between development tools used for specification, design, verification, code generation, etc.</li>
+<li>Fostering the construction of models that may be used to make quantitative predictions regarding real-time and embedded features of systems taking into account both hardware and software characteristics.</li>
+</ul>
+
+<p>The MARTE language is structured around two concerns, one to model the features of real-time and embedded systems and the other to annotate application models so as to support analysis of system properties. These are shown by the MARTE design model package in following figure, and the MARTE analysis model package, respectively. These two major parts share common concerns with describing time and the use of concurrent resources, which are contained in the shared package called MARTE foundations. A fourth package contains the annexes profiles defined in MARTE, as well as a predefined model libraries that may used by modelers to denotes their real-time and embedded applications.</p>
+
+<p>
+<img src="images/MARTE_foundations.png" class="img-responsive">
+<br />
+</p>
+
+<p>Architecture of the MARTE language (<strong>NFPs</strong> = Non-Functional Properties, <strong>GRM</strong> = Generic Resource Modeling, <strong>GCM</strong> = Generic Component Model, <strong>Alloc</strong> = Allocation modeling, <strong>RTEMoCC</strong> = RTE Model of Computation &amp; Communication, <strong>SRM</strong> = Software Resource Modeling, <strong>HRM</strong> = Hardware Resource Modeling, <strong>GQAM</strong> = Generic Quantitative Analysis Modeling, <strong>SAM</strong> = Schedulability Analysis Modeling, <strong>PAM</strong> = Performance Analysis Modeling, <strong>VSL</strong> = Value Specification Language, <strong>RSM</strong> = Repetitive Structure Modelling)</p>
+
+<p>The Time4sys platform is totally based on this MARTE standard language. Time4Sys provides the first open-source implementation of the MARTE metamodel with its <a href="https://github.com/polarsys/time4sys/tree/master/Time4Sys/plugins/org.polarsys.time4sys.marte/model">ecore model</a> and java api.</p>
+
 <h3 id="references">REFERENCES</h3>
 
 <p>[1] MAST, Modeling and analysis suite for real-time applications, <a href="http://mast.unican.es/">http://mast.unican.es/</a></p>
@@ -281,6 +311,41 @@
 
 <p>[10] CAPELLA: a model-based system engineering tool and methodology, <a href="https://polarsys.org/capella/">https://polarsys.org/capella/</a></p>
 
+<p>[11] ecore model of MARTE, <a href="https://github.com/polarsys/time4sys/tree/master/Time4Sys/plugins/org.polarsys.time4sys.marte/model">https://github.com/polarsys/time4sys/tree/master/Time4Sys/plugins/org.polarsys.time4sys.marte/model</a></p>
+
+<hr />
+
+<h3 id="publications">Publications</h3>
+
+<ul>
+<li>« Probabilistic Schedulability Analysis for Fixed Priority Mixed Criticality Real-Time Systems », by Dorin Maxim, Yasmina Abdeddaim, at DATE 2016.</li>
+<li>« Schedulability analysis of dependent probabilistic real-time tasks », by S. B. Amor, D. Maxim, L. Cucu-Grosjean, at RTNS 2016.</li>
+<li>« Periodicity of real-time schedules for dependent periodic tasks on identical multiprocessor platforms », by J. Goossens, E. Grolleau, Liliana Cucu-Grosjean, at Real-Time Systems 2016.</li>
+<li>« A review of priority assignment in real-time systems », by R. Davis, L. Cucu-Grosjean, M. Bertogna, A. Burns, at Journal of Systems Architecture 2016.</li>
+<li>« Average Probabilistic Response Time Analysis of Tasks with Multiple Probabilistic Parameters », by Antoine Bertout, Dorin Maxim, Liliana Cucu-Grosjean, at Wip (RTSS) 2016.</li>
+<li>« Analysis and Simulation Tools for Probabilistic Real-Time Systems », by Dorin Maxim, Antoine Bertout, at WATERS 2016.</li>
+<li>« Probabilistic Analysis for Mixed Criticality Systems using Fixed Priority Preemptive Scheduling », by D. Maxim, R. Davis, L. Cucu-Grosjean, A. Easwaran, at RTNS 2017.</li>
+<li>« Bridging the gap between practical cases and temporal performance analysis: a models repository-based approach », by A. Long, Y. Ouhammou, E. Grolleau, L. Fejoz, L. Rioux, at RTNS 2017.</li>
+<li>« PARAD Repository: On the Capitalization of Performance Analysis Process for AADL Designs », by TD Nguyen, Y. Ouhammou, E. Grolleau, at ECSA 2017.</li>
+<li>« Leveraging Real-Time Network Analyses by Extending a Model-based Framework », by A. Bui Long, Y. Ouhammou, E. Grolleau, at AICCSA 2017.</li>
+<li>« Open Challenges for Probabilistic Measurement-Based Worst-Case Execution Time », by S. Gil, I. Bate, G. Lima, L. Santinelli, A. Gogonel, L. Cucu-Grosjean, at Embedded Systems Letters 2017.</li>
+<li>« Towards statistical estimation of worst case inter-core communications », by A Revuz, L Cucu-Grosjean, at JW 2017.</li>
+<li>« Time4Sys in a Nutshell », by Y. Ouhammou, L Fejoz, at WATERS 2017.</li>
+</ul>
+
+<h3 id="invited-talks">Invited talks</h3>
+
+<ul>
+<li>« Probabilistic Approaches for Time Critical Embedded Systems », by L Cucu-Grosjean, at VECOS 2015.</li>
+<li>« Un retour d&rsquo;expérience de Capella en enseignement », by E. Grolleau, at journée NEPTUNE 2017.</li>
+</ul>
+
+<h3 id="talks">Talks</h3>
+
+<ul>
+<li>« Waruna: break the walls integrate temporal performance verification for your engineering practices », all partners of the Waruna project, at MODELS 2016.</li>
+</ul>
+
 		
 	</div>
 	<div class="col-sm-8">
diff --git a/index.xml b/index.xml
index 262fb17..f8f276a 100644
--- a/index.xml
+++ b/index.xml
@@ -6,12 +6,21 @@
     <description>Recent content on Time4Sys</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en-us</language>
-    <lastBuildDate>Fri, 17 Nov 2017 00:00:00 +0000</lastBuildDate>
+    <lastBuildDate>Wed, 28 Nov 2018 00:00:00 +0000</lastBuildDate>
     
 	<atom:link href="https://polarsys.org/time4sys/index.xml" rel="self" type="application/rss+xml" />
     
     
     <item>
+      <title>Polarsys Time4Sys</title>
+      <link>https://polarsys.org/time4sys/</link>
+      <pubDate>Wed, 28 Nov 2018 00:00:00 +0000</pubDate>
+      
+      <guid>https://polarsys.org/time4sys/</guid>
+      <description>Context Usually, the industrial practices rely on the subjective judgment of experienced software architects and developers to predict how design decisions may impact the timing behavior of real-time embedded systems. This is however risky since eventual timing errors are only detected after implementation and integration, when the software execution can be tested on system level, under realistic conditions. At this stage, timing errors may be very costly and time consuming to correct.</description>
+    </item>
+    
+    <item>
       <title>About</title>
       <link>https://polarsys.org/time4sys/about/</link>
       <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
@@ -52,16 +61,13 @@
       <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
       
       <guid>https://polarsys.org/time4sys/downloads/</guid>
-      <description> Current Release (version - 2017-03-0) Products  Time4Sys - version for Windows (64 Bit) - [[Zip-archive]()(317.7 MB)  </description>
-    </item>
-    
-    <item>
-      <title>Polarsys Time4Sys</title>
-      <link>https://polarsys.org/time4sys/</link>
-      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
-      
-      <guid>https://polarsys.org/time4sys/</guid>
-      <description>Context Usually, the industrial practices rely on the subjective judgment of experienced software architects and developers to predict how design decisions may impact the timing behavior of real-time embedded systems. This is however risky since eventual timing errors are only detected after implementation and integration, when the software execution can be tested on system level, under realistic conditions. At this stage, timing errors may be very costly and time consuming to correct.</description>
+      <description> Current Release (version - 2018-01-25) Version 1.0.0
+Products https://download.polarsys.org/time4sys/stable/v0.8.0/products/?d
+Update Site https://download.polarsys.org/time4sys/stable/v0.8.0/updateSite/
+Version 0.8.0
+Products https://download.polarsys.org/time4sys/stable/v0.8.0/products/?d
+Update Site https://download.polarsys.org/time4sys/stable/v0.8.0/updateSite/
+ Time4Sys - version for Windows (64 Bit) - [[Zip-archive]()(317.7 MB)  </description>
     </item>
     
     <item>
diff --git a/sitemap.xml b/sitemap.xml
index 27a8414..720d9dd 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3,6 +3,11 @@
   xmlns:xhtml="http://www.w3.org/1999/xhtml">
   
   <url>
+    <loc>https://polarsys.org/time4sys/</loc>
+    <lastmod>2018-11-28T00:00:00+00:00</lastmod>
+  </url>
+  
+  <url>
     <loc>https://polarsys.org/time4sys/about/</loc>
     <lastmod>2017-11-17T00:00:00+00:00</lastmod>
   </url>
@@ -23,11 +28,6 @@
   </url>
   
   <url>
-    <loc>https://polarsys.org/time4sys/</loc>
-    <lastmod>2017-11-17T00:00:00+00:00</lastmod>
-  </url>
-  
-  <url>
     <loc>https://polarsys.org/time4sys/videos/</loc>
     <lastmod>2017-11-17T00:00:00+00:00</lastmod>
   </url>
@@ -60,7 +60,7 @@
   
   <url>
     <loc>https://polarsys.org/time4sys/</loc>
-    <lastmod>2017-11-17T00:00:00+00:00</lastmod>
+    <lastmod>2018-11-28T00:00:00+00:00</lastmod>
     <priority>0</priority>
   </url>