-
-# Working with the Glossary Author user interface.
-
-Note the screenshots might be slightly out of date with the code base, but hopefully help orientate the reader.
-
-## Getting to the Glossary Author start screen
-- After logging into the Egeria react UI, you will see tasks at the left hand side of the user interface including the glossary author task.
-
-- If you see a screen with a connect button like this 
then the glossary author is not able to issue a successfully glossary call; this is caused by either
- - the Subject Area OMAS is not active, so the glossary author cannot call it
- - the glossary author view is not configured on the view server.
- - the presentation server is not configured to point to the glossary server view service.
- If everythign is correctly configured but the view server or its downstream server is not started then, start them and press the connect button.
-- Assuming you have successfully connected, then you are now in a position to author glossary content and should see
-
-- You will notice that you can choose the node to work with using the node tabs
-
-
-## Add a glossary
-- Add a node on a tab using the  add button. Pressing add for glossary will show
- <img src=)
. The minimal input is a name.
-pressing create will show a screen like :
- 
-
- ## Working with a glossary
-- Navigating back after having created a glossary called 'glossary1' in an empty system will show you
- 
-- 'List view' You can toggle the glossary view to show the glossaries as a list
-
-
-- 'paging' - notice the paging options, these allow you to change the page size (how many are displayed), page through the results if there is more than a page's worth to display.
-- 'filter' Entering text into the filter box 
filters the displayed results. If you want an exact match, check 
-
-## Button that appear when a node is selected
-- Note that there is a checkbox on the node card; when checked, buttons appear indicating actions you can perform against the selected node:
- - 
- this is shown for glossary, to quickly create Terms under the selected glossary
- - 
- this shows the children of the selected node.
- - 
- this displays an edit screen for the selected node
- - 
- this deletes the selected node. Glossaries with content cannot be deleted.
-
-## Quick terms
-- The quick term screen looks like this:
- 
-- Press the + button to add extra rows
- 
-- fillin the name and description in the rows
- 
-- press Create Terms on Server button to show
- 
-
-## Working with Categories and Terms
-Working with Categories and terms, is similar to working with Glossaries, apart from
- - choosing the Term or Category node tab, Terms or Categories can be created, in this case a wizard is displayed to aske the user to choose the glossary in which the term should be created. Here is the first page of the term wizard
- 
-
-## Glossary children
-When the glossary children action is chosen, the categories and terms under that glossary are displayed.
- 
-By default top categories are displayed, these are categories that do not have a parent category. If you want to see the all the categories under the glossary then toggle the Top Categories 
to All Categories 
-
-## Breadcrumb
-While navigating, a breadcrumb is created showing how deep the current node is that is being authored.
-
-
-
-## Future improvements
-- a breadcrumb to be optimized to minimize the url length.
-- Allow category hierarchies to be authored. i.e. child categories of categories
-- Allow Relationships to be authored
-- add governance classification authoring
-- add spine object views
-- add collaboration authoring and viewing
-- start with a context from the community profile.
-
-----
-License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
-Copyright Contributors to the ODPi Egeria project.
diff --git a/docs/GlossaryAuthor/Termwizard.png b/docs/GlossaryAuthor/Termwizard.png
deleted file mode 100644
index 5ade5947..00000000
Binary files a/docs/GlossaryAuthor/Termwizard.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/add.png b/docs/GlossaryAuthor/add.png
deleted file mode 100644
index d73376ff..00000000
Binary files a/docs/GlossaryAuthor/add.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/allcats.png b/docs/GlossaryAuthor/allcats.png
deleted file mode 100644
index 30bd7f2d..00000000
Binary files a/docs/GlossaryAuthor/allcats.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/children.png b/docs/GlossaryAuthor/children.png
deleted file mode 100644
index b4ab2a15..00000000
Binary files a/docs/GlossaryAuthor/children.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/connect.png b/docs/GlossaryAuthor/connect.png
deleted file mode 100644
index 15a94bb5..00000000
Binary files a/docs/GlossaryAuthor/connect.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/delete.png b/docs/GlossaryAuthor/delete.png
deleted file mode 100644
index b84fe755..00000000
Binary files a/docs/GlossaryAuthor/delete.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/edit.png b/docs/GlossaryAuthor/edit.png
deleted file mode 100644
index 094f6434..00000000
Binary files a/docs/GlossaryAuthor/edit.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/emptystartscreen.png b/docs/GlossaryAuthor/emptystartscreen.png
deleted file mode 100644
index 2845ac75..00000000
Binary files a/docs/GlossaryAuthor/emptystartscreen.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/exactmatch.png b/docs/GlossaryAuthor/exactmatch.png
deleted file mode 100644
index 030b15ba..00000000
Binary files a/docs/GlossaryAuthor/exactmatch.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/filter.png b/docs/GlossaryAuthor/filter.png
deleted file mode 100644
index 70981304..00000000
Binary files a/docs/GlossaryAuthor/filter.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/glossaryaddinput.png b/docs/GlossaryAuthor/glossaryaddinput.png
deleted file mode 100644
index 7f279c09..00000000
Binary files a/docs/GlossaryAuthor/glossaryaddinput.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/glossaryaddresult.png b/docs/GlossaryAuthor/glossaryaddresult.png
deleted file mode 100644
index 62b853f5..00000000
Binary files a/docs/GlossaryAuthor/glossaryaddresult.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/glossarychildren.png b/docs/GlossaryAuthor/glossarychildren.png
deleted file mode 100644
index 52df380e..00000000
Binary files a/docs/GlossaryAuthor/glossarychildren.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/initialquickterms.png b/docs/GlossaryAuthor/initialquickterms.png
deleted file mode 100644
index 9a145e44..00000000
Binary files a/docs/GlossaryAuthor/initialquickterms.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/leftnav.png b/docs/GlossaryAuthor/leftnav.png
deleted file mode 100644
index 82ff2a51..00000000
Binary files a/docs/GlossaryAuthor/leftnav.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/nodetabs.png b/docs/GlossaryAuthor/nodetabs.png
deleted file mode 100644
index 1f2e5afc..00000000
Binary files a/docs/GlossaryAuthor/nodetabs.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/quickterms.png b/docs/GlossaryAuthor/quickterms.png
deleted file mode 100644
index ea4b335e..00000000
Binary files a/docs/GlossaryAuthor/quickterms.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/quicktermsresults.png b/docs/GlossaryAuthor/quicktermsresults.png
deleted file mode 100644
index 8d066fc6..00000000
Binary files a/docs/GlossaryAuthor/quicktermsresults.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/quicktermswithblankrows.png b/docs/GlossaryAuthor/quicktermswithblankrows.png
deleted file mode 100644
index 5e86b09f..00000000
Binary files a/docs/GlossaryAuthor/quicktermswithblankrows.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/quicktermswithnames.png b/docs/GlossaryAuthor/quicktermswithnames.png
deleted file mode 100644
index 3a427668..00000000
Binary files a/docs/GlossaryAuthor/quicktermswithnames.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/startscreenwithoneglossary.png b/docs/GlossaryAuthor/startscreenwithoneglossary.png
deleted file mode 100644
index 2ad92970..00000000
Binary files a/docs/GlossaryAuthor/startscreenwithoneglossary.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/startscreenwithonelistedglossary.png b/docs/GlossaryAuthor/startscreenwithonelistedglossary.png
deleted file mode 100644
index 244823b7..00000000
Binary files a/docs/GlossaryAuthor/startscreenwithonelistedglossary.png and /dev/null differ
diff --git a/docs/GlossaryAuthor/topcats.png b/docs/GlossaryAuthor/topcats.png
deleted file mode 100644
index 89c8d944..00000000
Binary files a/docs/GlossaryAuthor/topcats.png and /dev/null differ
diff --git a/site/docs/contributors/contributorguide.md b/docs/contributors/contributorguide.md
similarity index 99%
rename from site/docs/contributors/contributorguide.md
rename to docs/contributors/contributorguide.md
index df20e6d9..06a17013 100644
--- a/site/docs/contributors/contributorguide.md
+++ b/docs/contributors/contributorguide.md
@@ -29,6 +29,7 @@ This project is a [Create React App](https://reactjs.org/docs/create-a-new-react
## 5. cra-server
This is the Express server (also known as the presentation server). the cra - stands for Create React app.
+
* db - this is the in memory database used for the simple authentication for demo purposes
* functions - common functions
* node_modules - dependant node modules
@@ -37,6 +38,7 @@ This is the Express server (also known as the presentation server). the cra - st
## 6. cra-client
This is the client code including the javascript. the cra - stands for Create React app.
+
* build - this is where the client code is built for use in production
* node_modules - dependant node modules
* public - resources
diff --git a/docs/TEX-design.drawio b/docs/design/glossary-author/TEX-design.drawio
similarity index 100%
rename from docs/TEX-design.drawio
rename to docs/design/glossary-author/TEX-design.drawio
diff --git a/docs/design/tex/TEX-design.drawio b/docs/design/tex/TEX-design.drawio
deleted file mode 100644
index ce273870..00000000
--- a/docs/design/tex/TEX-design.drawio
+++ /dev/null
@@ -1 +0,0 @@
-zip or tar.gz file, which you need to extract.
-=== "Development"
- git clone the repository using the instructions under the Code button at Latest code
-
- You now have a folder on your machine with the user interface code extracted.
-
-## 2. The presentation server environment variable
-
-The presentation server is the node application for the user applicaiton. It serves the web pages, proxies therest calls andhandles the login.
-For a particular tentant thepresentation server needs to know which back end servr to send requests to. This information is supplied in an
-environment variable(s).
-
-The environment variable is:
-
-EGERIA_PRESENTATIONSERVER_SERVER_\={"remoteServerName":"\","remoteURL":"\"}
-
-where
-
-cra-client folder and run npm installcra-server folder and run npm installcra-client, then run npm run build. The cra-client folder now should contain a build folder containing the artifiacts to run in production.npm run prod in the cra-server folder.cra-server and run npm start. https://localhost:9443/aaa/ (Replace host/port accordingly)
-
-* In this example `aaa` is the tenant name we used above when defining the environment variable
-
-* The trailing / is currently required to allow the login page to load
-
-For ecosystem tools use user 'garygeeke' and password 'admin'.
-
-For glossary author use user 'faithbroker' and password 'admin'.
-
-
-## 5. SSL configuration
-
-By default the Egeria React UI uses a truststore.p12 and keystore.p12 files for ssl. The p12 files are copies of files 'https://github.com/odpi/egeria/blob/master/keystore.p12' and 'https://github.com/odpi/egeria/blob/master/truststore.p12', which are the definitive sources of these files. The keystore and truststore files allow Egeria to run simply in a demo/development; this is not appropriate for production, which should be appropriately secured.
diff --git a/site/docs/index.md b/site/docs/index.md
deleted file mode 100644
index d2ad9b0d..00000000
--- a/site/docs/index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-template: home.html
-title: About
----
diff --git a/site/docs/overview/Overview.md b/site/docs/overview/Overview.md
deleted file mode 100644
index 4f70b37d..00000000
--- a/site/docs/overview/Overview.md
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-# Egeria React UI Overview
-
-The Egeria React UI isa React multi tenant User Interface for Open Metadata and Governance. It is part of the [Egeria](https://github.com/odpi/egeria/blob/master/README.md) project; as such it is bound by the same code of conduct, governance etc and it part of the Egeria community (and community calls).
-
-This Git repository contains the Egeria React User Interface (UI), which provides a multi tenanted, persona based interface for users to work with Egeria solutions and Egeria ecosystem tools.
-
-This repository is separate from the main Egeria repository, because the technology and build infrastructure is sufficiently different for the User interface.
-Egeria React User Interface developers work with nodejs, develop in javascript, use the React framework and use npm; whereas the main Egeria repository attracts developers with Java skills.
-
-The **Presentation Server** is a multi-tenant persona based server that serves a user interface - it issues rest calls downstream primarily to [view servers](https://egeria.odpi.org/open-metadata-implementation/admin-services/docs/concepts/view-server.html)
-
-See the [Egeria Planning guide](https://egeria.odpi.org/open-metadata-publication/website/planning-guide/) to familiarise yourself with
-the types of [Egeria OMAG Servers](https://egeria.odpi.org/open-metadata-implementation/docs/concepts/omag-server.md). There is an Egeria tutorial on setting up Egeria servers can be following [Egeria Dojo](https://egeria.odpi.org/open-metadata-resources/open-metadata-tutorials/egeria-dojo/), but this does not detail the parts to do with the presentation server and this UI.
-
-There are 2 types of capabilities in the Presentation Server.
-
-* [Ecosystem Tools](../ecosystem/ecosystem.md)
-* [Solutions](../solutions/solutions.md)
diff --git a/site/docs/solutions/GlossaryAuthor/GlossaryAuthorGuide.md b/site/docs/solutions/GlossaryAuthor/GlossaryAuthorGuide.md
deleted file mode 100644
index 5c8b6627..00000000
--- a/site/docs/solutions/GlossaryAuthor/GlossaryAuthorGuide.md
+++ /dev/null
@@ -1,86 +0,0 @@
-
-
-
-# Glossary Author
-
-The **Glossary Author** is a UI capability of the Egeria React UI that allows you to author glossary content, such as Glossaries, Terms, Categories
-and the relationships between them.
-
-## 1. Concepts
-
-Egeria has subject area open types that are described in [Area 3](https://egeria.odpi.org/open-metadata-publication/website/open-metadata-types/Area-3-models.html). This mature model of glossary content describes the relevant concepts around glossaries.
-
-The Glossary Author exposes concepts (json objects) that map onto the open types. The Glossary Author concepts are intended to make it easier for a
-user interface to author glossaries.
-
-As metadata is often best thought of as a graph; the Glossary author user interface exposes the concept of a Graph containing only the concepts relevant to a glossary author. The Graph is composed of Nodes (vertices) and Relationships (edges).
-
-Glossary, Category and Term are all types of Node. The Node object contains standard Egeria properties including:
-
-* Name - name to be displayed.
-* qualfied name - readable unique name
-* guid - global unique identifier.
-
-Glossary Author Node inheritance model, including the nodes that inherit from Term , Category and Glossary.
-
-
-## 2. Working with the Glossary Author user interface.
-
-
-## 2.1 Getting to the Glossary Author start screen
-- After logging into the Egeria react UI, you will see tasks at the left hand side of the user interface including the glossary author task.
-- If you see a screen with a connect button, then the glossary author is not able to issue a successfully glossary call; this is caused by either
- - the Subject Area OMAS is not active, so the glossary author cannot call it
- - the glossary author view is not configured on the view server.
- - the presentation server is not configured to point to the glossary server view service.
- If everythign is correctly configured but the view server or its downstream server is not started then, start them and press the connect button.
-- Assuming you have successfully connected, then you are now in a position to author glossary content
-- You will notice that you can choose the node to work with using the node tabs.
-
-## 2.2 Add a glossary
-- Add a node on a tab using the add (+) button. Pressing add for glossary will show a form to input properties. The minimal input is a name.
-
- ## 2.3 Working with a glossary
-- Navigating back after having created a glossary called 'glossary1' in an empty system, will show one glossary in a 'card view'
-- 'List view' You can toggle the glossary view to show the glossaries as a list
-- 'paging' - notice the paging options, these allow you to change the page size (how many are displayed), page through the results if there is more than a page's worth to display.
-- 'filter' Entering text into the filter box, filters the displayed results. If you want an exact match, check the exact match box.
-
-## 2.4 Buttons that appear when a node is selected
-- Note that there is a checkbox on the node card; when checked, buttons appear indicating actions you can perform against the selected node:
- - Quickterms button - this is shown for glossary, to quickly create Terms under the selected glossary
- - Children button - this shows the children of the selected node.
- - edit button - this displays an edit screen for the selected node
- - delete button - this deletes the selected node. Glossaries with content cannot be deleted.
- - glove button - visualisation described later
-
-## 2.5 Quick terms
-- The quick term screen lists the terms to be added. Initially it is empty
-- Press the + button to add extra rows
-- fill in the name and description in the rows
-- press Create Terms on Server button to show a screen indicaing whetehr the terms have been created or not.
-
-## 3. Working with Categories and Terms
-Working with Categories and terms, is similar to working with Glossaries, apart from
- - choosing the Term or Category node tab, Terms or Categories can be created, in this case a wizard is displayed to aske the user to choose the glossary in which the term should be created.
-
-## 4. Glossary children
-When the glossary children action is chosen, the categories and terms under that glossary are displayed.
-By default top categories are displayed, these are categories that do not have a parent category. If you want to see the all the categories under the glossary then toggle the Top Categories to All Categories
-
-## 5. Breadcrumb
-While navigating, a breadcrumb is created showing how deep the current node is that is being authored.
-
-## 6. Glove
-Glove is a visualisation that can be displayed when there is a selected node, it displays a canvas with the single node on it.It is then possible to
-* explore from the node to other glossary content.
-* Author new relationsips and nodes
-* search and add new nodes to the canvas
-
-
-## 7. Future improvements
-- a breadcrumb to be optimized to minimize the url length.
-- add governance classification authoring
-- add spine object views
-- add collaboration authoring and viewing
-- start with a context from the community profile.
diff --git a/site/docs/solutions/solutions.md b/site/docs/solutions/solutions.md
deleted file mode 100644
index ff4bdd95..00000000
--- a/site/docs/solutions/solutions.md
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
-These are user interface capabilities allowing particular personas to work with [Egeria Solutions](https://egeria.odpi.org/open-metadata-publication/website/solutions/). The solutions that are being developed are:
-
-- [GlossaryAuthor](./GlossaryAuthor/GlossaryAuthorGuide.md): allowing a Glossary Author persona to create, update and delete Glossary content.
-
-The expectation is that more solutions will be developed by the community.
\ No newline at end of file
diff --git a/site/mkdocs.yml b/site/mkdocs.yml
deleted file mode 100644
index 8e514075..00000000
--- a/site/mkdocs.yml
+++ /dev/null
@@ -1,85 +0,0 @@
-# SPDX-License-Identifier: CC-BY-4.0
-# Copyright Contributors to the ODPi Egeria project.
-
-site_name: Egeria React UI
-site_description: A multi-tenant Egeria React UI for Open Metadata.
-copyright: "License: CC BY 4.0, © 2018-2021 contributors to the Egeria project."
-repo_name: odpi/egeria-react-ui
-repo_url: https://github.com/odpi/egeria-react-ui
-site_url: https://odpi.github.io/egeria-react-ui/
-edit_uri: ""
-
-nav:
- - About: index.md
- - Getting started:
- - getting-started/prereqs.md
- - getting-started/setup.md
- - Overview:
- - overview/Overview.md
- - Solutions:
- - solutions/solutions.md
- - solutions/GlossaryAuthor/GlossaryAuthorGuide.md
- - Eco System:
- - ecosystem/ecosystem.md
- - ecosystem/RepositoryExplorerGuide.md
- - Contributors section:
- - contributors/contributorguide.md
-
-theme:
- name: material
- language: en
- custom_dir: overrides
- features:
- - navigation.tabs
- - navigation.sections
-# - navigation.instant
- - navigation.top
-# - toc.integrate
- palette:
- - scheme: default
- accent: cyan
- toggle:
- icon: material/toggle-switch-off-outline
- name: Switch to dark mode
- - scheme: slate
- accent: cyan
- toggle:
- icon: material/toggle-switch
- name: Switch to light mode
- icon:
- repo: fontawesome/brands/github
- favicon: assets/favicon.ico
- logo: assets/images/egeria-header.png
-
-extra_css:
- - assets/stylesheets/egeria.css
-
-extra:
- social:
- - icon: fontawesome/brands/github
- link: https://github.com/odpi/egeria
- name: Egeria on GitHub
- - icon: fontawesome/brands/docker
- link: https://hub.docker.com/u/odpi
- name: Egeria on Docker
- - icon: fontawesome/brands/medium
- link: https://medium.com/tag/egeria
- name: Egeria on Medium
- - icon: fontawesome/brands/slack
- link: https://lfaifoundation.slack.com/archives/C01F40J2XA8
- name: Egeria on Slack
-
-markdown_extensions:
- - admonition
- - attr_list
- - abbr
- - pymdownx.snippets
- - pymdownx.highlight
- - pymdownx.details
- - pymdownx.tabbed
- - pymdownx.superfences
- - toc:
- permalink: true
- - pymdownx.emoji:
- emoji_index: !!python/name:materialx.emoji.twemoji
- emoji_generator: !!python/name:materialx.emoji.to_svg
diff --git a/site/overrides/home.html b/site/overrides/home.html
deleted file mode 100644
index 19f0b755..00000000
--- a/site/overrides/home.html
+++ /dev/null
@@ -1,288 +0,0 @@
-
-
-
-
-
-{% extends "main.html" %}
-
-{% block tabs %}
-{{ super() }}
-
-
-- User interface to explore open metadata from many metadata sources via the Egeria eco-system. -
-- Leverages Egeria's open APIs for solutions designed for a particuler personna e.g. glossary author. -
-- Supports multi tenants. Each tenant can access different subsets of the backend metadata. -
-
-{% endblock %}
\ No newline at end of file
diff --git a/site/overrides/partials/header.html b/site/overrides/partials/header.html
deleted file mode 100644
index 0fb8ab3d..00000000
--- a/site/overrides/partials/header.html
+++ /dev/null
@@ -1,151 +0,0 @@
-
-
-
-
-
-
-