No navigation link for docs, no sitemap
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css
- Domain
- web-dev
Research direction
Start by locating the website's navigation and footer entry points, since the issue does not name specific files. Add an easy-to-find docs link in the navigation and a clear sitemap at the bottom of the site. Done means both navigation paths are visible and work as intended.
Written by the indexing model from the issue text.
Description
Hi.
I've recently started using logseq and I'm intrigued by it to say the least :)
Something that really caught my attention an bothered me on the website is that the docs are so hard to find, the link to the docs is on the 3rd page and you have to scroll down and pay attention to find it.
I think a link for docs should be in the navigation menu.
also at the bottom of the site, there should be a clear sitemap for easy navigation and understanding the sites structure.
I can do these and open a PR if you agree.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 14
- Avg merge
- 2m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/sites
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
chingu-voyages/V62-tier3-team-33#275 ·
Maintainers usually reply within 1 day
-
area/dashboard kind/bug QA/dev-automation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rancher/dashboard#19379 · 2 comments ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rjsf-team/react-jsonschema-form#5439 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day