NEW
Font size
WorksheetsModule 5: GitHub Pages & Wikis
Total questions: 20
Worksheet time: 7mins
What is the primary purpose of GitHub Pages?
To host dynamic server-side applications
To publish static websites and documentation directly from a repository
To manage repository permissions
To store large binary assets
Which of the following is a common use case for GitHub Pages?
Running background jobs
Hosting project documentation and guides
Managing CI/CD secrets
Monitoring application performance
How does GitHub Pages fit into the development workflow?
Documentation is managed separately from code
Documentation updates bypass review processes
Documentation evolves alongside code using pull requests
Documentation must be manually uploaded to servers
The approach of treating documentation with the same rigor as code is known as:
Infrastructure-as-Code
Docs-as-Code
Content-as-a-Service
Continuous Documentation
What is the first stage in the GitHub Pages development workflow?
Deploy documentation
Review changes
Make documentation changes
Approve changes
What action signals that documentation changes are ready for review?
Merging to the main branch
Enabling GitHub Pages
Opening a Pull Request
Assigning a reviewer
What happens automatically after approved documentation changes are merged?
Manual deployment is required
The documentation is archived
GitHub Pages builds and publishes the site
A new repository is created
Why is version control important for documentation in GitHub Pages?
It reduces file sizes
It allows automatic translations
It tracks changes and allows rollbacks
It disables public access
One key advantage of GitHub Pages is that:
It requires third-party hosting services
It eliminates the need for pull requests
It acts as both host and storage for documentation
It supports only private repositories
Why are custom domains important for GitHub Pages sites?
They reduce repository size
They provide a professional identity and easier access
They disable public access
They are required to enable Pages
Which benefit is provided by securing GitHub Pages with HTTPS?
Faster repository cloning
Encrypted communication and protection from tampering
Automatic content translation
Reduced build times
How does GitHub manage HTTPS certificates for Pages sites?
Teams must upload certificates manually
Certificates are purchased separately
GitHub provides automatic certificate management
HTTPS is optional and unmanaged
What is the primary purpose of GitHub Wikis?
Hosting static websites
Running CI pipelines
Creating collaborative project documentation
Managing repository issues
Which of the following is a common use case for GitHub Wikis?
Binary file storage
Architecture and design explanations
Application deployment
Dependency management
Which practice helps manage wiki content effectively?
Allowing unrestricted changes without review
Keeping wiki updates independent of code changes
Organising content into clear sections and pages
Avoiding ownership of documentation
Why should documentation be linked to repositories and pull requests?
To increase repository size
To ensure documentation and code updates happen together
To limit reviewer access
To prevent collaboration
How do pull requests help maintain documentation quality?
By bypassing reviews
By enforcing automated translations
By enabling structured review and discussion
By locking documentation files
Which principle supports a culture of collaborative documentation?
Only senior developers update documentation
Documentation is optional
Treat documentation changes with the same importance as code
Documentation should be written after release only
What is a sustainability practice for long-term documentation health?
Avoid reviewing documentation
Standardise documentation structure and naming
Store documentation outside the repository
Update documentation randomly
Where do you enable GitHub Pages for a repository?
Issues > Pages
Actions > Deploy
Settings > Pages
Wiki > Configuration
