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

[gnoweb] Possible improvements #2752

Open
leohhhn opened this issue Sep 2, 2024 · 1 comment
Open

[gnoweb] Possible improvements #2752

leohhhn opened this issue Sep 2, 2024 · 1 comment
Labels
🌍 gnoweb Issues & PRs related to gnoweb and render

Comments

@leohhhn
Copy link
Contributor

leohhhn commented Sep 2, 2024

Description

This is a small compilation issue on some thoughts I had regarding how gnoweb can be improved, in relation to its approaching revamp. Some of these items might have been mentioned in previous issues, and some of these might be good for a v2, v3, etc. instead of the initial revamped version.

  • If there is a README.md inside a package, provide raw + rendered display options
  • Code viewer:
    • Adding line numbers to code
    • Adding copy all code button to each file
    • Add click-to-see definition within gnoweb (might be hard)
    • Permalinks to code lines (like on GH)
    • Properly render < & > signs (ie here, DeleteTodo < would be cool if I could link to the function here :)
  • Check all functionalities on all OS platforms (happy to provide manual testing)
  • Make the [source] page more useful:
    • When showing the file list page of a package/realm, display metadata, such as:
      • Publisher & published date/block,
      • How many packages are using it; might be difficult without proper tools, but possibly could be something provided by the tx-indexer?
      • Godoc of the package, if it exists
    • If we implement something like gno pull, show gno pull pkgpath command for that package
    • Possibly provide "download zip/package" functionality - might be a bad idea; not sure. WDYT?
  • u/handle - possibly also add tree-like display of user-only namespaces (ie r/leon, because it's hard to paginate/display large amount of tree nodes) (very big nice-to-have)
  • handle {p,r}/namespace/ page - nspkg query: [gnoland] Add nspkgs (namespace packages) ABCI query #2383
  • Different code color theme options (nice to have, but please change the current one :)
  • Think about standardizing the link structure, so other apps can understand the standard and use it as well: [gnoweb/realms] Standardize hyperlink structure #2602
  • Work on better content organization for the landing/home page (gno.land). I'm writing an issue up on this currently, and I think this is a good time to think about this and try to improve the current state. In practice, this is a mix of figuring out what we want, what MD components we can utilize, and refactoring the r/gnoland/home content.
  • If a realm does not have a Render() function, make a nicer display showing it (instead of just "no render function provided").

Related: #2746, #2383, #2189, #2687, #2602

cc @alexiscolin @gfanton @moul

@leohhhn leohhhn added the 🌍 gnoweb Issues & PRs related to gnoweb and render label Sep 2, 2024
@leohhhn
Copy link
Contributor Author

leohhhn commented Sep 4, 2024

Adding to this; also give some love to the mobile version. Make source code scrollable sideways, which currently isn't the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌍 gnoweb Issues & PRs related to gnoweb and render
Projects
Status: Triage
Development

No branches or pull requests

1 participant