0 comments (0 comments)0 reactions (0 reactions)0 assignees (0 assignees)CSS1,574 stars (1,574 stars)314 forks (314 forks)user submission
Apphelp wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- shell
- Domain
- documentation
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 2
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- basic command line knowledgeunderstanding of HTTPS/SSL
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 75
- Research direction
- The issue requests adding a guide for integrating acme.sh with HyperApp. Since the issue body is empty, the contributor should first examine the existing guide structure, possibly finding a section on SSL or certificates. Then, they need to write clear, step by step instructions for installing acme.sh and using it to obtain TLS certificates, tailored for HyperApp users. The contributor may need to reference acme.sh's official documentation and test the steps. Since no further details are provided, the contributor should propose a draft and ask the maintainer for feedback on scope and format.