mirror of
https://github.com/Ocelot-Social-Community/Ocelot-Social.git
synced 2025-12-12 23:35:58 +00:00
Capitalized titles, encourage to update docs
This commit is contained in:
parent
c4a1c23e0e
commit
7c951bfb50
10
SUMMARY.md
10
SUMMARY.md
@ -1,13 +1,11 @@
|
||||
# Table of contents
|
||||
|
||||
* [README](README.md)
|
||||
* [Let's change the World](documentation/README.md)
|
||||
* [documentation](documentation/documentation/README.md)
|
||||
* [Edit this Documentation](documentation/documentation/edit-this-documentation.md)
|
||||
* [Edit this Documentation](edit-this-documentation.md)
|
||||
* [concept](concept/README.md)
|
||||
* [Network Specification](concept/specification.md)
|
||||
* [Installation](installation.md)
|
||||
* [webapp](webapp/README.md)
|
||||
* [Webapp](webapp/README.md)
|
||||
* [COMPONENTS](webapp/components.md)
|
||||
* [PLUGINS](webapp/plugins.md)
|
||||
* [STORE](webapp/store.md)
|
||||
@ -23,7 +21,7 @@
|
||||
* [Our GitHub Workflow](documentation/workflow/contribute/github-workflow.md)
|
||||
* [Deployment](documentation/workflow/deployment.md)
|
||||
* [Table of contents](documentation/summary.md)
|
||||
* [backend](backend/README.md)
|
||||
* [Backend](backend/README.md)
|
||||
* [graphql-with-apollo](backend/graphql-with-apollo/README.md)
|
||||
* [GraphQL with Apollo](backend/graphql-with-apollo/graphql-with-apollo/README.md)
|
||||
* [Mocking](backend/graphql-with-apollo/graphql-with-apollo/mocking.md)
|
||||
@ -32,7 +30,7 @@
|
||||
* [Import](backend/data-import.md)
|
||||
* [Middleware](backend/middleware.md)
|
||||
* [Testing Guide](testing.md)
|
||||
* [cypress](cypress/README.md)
|
||||
* [Cypress](cypress/README.md)
|
||||
* [Integration Testing](cypress/integration-testing.md)
|
||||
* [Deployment](deployment.md)
|
||||
* [CONTRIBUTING](contributing.md)
|
||||
|
||||
@ -1,18 +0,0 @@
|
||||
# Let's change the World
|
||||
|
||||
## Why do we need HC Nitro?
|
||||
|
||||
> This Prototype tries to resolve the biggest hurdle of connecting our services together. This is not possible in a sane way using our current approach.
|
||||
>
|
||||
> With this Prototype we can explore using the combination of GraphQL and the Neo4j Graph Database for achieving the connected nature of a social graph with better development experience, as we do not need to connect data on our own any more through weird table structures etc.
|
||||
>
|
||||
> **Advantages:**
|
||||
>
|
||||
> * easier data structure
|
||||
> * better connected data
|
||||
> * easy to achieve "recommendations" based on actions \(relations\)
|
||||
> * more performant and better to understand API
|
||||
> * better API client that uses caching
|
||||
>
|
||||
> We still need to evaluate the drawbacks and estimate the development cost of such an approach.
|
||||
|
||||
@ -1,2 +0,0 @@
|
||||
# documentation
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user