-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Epic] 4.1: Basic front end for node operator #100
Comments
Related: https://github.com/waku-org/waku-frontend |
Weekly update: |
@chair28980 keeping it open as per waku-org/nwaku#2223 (comment) |
Closing per status-im/nim-presto#68 (comment) |
Reopening since the frontend is not live in nwaku compose nor has the requested features. See deliverables section. |
Closing as this is in https://github.com/waku-org/nwaku-compose |
Epic label:
E:4.1: Basic front end for node operator
Summary
Context and Need
Waku nodes currently lack a user-friendly interface, making it difficult for non-technical users to interact with the network.
Objective
Provide a simple and non-technical means for users to interact with Waku nodes, enhancing usability, especially for workshops and new users.
Proof of concept
The design for this front end should be developed at a proof of concept level.
Deliverables
D1. Dockerized frontend with a nice design and some waku branding. Avoid using fancy frameworks that soon become obsolete. With the following features:
Integrated with nwaku-compose so that after "docker-compose up -d" the front end is available to the user.
The front end allows to publish a message to a given content topic, inputting a set of fields. Using the REST API. Can take UTF-8 string or binary payload in hex format (using post_waku_v2_relay_v1_message)
The front end allows to subscribe to a given content topic, and messages are displayed real-time in there.
Acceptance Criteria
RAID
Risks
Assumptions
Issues
Dependencies
Tasks
js-waku:
@waku/create-app
waku-frontend#8nwaku:
The text was updated successfully, but these errors were encountered: