Move Docs to HandyOrg.github.io repo
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, markdown
- Domain
- devops, documentation
Research direction
Start by reviewing the repository's docs folder and the Hexo GitHub Pages documentation linked in the issue. Compare the sample .github/workflows/pages.yml workflow and determine how the docs content should move to HandyOrg.github.io. Done means the Markdown source is in the new repository and GitHub Actions builds and deploys the site without manually generating or uploading the public folder.
Written by the indexing model from the issue text.
Description
Feature request type
enhancement
Is your feature request related to a problem? Please describe
By moving the contents of the docs folder to the HandyOrg/HandyOrg.github.io repository, GitHub Actions can automatically build and deploy the Hexo site. In this setup, you only need to edit the Markdown (.md) files and push your changes to the repository—everything else, including generating and uploading the public folder, is handled automatically by the GitHub Action. This simplifies the workflow and removes the need for manual deployment.
Describe the solution you'd like
Hexo Doc:
https://hexo.io/docs/github-pages
my Sample:
https://github.com/ghost1372/ghost1372.github.io
https://github.com/ghost1372/ghost1372.github.io/blob/master/.github/workflows/pages.yml
Describe alternatives you've considered
No response
Additional context
No response
- Dominant language
- C#
- Stars
- 7.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HandyOrg/HandyControl
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
HandyOrg/HandyControl#1818 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
HandyOrg/HandyControl#1809 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
HandyOrg/HandyControl#1820 ·
-
不能够独立的引入用户认为需要的部分Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
HandyOrg/HandyControl#1816 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
HandyOrg/HandyControl#1813 ·
All issues in HandyOrg/HandyControl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PCL-Community/PCL-CE#3652 ·
Maintainers usually reply within 1 day
-
area:frontend bug FE P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
klasolsson81/jobbliggaren#2010 ·
Maintainers usually reply within 1 day
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
area: homeblaze type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
RicoSuter/Namotion.Interceptor#630 ·
Maintainers usually reply within 1 day
-
Akka.Hosting enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100