logseq / logseq/sites

Does not work without JavaScript

Open
#29 4 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
CSS
Stars
15
Forks
14
Avg merge
1m
Merged PRs (30d)
1

Description

`w3m https://logseq.com/` gets a user a blank page. Users with scripts disabled by default for security, also get nothing.

If the goal of a homepage is to be accessible and provide basic information to users, there shouldn't be a scripting requirement—nothing requires interactivity (use case tabbing, could just show all with scripts disabled). This tends to hurt SEO as well (only the Googlebot executes JavaScript).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the blank page at https://logseq.com/ with JavaScript disabled, using w3m or a browser setting. Inspect the homepage implementation to identify where its basic information is generated. Done means users can read the homepage's essential information and access its use-case content without requiring JavaScript.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.