diff --git a/docs/learn/delivery-acknowledgements.md b/docs/learn/delivery-acknowledgements.md index e98aa22f3..fedc93621 100644 --- a/docs/learn/delivery-acknowledgements.md +++ b/docs/learn/delivery-acknowledgements.md @@ -8,8 +8,6 @@ tags: sidebarCollapsible: false --- -import Author from '@site/src/components/Author'; - ## Overview When a client signs a message, it creates a Delivery Acknowledgement that confirms a successful service computation delivery by a node. This [process](#node-vs-client-process-flow) ensures the immutability and integrity of the message (the client cannot change or reverse it) and also includes metadata about the commodities consumed by the node during the service execution. This metadata helps in calculating the reward that the node will receive. @@ -75,10 +73,3 @@ Learn more about it in the [Content Addressing](/docs/learn/the-network#content- ## Delivery Acknowledgement Customization A Service can have a custom configuration to specify how Delivery Acknowledgements should behave or work. Patterns and conventions should be expected to emerge from the Service builder community and best practices. - - diff --git a/docs/learn/index.md b/docs/learn/index.md index beac14e8a..5bf9a3b08 100644 --- a/docs/learn/index.md +++ b/docs/learn/index.md @@ -10,8 +10,6 @@ tags: - whitepaper --- -import Author from '@site/src/components/Author'; - ## Introduction The Core of Fleek Network offers a foundational layer to enable developers to build and deploy Edge Services efficiently. It abstracts away the development complexities of consensus, cryptography, storage and peer-to-peer networking, etc, to simplify things conceptually. It frees developers and teams to focus on what matters the most to reach business goals. @@ -47,10 +45,3 @@ When a client requests a service, the protocol determines the best route to the Once the computation is successful, the data streaming routes to the client. On-client request fulfillment, a proof of delivery is generated containing cryptographically secured metadata about the original request, any parts involved and the resources consumed. The Delivery Acknowledgements are stored locally in the participating node memory pools, rolled up to the protocol consensus consistently throughout the epoch (about 24h). This agreement is formed by a random committee of any healthy Nodes that use the information provided to reward the Nodes fairly. - - diff --git a/docs/learn/services.md b/docs/learn/services.md index dcd981f60..36260dcef 100644 --- a/docs/learn/services.md +++ b/docs/learn/services.md @@ -18,8 +18,6 @@ tags: - toolkit --- -import Author from '@site/src/components/Author'; - ## Overview A Fleek Network Service is a modular application that runs on nodes and allows users to perform well-defined functions or some specific tasks. Services are scalable and performant due to edge computation and networking features provided by the core principles of the network. @@ -137,10 +135,3 @@ This causes long finalization times and a reduction in block speeds on Layer-1, In Fleek Network, a service builder can offer an alternative to a Layer-2 sequencer, that is decentralized and more reliable by batching and posting to Layer-1 settlement contracts. With equivalent Layer-2 settlement times. An additional benefit can be enabling end-user gasless transaction submissions by disregarding a Layer-2 gas token to submit transactions to Layer-1. - - \ No newline at end of file diff --git a/docs/learn/the-network.md b/docs/learn/the-network.md index 83f5c6649..1bcf75056 100644 --- a/docs/learn/the-network.md +++ b/docs/learn/the-network.md @@ -17,7 +17,6 @@ tags: sidebarCollapsible: false --- -import Author from '@site/src/components/Author'; import Ports from '../../guides/partials/_ports.mdx'; ## Protocol @@ -401,10 +400,3 @@ The Fleek Network binary process is the program that's been compiled down to mac A JSON-RPC (JavaScript Object Notation Remote Procedure Call) is a protocol that enables communication between client and server applications. The [Fleek Network JSON-RPC](https://fleek-network.github.io/lightning/api-documentation/?202308171515) API enables JSON-RPC interaction with Fleek Network Node. Fleek Network JSON-RPC API reference documentation is available at [https://fleek-network.github.io/lightning/api-documentation](https://fleek-network.github.io/lightning/api-documentation). - - diff --git a/docs/node/analyzing-logs.md b/docs/node/analyzing-logs.md index fc4ac33c0..0ec4b3f0d 100644 --- a/docs/node/analyzing-logs.md +++ b/docs/node/analyzing-logs.md @@ -7,7 +7,6 @@ tags: - diagnostic --- -import Author from '@site/src/components/Author'; ## Analyzing Logs @@ -86,10 +85,3 @@ In any case, you can use the Docker command to analyze the logs. If you have sti sudo docker logs -f lightning-node ``` ::: - - diff --git a/docs/node/health-check.md b/docs/node/health-check.md index 7bee0ab94..b2130bc99 100644 --- a/docs/node/health-check.md +++ b/docs/node/health-check.md @@ -8,8 +8,6 @@ tags: - node status --- -import Author from '@site/src/components/Author'; - ## TL;DR: Run the command A script is available to do and provide a health check overview: @@ -104,10 +102,3 @@ If the request is successful, you should get the result `pong` as follows: ``` Any other response, such as errors determine that the node is not healthy. - - diff --git a/docs/node/index.md b/docs/node/index.md index 3d243af98..906931569 100644 --- a/docs/node/index.md +++ b/docs/node/index.md @@ -7,8 +7,6 @@ tags: - build --- -import Author from '@site/src/components/Author'; - ## Overview This section provides instructions to help you build a **Fleek Network Node**, it's aimed at everybody willing to learn and cultivate knowledge as a node operator. @@ -40,11 +38,3 @@ While we do our best to provide the clearest instructions, there's always space ::: **Ready?** Start by checking the [server requirements](/docs/node/requirements) - - - diff --git a/docs/node/install.md b/docs/node/install.md index 08cf0f50e..857699558 100644 --- a/docs/node/install.md +++ b/docs/node/install.md @@ -18,7 +18,6 @@ tags: - manual --- -import Author from '@site/src/components/Author'; import GitCloneOptions from '../../guides/partials/_git-clone-options.mdx'; import CreateAUser from '../../guides/partials/_create-a-user.mdx'; import SetUserPathInConfigToml from '../../guides/partials/_set-user-path-config-toml.mdx'; @@ -708,10 +707,3 @@ Learn how to manage the Systemd Service by reading the section [systemd service] ## Frequently Used Commands (Quick Reference) A quick reference of the most Frequently Used Commands are available for [Native](/references/Lightning%20CLI/frequently-used-commands-for-native-setup) and [Docker](/references/Docker/frequently-used-commands-for-docker-setup) setups. If you'd like a more in depth explanation of the commands, check the [health check](/docs/node/health-check), [analyzing logs](/docs/node/analyzing-logs), [systemd service](/docs/node/systemd-service) and [guides](/guides) sections separately. - - diff --git a/docs/node/lightning-cli.md b/docs/node/lightning-cli.md index 07d687c7c..8ef9557ac 100644 --- a/docs/node/lightning-cli.md +++ b/docs/node/lightning-cli.md @@ -9,7 +9,6 @@ tags: - lgtn --- -import Author from '@site/src/components/Author'; import InfoNetworkParticipation from '../../guides/partials/_info_network_participation.mdx'; import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx'; import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx'; @@ -167,10 +166,3 @@ Options: -v... Increases the level of verbosity (the max level is -vvv) -h, --help Print help ``` - - diff --git a/docs/node/requirements.md b/docs/node/requirements.md index d1a924b5f..6d543bec5 100644 --- a/docs/node/requirements.md +++ b/docs/node/requirements.md @@ -8,7 +8,6 @@ tags: sidebarCollapsible: false --- -import Author from '@site/src/components/Author'; import Ports from '../../guides/partials/_ports.mdx'; ## Requirements @@ -57,10 +56,3 @@ The recommended number of CPU cores is a minimum of 4 with a minimum CPU speed o ### Memory A minimum of 32 GB of memory (RAM) is required and a reasonable amount of disk space for the installation and running processes, which at the minimum should be around 20 GB. - - diff --git a/docs/node/systemd-service.md b/docs/node/systemd-service.md index b18c09085..c818b4690 100644 --- a/docs/node/systemd-service.md +++ b/docs/node/systemd-service.md @@ -9,7 +9,6 @@ tags: - manage --- -import Author from '@site/src/components/Author'; import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx'; import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx'; import InfoNetworkParticipation from '../../guides/partials/_info_network_participation.mdx'; @@ -156,10 +155,3 @@ If you have installed or set up the Service as a Docker Container, prefix the se sudo systemctl status docker-lightning ``` ::: - - diff --git a/docs/node/testnet-onboarding.md b/docs/node/testnet-onboarding.md index 6785b81e5..2f9d46a16 100644 --- a/docs/node/testnet-onboarding.md +++ b/docs/node/testnet-onboarding.md @@ -11,7 +11,6 @@ tags: sidebarCollapsible: false --- -import Author from '@site/src/components/Author'; import InfoNetworkParticipation from '../../guides/partials/_info_network_participation.mdx'; :::warning @@ -184,10 +183,3 @@ However, if you wish to learn about key management, you can refer to the [instru ### Does Nodes require to have SGX chips? Phase {4} testnet includes enhancements that require node features, such as [SGX chips](https://en.wikipedia.org/wiki/Software_Guard_Extensions). This enhances the network's capabilities and expands its service and use cases, as described in the [Genesis Node Operator Application](https://blog.fleek.network/post/genesis-node-operator-application/). For more information check the [following list of hardware](https://github.com/ayeks/SGX-hardware) which supports Intel SGX - Software Guard Extensions. - - diff --git a/guides/Node Operators/getting-started-guide.md b/guides/Node Operators/getting-started-guide.md index 8b8a19757..52ff22170 100644 --- a/guides/Node Operators/getting-started-guide.md +++ b/guides/Node Operators/getting-started-guide.md @@ -20,7 +20,6 @@ tags: -import Author from '@site/src/components/Author'; import GitCloneOptions from '../partials/_git-clone-options.mdx'; import InfoNetworkParticipation from '../../guides/partials/_info_network_participation.mdx'; @@ -266,10 +265,3 @@ Furthermore, we guide you through a step-by-step installation of the network nod Finally, we do a quick health check to confirm the status of our node. Discover more about the project by [watching/contributing on GitHub](https://github.com/fleek-network/lightning), following us on [Twitter](https://twitter.com/fleek_net), and joining [our community Discord](https://discord.gg/fleek) for any updates. - - diff --git a/guides/Node Operators/how-to-manage-logfiles.md b/guides/Node Operators/how-to-manage-logfiles.md index 862d0fc8b..c649d2947 100644 --- a/guides/Node Operators/how-to-manage-logfiles.md +++ b/guides/Node Operators/how-to-manage-logfiles.md @@ -13,8 +13,6 @@ tags: ![How to manage log files](./assets/how-to-manage-log-files.png?202310271441) -import Author from '@site/src/components/Author'; - ## Introduction The Fleek Network node streams text messages to the standard output and error in Linux. Given that disk space is a limited resource for most systems, the number of text data can be a cause of concern. Managing the file sizes by means of rotation and compression can help. @@ -292,10 +290,3 @@ The guide starts by warning us about the stream text messages that the Fleek Net To help control it, the journald is introduced, by explaining its role as a centralized message system, that runs alongside the application logs. Then, have it configured to limit the maximum file size, amongst other system-wide settings. Finally, logrotate is discussed in helping us manage the Fleek Network Lightning application log files by setting it to automatically compress, rename, remove logs for the system admin convenience and saving system's resources. - - \ No newline at end of file diff --git a/guides/Node Operators/managing-the-keystore.md b/guides/Node Operators/managing-the-keystore.md index e852bd83d..1dd14574b 100644 --- a/guides/Node Operators/managing-the-keystore.md +++ b/guides/Node Operators/managing-the-keystore.md @@ -16,7 +16,6 @@ tags: ![Managing the keystore](./assets/managing-the-keystore.png?202311181211) -import Author from '@site/src/components/Author'; import RestoreKeystore from '../partials/_restore-keystore.mdx'; ## Introduction @@ -439,10 +438,3 @@ In the future, we'll introduce more advanced topics that will help you improve t While we do our best to provide the clearest instructions, there's always space for improvement, therefore feel free to make any contributions by messaging us on our [Discord](https://discord.gg/fleek) or by opening a [PR](https://github.com/fleek-network) in any of our repositories. Discover more about the project by [watching/contributing on Github](https://github.com/fleek-network/lightning), following us on [Twitter](https://twitter.com/fleek_net), and joining [our community Discord](https://discord.gg/fleek) for all the best updates! - - \ No newline at end of file diff --git a/guides/Node Operators/running-a-node-in-docker.md b/guides/Node Operators/running-a-node-in-docker.md index 0dfc5733a..0deefbd4b 100644 --- a/guides/Node Operators/running-a-node-in-docker.md +++ b/guides/Node Operators/running-a-node-in-docker.md @@ -17,7 +17,6 @@ tags: -import Author from '@site/src/components/Author'; import GitCloneOptions from '../partials/_git-clone-options.mdx'; import CreateAUser from '../../guides/partials/_create-a-user.mdx'; @@ -441,10 +440,3 @@ We guided you through the initial installation steps, and how to build a [Docker While we do our best to provide the clearest instructions, there's always space for improvement, therefore feel free to make any contributions by messaging us on our [Discord](https://discord.gg/fleek) or by opening a [PR](https://github.com/fleek-network) in any of our repositories. Discover more about the project by [watching/contributing on Github](https://github.com/fleek-network/lightning), following us on [Twitter](https://twitter.com/fleek_net), and joining [our community Discord](https://discord.gg/fleek) for all the best updates! - - diff --git a/guides/Node Operators/transfering-setup-ownership.md b/guides/Node Operators/transfering-setup-ownership.md index 335aa6a77..4a0d0eb0e 100644 --- a/guides/Node Operators/transfering-setup-ownership.md +++ b/guides/Node Operators/transfering-setup-ownership.md @@ -21,7 +21,6 @@ tags: -import Author from '@site/src/components/Author'; import CreateAUser from '../../guides/partials/_create-a-user.mdx'; import FindAndReplaceConfigWithUserPaths from '../../guides/partials/_find-and-replace-config-with-user-paths.mdx'; @@ -350,10 +349,3 @@ Jumped through topics of Systemd service that helps the user manage the service We've gone through the step-by-step process to migrate the Fleek Network CLI and Systemd service setup from one user to the other. To keep it short, we decided to go with the use-case of where the migration happens between a **root** user and a **sudoer**. Discover more about the project by [watching/contributing on GitHub](https://github.com/fleek-network/lightning), following us on [Twitter](https://twitter.com/fleek_net), and joining [our community Discord](https://discord.gg/fleek) for any updates. - - diff --git a/guides/Node Operators/updating-lightning.md b/guides/Node Operators/updating-lightning.md index 3521ff78d..e2a43ca4e 100644 --- a/guides/Node Operators/updating-lightning.md +++ b/guides/Node Operators/updating-lightning.md @@ -16,7 +16,6 @@ tags: ![Update Lightning](./assets/updating-lightning.png?202309191740) -import Author from '@site/src/components/Author'; import CheckoutCommitWarning from '../../guides/partials/_checkout-commit-warning.mdx'; import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx'; import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx'; @@ -359,10 +358,3 @@ We have looked into how to pull the changes via Git, and discussed that contribu To complete, provided a step-by-step walkthrough the installation and setup process for the Fleek Network Lightning CLI and Systemd service. Discover more about the project by [watching/contributing on GitHub](https://github.com/fleek-network/lightning), following us on [Twitter](https://twitter.com/fleek_net), and joining [our community Discord](https://discord.gg/fleek) for any updates. - - diff --git a/references/Docker/build-and-run-in-docker.md b/references/Docker/build-and-run-in-docker.md index 55293cc77..caca9d3f9 100644 --- a/references/Docker/build-and-run-in-docker.md +++ b/references/Docker/build-and-run-in-docker.md @@ -11,7 +11,6 @@ tags: - container --- -import Author from '@site/src/components/Author'; import GitCloneOptions from '../../guides/partials/_git-clone-options.mdx'; ## Clone the source code locally @@ -159,10 +158,3 @@ To view the logs of a Docker container in real time, use the following command: ```sh sudo docker logs -f lightning-node ``` - - diff --git a/references/Docker/frequently-used-commands-for-docker-setup.md b/references/Docker/frequently-used-commands-for-docker-setup.md index 449aa0072..854de85b4 100644 --- a/references/Docker/frequently-used-commands-for-docker-setup.md +++ b/references/Docker/frequently-used-commands-for-docker-setup.md @@ -9,8 +9,6 @@ tags: - docker --- -import Author from '@site/src/components/Author'; - ## TL;DR Most assisted processes are available through the `get.fleek.network` command, where you can select to install, do a health check amongst others. @@ -184,10 +182,3 @@ sudo docker stop ```sh sudo docker rm ``` - - diff --git a/references/Docker/uninstall-docker-setup.md b/references/Docker/uninstall-docker-setup.md index c1e0a95e8..92533d373 100644 --- a/references/Docker/uninstall-docker-setup.md +++ b/references/Docker/uninstall-docker-setup.md @@ -10,7 +10,6 @@ tags: - container --- -import Author from '@site/src/components/Author'; import GitCloneOptions from '../../guides/partials/_git-clone-options.mdx'; import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx'; import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx'; @@ -147,10 +146,3 @@ To completely remove the directory run the command: ```sh sudo rm -rf /var/log/lightning ``` - - diff --git a/references/Lightning CLI/error-linking-with-cc-failed.md b/references/Lightning CLI/error-linking-with-cc-failed.md index 32f936859..595369af9 100644 --- a/references/Lightning CLI/error-linking-with-cc-failed.md +++ b/references/Lightning CLI/error-linking-with-cc-failed.md @@ -10,8 +10,6 @@ tags: - fix --- -import Author from '@site/src/components/Author'; - ## Check if CPU is supported ```sh @@ -54,11 +52,3 @@ curl https://get.fleek.network | bash ``` Alternatively, read the [manual installation instructions](/docs/node/install#manual-installation) for more information. - - - diff --git a/references/Lightning CLI/file-permissions-and-ownership.md b/references/Lightning CLI/file-permissions-and-ownership.md index 2abdb2997..bff8818cd 100644 --- a/references/Lightning CLI/file-permissions-and-ownership.md +++ b/references/Lightning CLI/file-permissions-and-ownership.md @@ -9,7 +9,6 @@ tags: - root --- -import Author from '@site/src/components/Author'; import FindAndReplaceConfigWithUserPaths from '../../guides/partials/_find-and-replace-config-with-user-paths.mdx'; ## Ownership @@ -147,10 +146,3 @@ sudo systemctl daemon-reload ``` Consequently, when a user manages the service via the systemctl, the Lightning CLI process will read the configuration file settings provided above. It includes the location of the user preferences, such as the keystore location amongst others, preventing confusion regardless of **root** delegation. - - diff --git a/references/Lightning CLI/frequently-used-commands-for-native-setup.md b/references/Lightning CLI/frequently-used-commands-for-native-setup.md index 46fafe6c0..9480af934 100644 --- a/references/Lightning CLI/frequently-used-commands-for-native-setup.md +++ b/references/Lightning CLI/frequently-used-commands-for-native-setup.md @@ -8,7 +8,6 @@ tags: - lightning --- -import Author from '@site/src/components/Author'; import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx'; import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx'; @@ -143,10 +142,3 @@ tail -f /var/log/lightning/output.log ```sh tail -f /var/log/lightning/diagnostic.log ``` - - diff --git a/references/Lightning CLI/keys-not-found.md b/references/Lightning CLI/keys-not-found.md index 6234bea43..aa1f4811b 100644 --- a/references/Lightning CLI/keys-not-found.md +++ b/references/Lightning CLI/keys-not-found.md @@ -9,8 +9,6 @@ tags: - file permissions --- -import Author from '@site/src/components/Author'; - ## Node key does not exist When watching the Fleek Network Lightning service log output, you find the "Node key does not exist" message placed recursively. As follows: @@ -25,11 +23,3 @@ note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace If you haven't deleted the keystore and can locate it, it's due to how the service is being run. As a user can delegate (sudo) the execution of the process to **root**, the location of the keystore differs on runtime. To learn more about how file permissions and ownership work, you're advised to read the reference document [here](/references/Lightning%20CLI/file-permissions-and-ownership.md). - - - diff --git a/references/Lightning CLI/keystore-backup.md b/references/Lightning CLI/keystore-backup.md index f79fe47b3..a781d671f 100644 --- a/references/Lightning CLI/keystore-backup.md +++ b/references/Lightning CLI/keystore-backup.md @@ -10,8 +10,6 @@ tags: - restore --- -import Author from '@site/src/components/Author'; - :::caution The security of the private key is the responsibility of the user. Unfortunately, the Fleek Network team and any others are unable to help regain access to private key if lost or failed to secure them. The private keys are the user responsibility. The Fleek Network team doesn't endorse any methods of encryption and storage, the methods described here are for educational purposes only. ::: @@ -137,10 +135,3 @@ tar -xf keystore.tar -C $HOME/tar_keystore_extract Locate the extracted files in `$HOME/tar_keystore_extract`, which should look like `$HOME/tar_keystore/home//.lightning/keystore` For a more in depth or step-by-step instructions read the guide [managing the keystore](/guides/Node%20Operators/managing-the-keystore). - - diff --git a/references/Lightning CLI/node-secret-key-does-not-exist.md b/references/Lightning CLI/node-secret-key-does-not-exist.md index f66886581..b243422d2 100644 --- a/references/Lightning CLI/node-secret-key-does-not-exist.md +++ b/references/Lightning CLI/node-secret-key-does-not-exist.md @@ -9,8 +9,6 @@ tags: - file permissions --- -import Author from '@site/src/components/Author'; - ## Node secret key does not exist When watching the Fleek Network Lightning service log output, you find the "Node secret key does not exist" message as follows: @@ -31,11 +29,3 @@ node_key_path = "/home/skywalker/.lightning/keystore/node.pem" ``` To learn more about how file permissions and ownership work, you're advised to read the reference document [here](/references/Lightning%20CLI/file-permissions-and-ownership.md). - - - diff --git a/references/Lightning CLI/permission-denied-os-error-13.md b/references/Lightning CLI/permission-denied-os-error-13.md index ec8bbc3b5..9c98e7acf 100644 --- a/references/Lightning CLI/permission-denied-os-error-13.md +++ b/references/Lightning CLI/permission-denied-os-error-13.md @@ -6,8 +6,6 @@ tags: - permissions --- -import Author from '@site/src/components/Author'; - ## Ownership and file permissions When running the Lightning CLI, the user who's in control can delegate to **root** via **sudo**. Depending on how the Fleek Networking Lightning CLI was installed, this might cause some confusion, which is better explained by reading the reference [Keys not found](/references/Lightning%20CLI/keys-not-found), which illustrates a situation where a user gets an error message about the wrong location of a system path (keystore). @@ -73,10 +71,3 @@ Environment=TMPDIR=/var/tmp :::caution attention The `/etc/systemd/system/lightning.service` service unit file presented here is a shorter version for simplicity. Do not replace your service unit file with the shorter content version presented here. ::: - - \ No newline at end of file diff --git a/references/Lightning CLI/restore-keystore.md b/references/Lightning CLI/restore-keystore.md index 9a773e874..5960dbc29 100644 --- a/references/Lightning CLI/restore-keystore.md +++ b/references/Lightning CLI/restore-keystore.md @@ -10,7 +10,6 @@ tags: - restore --- -import Author from '@site/src/components/Author'; import FindAndReplaceConfigWithUserPaths from '../../guides/partials/_find-and-replace-config-with-user-paths.mdx'; import RestoreKeystore from '../../guides/partials/_restore-keystore.mdx'; @@ -79,10 +78,3 @@ lgtn print-config --default > ~/.lightning/config.toml For a more in depth or step-by-step instructions read the guide [managing the keystore](/guides/Node%20Operators/managing-the-keystore). - - diff --git a/references/Lightning CLI/uninstall-lightning-node.md b/references/Lightning CLI/uninstall-lightning-node.md index 3584d2c50..7a7e122ba 100644 --- a/references/Lightning CLI/uninstall-lightning-node.md +++ b/references/Lightning CLI/uninstall-lightning-node.md @@ -12,7 +12,6 @@ tags: - Clean --- -import Author from '@site/src/components/Author'; import WarningPreventPrematureShutdown from '../../guides/partials/_warning_prevent_premature_shutdown.mdx'; import TipShutdownGracefully from '../../guides/partials/_tip_shutdown_gracefully.mdx'; @@ -107,10 +106,3 @@ To uninstall rustc, rustup and cargo run the following command: ```sh rustup self uninstall ``` - - diff --git a/references/Lightning CLI/update-cli-from-source-code.md b/references/Lightning CLI/update-cli-from-source-code.md index 677effc8b..628af4ea4 100644 --- a/references/Lightning CLI/update-cli-from-source-code.md +++ b/references/Lightning CLI/update-cli-from-source-code.md @@ -10,7 +10,6 @@ tags: - fix --- -import Author from '@site/src/components/Author'; import SetUserPathInConfigToml from '../../guides/partials/_set-user-path-config-toml.mdx'; import NoteExecStartFlagCConfigPath from '../../guides/partials/_note_execstart-flag-c-config-path.mdx'; import FindAndReplaceConfigWithUserPaths from '../../guides/partials/_find-and-replace-config-with-user-paths.mdx'; @@ -228,10 +227,3 @@ If successful, you should get the response `running and staked`, as follows: ```sh running and staked ``` - - diff --git a/references/Systemd/service-keeps-running-after-shutdown.md b/references/Systemd/service-keeps-running-after-shutdown.md index ad6a4bff9..5428a5ea8 100644 --- a/references/Systemd/service-keeps-running-after-shutdown.md +++ b/references/Systemd/service-keeps-running-after-shutdown.md @@ -11,8 +11,6 @@ tags: - process --- -import Author from '@site/src/components/Author'; - ## Stop the service The [Systemd service](/docs/node/systemd-service) section tells how to stop the service, as follows: @@ -40,10 +38,3 @@ To force stop the service `lgtn` execute the command: ```sh sudo killall -9 lgtn ``` - - diff --git a/references/Systemd/shutting-down-persistance.md b/references/Systemd/shutting-down-persistance.md index 28e2b1293..57ffb50db 100644 --- a/references/Systemd/shutting-down-persistance.md +++ b/references/Systemd/shutting-down-persistance.md @@ -12,9 +12,6 @@ tags: - systemd --- -import Author from '@site/src/components/Author'; - - ## Systemd Service as frozen or idle If you have a `Shutting node down` message on the service log, the process is likely failing to respond to Systemd shut down command by failing to terminate all the child processes that were started by the service. @@ -85,10 +82,3 @@ Alternatively, you can watch the diagnostic.log ```sh tail -f /var/log/lightning/diagnostic.log ``` - - diff --git a/references/Systemd/user-service.md b/references/Systemd/user-service.md index f1c750a58..b6a63d26e 100644 --- a/references/Systemd/user-service.md +++ b/references/Systemd/user-service.md @@ -11,8 +11,6 @@ tags: - systemd --- -import Author from '@site/src/components/Author'; - A user should have the ability to run a Systemd user service unit without having to use `sudo` to control it. ## Check `--user` support @@ -130,10 +128,3 @@ For example, if we check the `$XDG_RUNTIME_DIR` in a DigitalOcean box, we get th ``` For this reason and to provide support for a wider audience of users and systems, we've stuck to sudo to execute the service, but this should not be a requirement and is not recommended. - - diff --git a/src/components/Author/index.tsx b/src/components/Author/index.tsx deleted file mode 100644 index 283795c4f..000000000 --- a/src/components/Author/index.tsx +++ /dev/null @@ -1,38 +0,0 @@ -import React from 'react'; - -const discordUrl = "https://discord.gg/fleek"; - -const Author = ({ - image, - name, - title, - url, - communityMember = false, -}: { - name: string; - image: string; - title: string; - url: string; - communityMember: boolean, -}): JSX.Element => { - return ( -
-
- {name} -
- {name} - {title} - - { - communityMember - ? "Join our community on" - : "Got questions? Find us on" - } discord! - -
-
-
- ); -}; - -export default Author; diff --git a/src/components/Author/styles.css b/src/components/Author/styles.css deleted file mode 100644 index 7db8c6c14..000000000 --- a/src/components/Author/styles.css +++ /dev/null @@ -1,80 +0,0 @@ -.author_card { - display: flex; - justify-content: flex-end; -} - -.author_card .discord a { - color: var(--ifm-color-primary-darker); - font-weight: bold; -} - -.author_card a { - flex-shrink: 0; -} - -.author_card a img { - transition: transform 0.3s, opacity 0.3s; - width: 60px; - height: 60px; -} - -.author_card a img:hover { - opacity: 0.9; - transform: scale(1.03); -} - -.author_card span, -.author_card a { - font-size: 16px; - line-height: 1.4; -} - -.author_card>div { - display: grid; - grid-template-columns: auto auto; - gap: 1rem; - height: auto; - position: relative; - padding: 20px; - margin: 40px 5px; - border-radius: 0px; - max-width: 420px; - width: 100%; - border: 1px solid var(--ifm-color-primary-darker); -} - -.author_card>div>div { - display: flex; - flex-flow: column; -} - -.author_card img { - display: block; - overflow: hidden; - width: auto; - height: 100%; - align-self: center; -} - -.author_card .title { - flex-grow: 1; -} - -.author_card .name { - font: bold var(--ifm-h4-font-size) / var(--ifm-heading-line-height) var(--ifm-font-family-base); - a { - color: var(--text-color); - } -} - - -@media (min-width: 768px) { - .author_card>div { - height: 120px; - } - - .author_card a img { - width: 80px; - height: 80px; - } -} \ No newline at end of file diff --git a/src/components/Author/styles.module.css b/src/components/Author/styles.module.css deleted file mode 100644 index 975ea17d2..000000000 --- a/src/components/Author/styles.module.css +++ /dev/null @@ -1,11 +0,0 @@ -.container { - width: 100%; -} - -.avatar { - border-radius: 50%; - display: block; - height: var(--ifm-avatar-photo-size); - overflow: hidden; - width: var(--ifm-avatar-photo-size); -} \ No newline at end of file diff --git a/src/css/custom.css b/src/css/custom.css index 2d9a5bfcd..5cc5197ce 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -30,6 +30,7 @@ --background-color: #fff; --text-color: #202020; --link-active: #9E6C00; + --neutral-6: #d9d9d9; --ifm-navbar-background-color: var(--background-color); --ifm-navbar-link-color: var(--text-color); @@ -47,6 +48,7 @@ --ifm-color-content-secondary: var(--text-color); --ifm-pagination-nav-color-hover: var(--link-active); --ifm-font-weight-base: var(--ifm-font-weight-light); + --ifm-heading-color: var(--text-color); } /* For readability concerns, you should choose a lighter palette in dark mode. */ @@ -61,8 +63,7 @@ --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.3); } -@import url('../theme/Navbar/styles.css'); -@import url('../components/Author/styles.css'); +@import url('./navbar.css'); @import url('./sidebar.css'); @import url('./tags.css'); @import url('./pagination-nav.css'); @@ -98,7 +99,7 @@ html[data-theme='dark'] { [data-theme='dark'] .footer { background: transparent; - border-top: 1px solid var(--ifm-toc-border-color); + border-top: 1px solid var(--neutral-6); } .alert { @@ -245,7 +246,6 @@ article h1, .col article header > h2 { background: #ffffff; -webkit-background-clip: text; - -webkit-text-fill-color: transparent; } .pagination-nav__link { diff --git a/src/theme/Navbar/styles.css b/src/css/navbar.css similarity index 100% rename from src/theme/Navbar/styles.css rename to src/css/navbar.css diff --git a/src/css/sidebar.css b/src/css/sidebar.css index 85c839b94..951031015 100644 --- a/src/css/sidebar.css +++ b/src/css/sidebar.css @@ -1,5 +1,6 @@ .menu .menu__list { padding-right: 2rem; + margin-top: 0; } nav>.menu__list { @@ -43,17 +44,23 @@ nav>.menu__list { .theme-doc-sidebar-item-category::after { content: url("../../static/img/chevron-down.svg"); + fill: var(--text-color); position: absolute; - top: 5px; + top: 7px; right: 0; transform: rotate(180deg); + pointer-events: none; } .menu__list-item--collapsed.theme-doc-sidebar-item-category::after { - top: 0; + top: 3px; transform: rotate(0deg); } +.menu__list-item:not(:first-child) { + margin-top: 0; +} + @media (min-width: 997px) { aside .sidebarViewport_node_modules-\@docusaurus-theme-classic-lib-theme-DocRoot-Layout-Sidebar-styles-module { top: 36px; diff --git a/src/css/toc.css b/src/css/toc.css index 01aa426c9..97266b27d 100644 --- a/src/css/toc.css +++ b/src/css/toc.css @@ -13,6 +13,13 @@ padding: var(--ifm-toc-padding-vertical) var(--ifm-toc-padding-horizontal); } + .table-of-contents__link.toc-highlight > code { + color: var(--text-color) + } + .table-of-contents__link.toc-highlight > code:hover{ + color: #000; + } + .table-of-contents__link--active { border-left: 1px solid var(--text-color); } diff --git a/src/theme/Navbar/Content/index.js b/src/theme/Navbar/Content/index.js index 3a7d19cf0..4c5bc78a0 100644 --- a/src/theme/Navbar/Content/index.js +++ b/src/theme/Navbar/Content/index.js @@ -46,7 +46,7 @@ export default function NavbarContent() { // TODO stop hardcoding items? <> -
+
{!mobileSidebar.disabled && } {!searchBarItem && ( diff --git a/src/theme/Navbar/Content/styles.module.css b/src/theme/Navbar/Content/styles.module.css index 2d4d38feb..a7e5e047b 100644 --- a/src/theme/Navbar/Content/styles.module.css +++ b/src/theme/Navbar/Content/styles.module.css @@ -17,7 +17,6 @@ Hide color mode toggle in small viewports color: var(--text-color); text-align: center; - font-size: 14px; font-weight: 400; line-height: 2rem; text-decoration: none;