diff --git a/introduction/introduction.md b/introduction/introduction.md
index 815fd48d..160a94a9 100644
--- a/introduction/introduction.md
+++ b/introduction/introduction.md
@@ -1,5 +1,5 @@
 <!---
-   Copyright 2017 Ericsson AB.
+   Copyright 2017-2019 Ericsson AB and others.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");
@@ -44,10 +44,10 @@ The Eiffel vocabulary can be adopted incrementally - which events you use is up
 
 There are several valid out-of-the-box solutions for event transport and routing infrastructure, depending on your needs and preferences. Examples include [RabbitMQ](https://www.rabbitmq.com/), [Kafka](http://kafka.apache.org/), [NATS](http://nats.io/) and more. When choosing infrastructure, it is important to understand the implications of the different types of guarantees these solutions can offer. While some provide durable queues and delivery guarantees, others do not, but instead offer higher performance. It is important to consider one's requirements and choose the appropriate solution for event transport and routing accordingly; to maximize reliability and traceability capabilities, it is generally recommended to choose a solution with durable queues and delivery guarantees.
 
-Services for Eiffel event handling address a multitude of needs. These services range from very simplistic to highly complex, and just like the Eiffel vocabulary one is free to pick and choose what suits the particular case. The documentation in this repository links such services as they become available, addressing e.g. [event dispatch](../implementations/event-dispatch.md) and [event aggregation and analysis](../implementations/event-aggregation-and-analysis.md).
+Services for Eiffel event handling address a multitude of needs. These services range from very simplistic to highly complex, and just like the Eiffel vocabulary one is free to pick and choose what suits the particular case. The documentation in this repository links such services as they become available, addressing e.g. [event dispatch](https://eiffel-community.github.io/eiffel-sepia/event-publishing.html) and [event aggregation and analysis](https://eiffel-community.github.io/eiffel-sepia/event-analysis.html).
 
 ## How is Eiffel Technology Agnostic?
-Eiffel provides a communication protocol geared towards machine-to-machine continuous integration and delivery communication; it makes no assumptions with regards to underlying infrastructure (though widely used messaging solutions are recommended, as discussed above) or choice of continuous integration servers, test frameworks, source code management systems or other tooling. As long as the tools you use can be plugged into or configured to access services for event [dispatch](../implementations/event-dispatch.md) or [analysis](../implementations/event-aggregation-and-analysis.md), you're good to go.
+Eiffel provides a communication protocol geared towards machine-to-machine continuous integration and delivery communication; it makes no assumptions with regards to underlying infrastructure (though widely used messaging solutions are recommended, as discussed above) or choice of continuous integration servers, test frameworks, source code management systems or other tooling. As long as the tools you use can be plugged into or configured to access services for event [dispatch](https://eiffel-community.github.io/eiffel-sepia/event-publishing.html) or [analysis](https://eiffel-community.github.io/eiffel-sepia/event-analysis.html), you're good to go.
 
 ## How Does Eiffel Achieve Scalability?
 Eiffel is not a centralized or monolithic tool. Instead it represents a decentralized and federated approach to driving and documenting enterprise scale continuous integration and delivery systems. By broadcasting events globally and allowing any tool or service to react as it sees fit to those events several important goals are achieved:
@@ -76,4 +76,4 @@ Eiffel builds upon this principle. Think of Eiffel events as proxies or handles
 ## How Do I Make Sense of Events?
 A single Eiffel event only tells a fragment of the story. To derive real value, it must be analyzed together with the many other events it references. This is both a strength and a weakness: a strength because it affords separation of concerns and a tight, standardized syntax; a weakness because it makes it difficult to react intelligently to just the one event.
 
-As a consequence, effective analysis of Eiffel events requires supporting implementations. A minimum requirement is some form of [persistence](../implementations/event-persistence.md), allowing users to analyze not just current events, but to dig into the historical record. True value is gained, however, when using [more intelligent services with the ability to raise the level of abstraction from raw events and present aggregated data](../implementations/event-aggregation-and-analysis.md), and [visualization solutions](../implementations/visualization.md) building on top of those aggregations.
\ No newline at end of file
+As a consequence, effective analysis of Eiffel events requires supporting implementations. A minimum requirement is some form of [persistence](https://eiffel-community.github.io/eiffel-sepia/event-persistence.html), allowing users to analyze not just current events, but to dig into the historical record. True value is gained, however, when using [more intelligent services with the ability to raise the level of abstraction from raw events and present aggregated data](https://eiffel-community.github.io/eiffel-sepia/event-analysis.html), and [visualization solutions](https://eiffel-community.github.io/eiffel-sepia/event-presentation.html) building on top of those aggregations.