Feat/footer #142
Draft
Feat/footer #142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
# Conflicts: # apps/documentation/docusaurus.config.js # apps/documentation/package.json # apps/landing/src/components/layout/index.tsx # packages/ui/src/header/styles.module.scss # pnpm-lock.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
⚠ PLEASE DO NOT DELETE THE TEXT BELOW ⚠
Pull request's description
Add here a description of the modifications you made.
Checklist before merging (please do not edit)
You must review you work before to submit the review to others.
Self-review of your content
Remember the content must be readable and understandable by someone else than yourself.
External reviews of your content
Some guidelines to keep in mind
Colons (:), semi-colons (;), exclamation (!), and interrogation points (?) are not preceded by a space (like full stops and commas). E.g.: Colons!
File names and/or address are put in italic. E.g.: The file main.c.
Functions, variables, or more generally short codes are put between grave accents. E.g.: To obtain
code(), type `code()`.Long codes are put into blocks of code with three grave accent on each side, and the language's name:
```c
// Some C language
```
"Luos engine" has a upper case on the L for "Luos" and lower case on the e for "engine".
We call it "Luos engine" as a proper name, and not "the Luos engine".
Following that fashion, anything that's owned by "Luos engine" implies that we must use
'sas the standard English rule to show the possessive case, e.g. "Luos engine's API".The names pipe, gate, inspector, sniffer, app or application, driver, etc. have a lower case and can be refereed with the determiner
the. E.g.: The inspector.