fix urls and prepare to renam the repo

Author: malaskowski

README.md

@@ -1,11 +1,11 @@
 # Knot.x Fragments
 This repository contains all modules that are the core of the Knot.x Fragments processing.
 
-[**Fragments**](https://github.com/Knotx/knotx-fragments-handler/tree/master/api#knotx-fragment-api) 
+[**Fragments**](https://github.com/Knotx/knotx-fragments/tree/master/api#knotx-fragment-api) 
 are the result of breaking the request into smaller, independent parts by the
-[Fragments Supplier](https://github.com/Knotx/knotx-fragments-handler/tree/master/supplier)
+[Fragments Supplier](https://github.com/Knotx/knotx-fragments/tree/master/supplier)
 
-![Node with exits](https://github.com/Knotx/knotx-fragments-handler/raw/master/assets/images/case.png)
+![Node with exits](https://github.com/Knotx/knotx-fragments/raw/master/assets/images/case.png)
 
 ## How does it work
 
@@ -15,38 +15,38 @@ Each **Action** transforms the Fragment's content and/or updates its payload.
 
 Fragment's path in the Task graph is defined by Action's output, called **Transition**.
 
-<img src="https://github.com/Knotx/knotx-fragments-handler/raw/master/assets/images/graph_processing.png" width="700">
+<img src="https://github.com/Knotx/knotx-fragments/raw/master/assets/images/graph_processing.png" width="700">
 
-You may read more about it in the [Handler API docs](https://github.com/Knotx/knotx-fragments-handler/tree/master/handler/api).
+You may read more about it in the [Handler API docs](https://github.com/Knotx/knotx-fragments/tree/master/handler/api).
 
 ---
 
 **Action** is a simple function (business logic) with possible restrictions imposed. E.g. function execution
 can be limited to a certain amount of time. If it will not end in that time, Action times out. 
 In that case, Action's output is **error Transition** and some **fallback Action** may be applied.
 
-<img src="https://github.com/Knotx/knotx-fragments-handler/raw/master/assets/images/graph_processing_failure.png" width="500">
+<img src="https://github.com/Knotx/knotx-fragments/raw/master/assets/images/graph_processing_failure.png" width="500">
 
 Additionally, **Actions** may be composed into a **Composed Structure** that will be executed in parallel when they
 are independent.
 
 You may read more about actions restrictions and implementations of Actions delivered with this 
-module in the [Handler Core docs](https://github.com/Knotx/knotx-fragments-handler/tree/master/handler/core)
+module in the [Handler Core docs](https://github.com/Knotx/knotx-fragments/tree/master/handler/core)
 
 ---
 
 ### Fragments Engine
 The diagram below depicts Fragments Engine logic (map-reduce).
 
-![Node with exits](https://github.com/Knotx/knotx-fragments-handler/raw/master/assets/images/all_in_one_processing.png)
+![Node with exits](https://github.com/Knotx/knotx-fragments/raw/master/assets/images/all_in_one_processing.png)
 
-Read more about it [here](https://github.com/Knotx/knotx-fragments-handler/tree/master/handler/engine).
+Read more about it [here](https://github.com/Knotx/knotx-fragments/tree/master/handler/engine).
 
 ---
 
 ### Fragments assembler
 Finally, after all the Fragments were processed, they are combined into a single response by the 
-[Fragments Assembler](https://github.com/Knotx/knotx-fragments-handler/tree/master/assembler) handler.
+[Fragments Assembler](https://github.com/Knotx/knotx-fragments/tree/master/assembler) handler.
 
 ## License
 **Knot.x Fragments** is licensed under the [Apache License, Version 2.0 (the "License")](https://www.apache.org/licenses/LICENSE-2.0.txt)

assembler/README.md

@@ -1,6 +1,6 @@
 # Knot.x Fragments Assembler
 This module contains [Handler](https://vertx.io/docs/apidocs/io/vertx/core/Handler.html)
-that joins all [`Fragments`](https://github.com/Knotx/knotx-fragments-handler/tree/master/api) and
+that joins all [`Fragments`](https://github.com/Knotx/knotx-fragments/tree/master/api) and
 saves the result into the [`ClientResponse`](https://github.com/Knotx/knotx-server-http/blob/master/api/docs/asciidoc/dataobjects.adoc#clientresponse) body.
 
 ## How does it work?

gradle.properties

@@ -1,2 +1,2 @@
 version=2.0.0-SNAPSHOT
-publication.scm=scm:git:git://github.com/Knotx/knotx-fragments-handler.git
+publication.scm=scm:git:git://github.com/Knotx/knotx-fragments.git

handler/api/README.md

@@ -1,9 +1,9 @@
 # Fragments Handler API
 
 ## Action
-**Action** is a simple function that operates on a [Fragment](https://github.com/Knotx/knotx-fragments-handler/tree/master/api#knotx-fragment-api) 
-(which is part of a [`FragmentContext`](https://github.com/Knotx/knotx-fragments-handler/blob/master/api/docs/asciidoc/dataobjects.adoc#FragmentContext)).
-The result of applying Action logic is the [`FragmentResult`](https://github.com/Knotx/knotx-fragments-handler/blob/master/api/docs/asciidoc/dataobjects.adoc#FragmentResult)
+**Action** is a simple function that operates on a [Fragment](https://github.com/Knotx/knotx-fragments/tree/master/api#knotx-fragment-api) 
+(which is part of a [`FragmentContext`](https://github.com/Knotx/knotx-fragments/blob/master/handler/api/docs/asciidoc/dataobjects.adoc#FragmentContext)).
+The result of applying Action logic is the [`FragmentResult`](https://github.com/Knotx/knotx-fragments/blob/master/handler/api/docs/asciidoc/dataobjects.adoc#FragmentResult)
 which contains the new Fragment and a Transition (which determines an edge in the processing graph).
 
 In other words, you should understand applying an Action as performing the function:
@@ -15,4 +15,4 @@ In other words, you should understand applying an Action as performing the funct
 ## Knot
 **Knot** is a scalable **Action** that is available on the [Vert.x Event Bus](https://vertx.io/docs/vertx-core/java/#event_bus).
 
-Read more about the API Data Objects in the [Data Object docs](https://github.com/Knotx/knotx-fragments-handler/blob/master/api/docs/asciidoc/dataobjects.adoc).
+Read more about the API Data Objects in the [Data Object docs](https://github.com/Knotx/knotx-fragments/blob/master/handler/api/docs/asciidoc/dataobjects.adoc).

handler/core/README.md

@@ -67,7 +67,7 @@ actions {
 }
 ```
 
-Read more about configuring fragment graph in the [Data Object docs](https://github.com/Knotx/knotx-fragments-handler/blob/master/core/docs/asciidoc/dataobjects.adoc).
+Read more about configuring fragment graph in the [Data Object docs](https://github.com/Knotx/knotx-fragments/blob/master/handler/core/docs/asciidoc/dataobjects.adoc).
 
 ## Actions
 

handler/engine/README.md

@@ -1,7 +1,7 @@
 # Fragments Engine
 This module is a heart of the *Fragment Processing*. It actually does the work of independent 
 [**Fragments**](https://github.com/Knotx/knotx-fragments/tree/master/api) processing,
-by routing each *Fragment* throught the graph and applying [**Actions**](https://github.com/Knotx/knotx-fragments-handler/tree/master/api#action)
+by routing each *Fragment* throught the graph and applying [**Actions**](https://github.com/Knotx/knotx-fragments/tree/master/handler/api#action)
  during that processing.
 
 ## Graph Engine
@@ -10,7 +10,7 @@ A **Task** specifies the nodes through which Fragments will be routed by the Gra
 Each Node may define possible *outgoing edges* - **Transitions**.
 
 Additionally, a **Node** can do one of the following:
-  - define an [**Action**](https://github.com/Knotx/knotx-fragments-handler/tree/master/api#action) 
+  - define an [**Action**](https://github.com/Knotx/knotx-fragments/tree/master/handler/api#action) 
   that will be applied to *Fragment* (we call it **Action Node**),
   - consist of other **Nodes** (we call it **Composite Node**).
 
@@ -58,23 +58,23 @@ The images below illustrates the above rules.
 
 * *Node A* and *Node B* ends correctly:
 
-![Node with exits](../assets/images/a_next_b.png)
+![Node with exits](assets/images/a_next_b.png)
 
 * *Node A* raises an exception, *Node B* ends correctly 
 
-![Node with exits](../assets/images/a_error_c.png)
+![Node with exits](assets/images/a_error_c.png)
 
 `FAILURE` states:
 
 * *Node A* ends correctly and *Node B* raises exception:
 
-![Node with exits](../assets/images/a_next_b_error.png)
+![Node with exits](assets/images/a_next_b_error.png)
 
 * *Node A* and *Node C* raises exceptions:
 
-![Node with exits](../assets/images/a_error_c_error.png)
+![Node with exits](assets/images/a_error_c_error.png)
 
 A node can also declare its own exits (transitions) but then we need to configure them in a graph. 
 Otherwise, if the custom transition is set but is not declared, then the `FAILURE` status is returned:
 
-![Node with exits](../assets/images/a_custom.png)
+![Node with exits](assets/images/a_custom.png)

settings.gradle.kts

@@ -22,7 +22,7 @@ pluginManagement {
     }
 }
 
-rootProject.name = "knotx-fragments-handler"
+rootProject.name = "knotx-fragments"
 
 // API
 include("knotx-fragments-api")

supplier/README.md

@@ -1,6 +1,6 @@
 # Fragments Supplier
 Suppliers are [**Handlers**](https://github.com/Knotx/knotx-server-http/tree/master/api#routing-handlers)
-that break the request into smaller pieces, called [**Fragments**](https://github.com/Knotx/knotx-fragments-handler/tree/master/api#knotx-fragment-api),
+that break the request into smaller pieces, called [**Fragments**](https://github.com/Knotx/knotx-fragments/tree/master/handler/api#knotx-fragment-api),
 during the [HTTP Server request processing](https://github.com/Knotx/knotx-server-http#how-does-it-work).
 
 You may read more about any of the implementations inside the module's `README.md` docs.

supplier/html-splitter/README.md

@@ -1,6 +1,6 @@
 # Knot.x Splitter Handler
 This module contains [Handler](https://vertx.io/docs/apidocs/io/vertx/core/Handler.html)
-implementation that splits a Template into [`Fragments`](https://github.com/Knotx/knotx-fragments-handler/tree/master/api).
+implementation that splits a Template into [`Fragments`](https://github.com/Knotx/knotx-fragments/tree/master/api).
 
 Template is a document that will be later processed by Knot.x instance. Current implementation (`HtmlFragmentSplitter`)
 supports splitting HTML markup, but Template could be any document like PDF file, Office file or even an image.