Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 [Feature] : Create Website Sections according to Litepaper #3

Closed
6 tasks
xuelink opened this issue May 25, 2024 · 2 comments · Fixed by #5
Closed
6 tasks

🚀 [Feature] : Create Website Sections according to Litepaper #3

xuelink opened this issue May 25, 2024 · 2 comments · Fixed by #5
Labels
feature New feature or request

Comments

@xuelink
Copy link
Member

xuelink commented May 25, 2024

Is your feature request related to a problem? Please describe.
The current litepaper lacks structured sections, making it difficult to navigate and find information related to the LangX Token and its associated functionalities. This can be frustrating for users trying to understand and utilize the various features.

Describe the solution you'd like
I would like the creation of well-defined sections in the documentation, as outlined in the LangX litepaper. These sections should include:

  • LangX Token
  • Distribution
  • Staking
  • Trading
  • Utility
  • LangX NFT

Each section should have detailed explanations, usage examples, and any relevant information to help users understand and utilize each feature effectively.

Describe alternatives you've considered
An alternative could be to create a single, long page with all the information, but breaking it down into sections would improve readability and navigation.

Additional context
The attached screenshot provides a visual guide for the section layout. Each section should be accessible from a sidebar menu to enhance user experience.

Screenshot 2024-05-25 at 7 44 32 AM

If you want to speed up the process of this issue, please send 🚀 as a reaction.

@xuelink xuelink added the feature New feature or request label May 25, 2024
@xuelink
Copy link
Member Author

xuelink commented May 25, 2024

We should make #1 completed and closed firstly.

@xuelink xuelink linked a pull request Jun 18, 2024 that will close this issue
@xuelink
Copy link
Member Author

xuelink commented Jun 18, 2024

Done w/ #5

@xuelink xuelink closed this as completed Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant