Issue with people accessing my gh-pages on Github - html

So I created a gh-pages repo in Github to host my portfolio but whenever someone goes there they have to log into Github to view. Gh-pages are supposed to be public so I have no idea why this is happening. My portfolio is just html and css.
Here's a link to the page : https://github.iu.edu/pages/iford/Portfolio/.

So the github I account I used to setup the portfolio was on a server running Github Enterprise that is why it wasn't truly "public". To fix this I just created a new github account through github (not an enterprise edition) and created a new repo for the page there. Done.

Related

MkDocs site not getting deployed correctly to github pages

I am using Deploy MkDocs action to deploy my site to github pages. After pushing my changes to my master branch the action successfully runs.
However, when I visit my project page link then my site seems to be broken. Any pointers would be of great help.
My repo structure is the following-->
The document contents are inside the "docs" directory.
When I tried to visit the site using my pages link, I can see something like this(I have checked my site locally and it renders properly on my local machine) -->
Add an index.md to the src folder e.g. When build this will produce needed index.html page. Also try to build with: mkdocs build --clean.

How to publish my portfolio consisting of multiple html files in github?

I am trying to publish my portfolio site in github. My folder consists of multiple html files (including homepage.html, projectpage.html, images folder etc.) and css file. However when I publish my site it shows only readme file and not my html web pages. How do I host my portfolio site in github? Please let me know.
Thank you
Using GitHub Pages:
Upload all files to GitHub repository. Name the homepage index.html
In the top horizontal bar, click Settings
Scroll down to GitHub Pages
Under Source, click the dropdown which currently says None ↓ and click Master Branch
Your site is now published at username.github.io/repo
Using Vercel's free plan which gives you a customisable domain:
Upload all files to GitHub repository. Name the homepage index.html
Sign up to Vercel for free using your GitHub account
Go to deploy.new
Under Import Git Repository, click Import on the right of the repository with your website code
Click Select on your personal GitHub account
Click Continue with the root directory selected
Edit your project name if you like. Vercel will automatically detect your project's framework, but you can override the default options if you wish.
Click Deploy
Vercel will start building your site. It will be hosted at projectname.vercel.app

How should I set up my repository using GitHub pages so I can see all the files that the site uses?

Can I set up my repository so that I can see all the files (html and css) that my site uses in the repository while still using the GitHub page generator?
I want to use github.com to maintain my multi page site, without installing Jekyll locally.
After you create your github repo go to the settings and select the option to host from the docs directory I found this to be the best method to host my websites that way you done have to mess with different branches unless your in to that thing.
It is not required for you to use Jekyll I personally have never used it. It is to wordpress esq.
What you can use instead of Jekyll is a static site generator or spa to precompile your website content add the static content to the doc directory and push your repo.
Github will generate a url for your that will also be available in your settings. You can also add custom domains.
I recomd using a static site generator performance and seo is the reason.
If you create a Jekyll website on your local machine in /some/path/website/, initialise your Git repository there:
cd /some/path/website/
git init
Then you can push this to your remote Github repository and all of your files will added and viewable.
I don't think you can initialise a Jekyll website in your remote repository though.
From their documentation:
Jekyll's simplified build process with GitHub Pages is one of the biggest advantages of using Jekyll instead of other static site generators. GitHub Pages manages your site's build process with a single push to your site's publishing branch. This is Jekyll's build process for managing your site:
Push file changes to your pages publishing branch (my emphasis)
GitHub Pages publishes your site.
It turned out that the reason I was not seeing many files was that there was only the index.html that I created using the tutorial at GitHub Pages
The reason I thought there must have been other files was that the theme I picked looked a whole lot better than my helloworld.html

github page doesn't exist (the simple jekyll configuration)

I have the simplest (default jekyll) page on github
https://github.com/pejot/pejot.github.io
When I run locally
bundle exec jekyll serve
it works fine.
but on the github domain
pejot.github.io
it says: "There isn't a GitHub Page here."
what can be a problem that it works locally but not on github? Please take into account that page is basically empty. Is the default one generated by jekyll.
I get it!
github takes gh-pages branch for project page and master for the user one.

Github pages not updating home page

On my octopress/jekyll blog http://www.railsonmaui.com, after I update an article and push to GitHub pages, the specific blog article is updating, but the home page of blog articles is not updating.
Is there any way to tell GitHub pages to clear the cache on the home page?
Any reason the home page is the only page that has this issue?
I experienced the same issue and found that stopping the Jekyll server
Server running... press ctrl-c to stop
and starting it again
jekyll serve
refreshed my home page
Upgrade your code to octopress v3 and now you have the rake deploy which will build, update & deploy your code to github.
You will have to set it up with:
rake setup_github_pages
# Build and deploy the blog to github
rake deploy
Once using this task you site will be updated with the latest code.
did you run jekyll build after updating?