Skip to content

Commit 23d7504

Browse files
authored
Fixed banner location causing antora to create an invalid page title (#989)
1 parent 07dc37e commit 23d7504

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

53 files changed

+104
-99
lines changed

docs/modules/ROOT/pages/developer-guide/adding-visualizations.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
include::../banner.adoc[]
2-
31
= Adding Visualizations
42

3+
include::../banner.adoc[]
4+
55
You can extend NeoDash with your own visualizations without diving deep
66
into the core application. Likewise, adding a new customization to an
77
existing report requires minimal changes.

docs/modules/ROOT/pages/developer-guide/build-and-run.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
include::../banner.adoc[]
2-
31
= Build & Run
42

3+
include::../banner.adoc[]
4+
55
To start developing the application, you will need to set up the
66
development environment.
77

docs/modules/ROOT/pages/developer-guide/component-overview.adoc

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
1-
include::../banner.adoc[]
2-
31
= Component Overview
42

3+
include::../banner.adoc[]
54

65
The image below contains a high-level overview of the component
76
hierarchy within the application. The following conceptual building

docs/modules/ROOT/pages/developer-guide/configuration.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
include::../banner.adoc[]
2-
31
= Configuration
42

3+
include::../banner.adoc[]
4+
55
When using a custom NeoDash deployment, there are several settings that
66
can be configured. These mostly relate to
77
link:../standalone-mode[Standalone Mode] and SSO configurations.

docs/modules/ROOT/pages/developer-guide/contributing.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
include::../banner.adoc[]
2-
31
= Contributing
42

3+
include::../banner.adoc[]
4+
55
Contributions to the project are highly welcomed. Please consider
66
creating a https://github.com/neo4j-labs/neodash/pulls[Pull Request].
77
Ensure you start from the `develop` branch, and set the merge base to

docs/modules/ROOT/pages/developer-guide/deploy-a-build.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
1+
= Deploy a Build
2+
13
include::../banner.adoc[]
24

3-
= Deploy a Build
45
If you have a pre-built NeoDash application, you can easily deploy it on an any webserver.
56
A NeoDash build is "just" a collection of HTML, CSS and JavaScript files, so it can run virtually anywhere.
67

docs/modules/ROOT/pages/developer-guide/design.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
1+
= Design
2+
13
include::../banner.adoc[]
24

3-
= Design
45

56
This page contains some key guidelines for design of the application.
67
This entails code architecture, as well as UX/UI design.

docs/modules/ROOT/pages/developer-guide/index.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
1+
= Developer Guide
2+
13
include::../banner.adoc[]
24

3-
= Developer Guide
45

56
This guide contains information for developers looking to deploy NeoDash, or extend it for their own needs.
67

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
include::../banner.adoc[]
2-
31
= Session Storage
42

3+
include::../banner.adoc[]
4+
55
This reducer serves only to store data that we want to reset at each new session.
66
To connect to it, just define a key and use the predefined actions to set a new pair (key,value) inside of it.
77
Inside the actions there is also an action to delete all the keys that match a precise prefix, it can be useful, for example, to wipe the sessionStorage state for a certain extension, if it stores the data inside the sessionStorage using a prefix (for example look at the query-translator extension at getSessionStorageHistoryKey).

docs/modules/ROOT/pages/developer-guide/standalone-mode.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
include::../banner.adoc[]
2-
31
= Standalone Mode
42

3+
include::../banner.adoc[]
4+
55
Next to being a dashboard editor, NeoDash can be deployed in a
66
`standalone mode' - allowing you set up a architecture to publish and
77
read dashboards.

0 commit comments

Comments
 (0)