You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because if you don't have, well, this repo can simply be turned into a website right away. Others will discover this project in that website.
Steps:
Go to Settings and look for GitHub Pages, scroll down. That's almost at the bottom.
You will see there: Branch:none, so you should change that to master because you have a README.md file in the master repo. This will be your page. Click Save first.
Then click Choose a theme, you select a predefined theme of your site.
Visit your site now! The URL will be https://charignon.github.io/github-review.
If you were amazed by that, simply read the documentation about GitHub Pages.
The text was updated successfully, but these errors were encountered:
I feel like the emacs community discovers packages through blog articles and reddit. This package is mentioned by several blogs including Sacha Chua's and was mentioned on reddit. If you feel like a site would help for discoverability within the community, please upvote this comment and I will do it.
Yup, it really helps because those big companies like Twitter, their Bootstrap project, they have the website solely dedicated for the project and its documentation. Thanks a lot for the response.
Hi there.
Is there a website for this repo?
Because if you don't have, well, this repo can simply be turned into a website right away. Others will discover this project in that website.
Steps:
Go to Settings and look for
GitHub Pages
, scroll down. That's almost at the bottom.You will see there:
Branch:none
, so you should change that tomaster
because you have aREADME.md
file in the master repo. This will be your page. ClickSave
first.Then click
Choose a theme
, you select a predefined theme of your site.Visit your site now! The URL will be
https://charignon.github.io/github-review
.If you were amazed by that, simply read the documentation about GitHub Pages.
The text was updated successfully, but these errors were encountered: