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
Alt Text: This banner image shows a moonscape scene with two Ocotcats standing on the moon posing with the earth in the background. It includes the text "Pages Check-in" in the upper left corner.
Hello Pages community! Let’s do a mid-summer check-in
🧑💻 August Community Topic
What is your favorite front-end tech stack
Looking for a way to connect with the community? Write a quick “blog style” discussion about your favorite Front End Tech Stack and how you use it. Show off your work and methods, share your workflow, get feedback, and grow together!
Suggested content:
Share what you’ve built
Why you are using your selected stack
Likes and dislikes of the stack
What was your deployment experience (with Pages or other)
What you learned
Tips for other community members
Ask for feedback / help on your project
🎉 Shout Out to Our Top Contributors in July
Thank you to all of our great contributors! These were the most active contributors in Pages last month.
@MaggieWillDesign and @CleverLemming1337 took on a tricky 404 error where it seemed that new files pushed to the repo did not show up in the deployment. It turns out they needed a .nojekyll file to keep jekyll from renaming files! Check out the Deployment
@SuhainaFathimaM Faced down the Dangerous Site flag from Google, with help from @davevad93, @Damandeep-S, @knarrff, and @aishamc. Look out for naming conventions in your repo names; using names like netflix_clone can get your domain flagged (<username>.github.io) by Google. This results in all deployments associated with that domain being labeled as dangerous.
GitHub Pages uses jekyll (behind the scenes) to deploy every project. Jekyll likes to rename some files to comply with its file structure. This can cause problems for projects not built with jekyll.
TL;DR: If you are not using jekyll in your project, and you are not using the Actions Build Method, add an empty file named .nojekyll to your main branch (or whichever branch you run your build from).
If you are not using a Front End Framework (just plain .html, .css, .md, and .js files) still use a .nojekyll file in your main branch to avoid any issues.
If you are getting odd 404s in your deployed application (and are not using jekyll), add a .nojekyll file for good measure.
GitHub Actions Deployment
Github Actions is the new default method of deployment for Pages (Deploy from a branch is still available for now)
Using Actions for deployment brings your app into the CI/CD world
Any push to main will automatically update your deployment. Or you can customize your workflow any way you want!
PagesHost a static website, right from your repoCommunity Check-InUpdates & News from GitHub Community Managers
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello Pages community! Let’s do a mid-summer check-in
🧑💻 August Community Topic
What is your favorite front-end tech stack
Looking for a way to connect with the community? Write a quick “blog style” discussion about your favorite Front End Tech Stack and how you use it. Show off your work and methods, share your workflow, get feedback, and grow together!
🎉 Shout Out to Our Top Contributors in July
Thank you to all of our great contributors! These were the most active contributors in Pages last month.
@akruse10 and @knarrff took on some 404 errors involving DNS settings, DNS verification / DNS takeover, and Create-React-App configuration for Gh-Pages in a 3 week battle! View the hard-fought victory deployment.
@MaggieWillDesign and @CleverLemming1337 took on a tricky 404 error where it seemed that new files pushed to the repo did not show up in the deployment. It turns out they needed a
.nojekyll
file to keep jekyll from renaming files! Check out the DeploymentNotServedByPagesError
and SquareSpace. SquareSpace now defaults to thewww
variant of DNS naming schemas. So even though a user may expect their domain name to beexample.com
, with SquareSpace it is actuallywww.example.com
; this is super important when selecting theCustom Domain Name
setting inPages
settings.Dangerous Site
flag from Google, with help from @davevad93, @Damandeep-S, @knarrff, and @aishamc. Look out for naming conventions in your repo names; using names likenetflix_clone
can get your domain flagged (<username>.github.io) by Google. This results in all deployments associated with that domain being labeled as dangerous.🆕 What’s New
Sunsetting GitHub Pages’ legacy worker
.nojekyll
.nojekyll
to yourmain
branch (or whichever branch you run your build from)..nojekyll
file in yourmain
branch to avoid any issues..nojekyll
file for good measure.GitHub Actions Deployment
Github Actions is the new default method of deployment for Pages (Deploy from a branch is still available for now)
main
will automatically update your deployment. Or you can customize your workflow any way you want!Beta Was this translation helpful? Give feedback.
All reactions