Comments (6)
To ensure that the program works as expected, you will need to do a few extra steps after forking.
- Configure the URL for the project in the settings of the github repository, so that others can access the blog through that URL.
- Go to
Actions
settings and turn on the workflow run permission manually. As a protection measure, the forked project will not trigger actions by default. It doesn't take much work, you just need to press the activate button in order to start.
After startup, the readme.md
in the root directory will not be displayed in the website. The reason you can see a readme file on the website is because there is another copy of readme.md
in the /blog
directory. The logic is that the website will show all the articles in the /blog
directory, following the corresponding tree structure.
If you have further questions, don't hesitate to let me know.
from goodmanwen.github.io.
I run it successfully ,but also show the readme file.
and if I delete the readme.md in the root directory that will display the 404 page.
I have only revised the following.
from goodmanwen.github.io.
The Github pages feature comes with a set of UI logic natively, which allows users to display pages without customizing their appearance, also this means that if you are trying to use html for customization then you will need to do additional setup.
I've visited your project and the reason your pages only shows the readme.md
under /root
directory is because you have not done pages's futher settings, this makes the pages interpreter not connect to the specified page style file, you need to modify it to achieving the expected outcome. Of course, the most recommended way is to fork this project directly, so that all the configuration is inherited by default and you don't need to do any additional configuration.
from goodmanwen.github.io.
I made it. Thank you for your help.
from goodmanwen.github.io.
I've visited your project and the reason your pages only shows the readme.md under /root directory is because you have not done pages's futher settings, this makes the pages interpreter not connect to the specified page style file,-----我也遇到了同样的问题,仅展示了根root的readme界面,这里提到的pages's futher settings 是指什么,我已经更改了[AutoUpdate.yml]文件中的仓库引用,指向了我自己fork后的仓库
from goodmanwen.github.io.
问题已经解决了,我更改了page中 jekyll的路径,使用了docs路径,解决了该问题
from goodmanwen.github.io.
Related Issues (5)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from goodmanwen.github.io.