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

Documenting Joyboy Listing Requirements #40

Open
AbdelStark opened this issue May 16, 2024 · 10 comments
Open

Documenting Joyboy Listing Requirements #40

AbdelStark opened this issue May 16, 2024 · 10 comments
Assignees

Comments

@AbdelStark
Copy link
Contributor

Title: Comprehensive Documentation for Joyboy Listings

Objective: To systematically identify all potential platforms and directories where Joyboy needs to be listed and document the requirements and processes for each listing.

Background:
Joyboy is a decentralized social platform built using the Nostr protocol and enhanced by Starknet's account abstraction. Proper listing on relevant directories and platforms is crucial for visibility and integration within the wider ecosystem. This task involves researching and documenting all the necessary steps to ensure Joyboy is listed appropriately across various platforms.

Task Details:

  1. Identify Listing Locations:

    • Review and list all potential websites, directories, and platforms where Joyboy elements (such as clients and relays) need to be referenced.
    • Examples include:
      • Listing as a Nostr client on the Nostr website clients page.
      • Adding the Joyboy relay at nostr.joyboy.community to directories like nostr.watch which lists Nostr relays.
  2. Research Listing Requirements:

    • For each identified location, research and document specific requirements for getting listed. This may include forms to fill out, information to provide, or contacts to reach out to.
    • Document any costs, prerequisites, and timelines associated with each listing.
  3. Documentation:

    • Create a detailed markdown file titled joyboy-listing.md.
    • Store this file under resources/branding/listing/ in the repository.
    • The document should be structured to include:
      • Platform/Directory Name: Description and relevance to Joyboy.
      • Listing Requirements: Detailed steps and requirements for listing.
      • Contact Information: If applicable, include contact information or submission links.
      • Additional Notes: Any other relevant information or strategic considerations.
  4. Expected Outcome:

    • A comprehensive guide that will serve as a reference for getting Joyboy listed across all relevant platforms, enhancing its visibility and integration within the ecosystem.

Acceptance Criteria:

  • The markdown document must be clear, well-organized, and easy to navigate.
  • All information should be accurately researched and referenced.
  • The guide should cover all necessary platforms and provide detailed steps for the listing process.

Please ensure the documentation is thorough and consider potential updates as platforms evolve. This will be a critical resource for our marketing and partnership teams to extend Joyjoy's reach and utility.

@kateberryd
Copy link
Contributor

Can I contribute on this @AbdelStark

@mubarak23
Copy link
Contributor

@AbdelStark kindly assign

@AbdelStark
Copy link
Contributor Author

Can I contribute on this @AbdelStark

Are you in the telegram group ?

@kateberryd
Copy link
Contributor

Yes @AbdelStark

@AbdelStark
Copy link
Contributor Author

kateberryd

ohhh you are Temi Hardhek on telegram ?

@TEMHITHORPHE
Copy link

@t0rp3d0 here

@kateberryd
Copy link
Contributor

No, @zintarh

@AbdelStark
Copy link
Contributor Author

No, @zintarh

Gotcha. ok sorry then I already assigned to @TEMHITHORPHE and @mubarak23 since we discussed about it on telegram.
Bare with us and be ready to take something else on Joyboy!

@kateberryd
Copy link
Contributor

Alright. Thank you @AbdelStark

@Constantine234
Copy link

can i contribute to this too @AbdelStark

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants