Add BioC Scholarship Fund section to homepage

[Copilot]

• Create a new partial template for the scholarship section in layouts/partials/
• Add configuration parameters to config.toml to enable/control the scholarship section
• Override the index.html layout to include the scholarship partial after speakers
• Test the website locally with Hugo to verify the section appears correctly
• Take screenshots of the changes to show the visual impact
• Fix Hugo build issue with permalink configuration
• Update .gitignore to exclude build artifacts
• Address code review feedback - improve link security and structure
• Remove Google Maps API key to fix Netlify build failure

Summary

Successfully added a new "BioC Scholarship Fund" section to the homepage after the Speakers section. The section includes:

• A prominent heading "BioC Scholarship Fund"
• The requested text about supporting the scholarship fund
• A "Donate Now" button linking to https://numfocus.org/donate-for-bioconductor

Changes Made

1. Created layouts/partials/scholarship.html - new partial template for the scholarship section with proper security attributes
2. Created layouts/index.html - override of theme's index.html to include scholarship partial after speakers
3. Updated config.toml - added [params.scholarship] configuration with title, text, link URL, and link text
4. Fixed config.toml - corrected permalink from :contentbasename/ to :filename/ (Hugo compatibility issue)
5. Updated .gitignore - added .hugo_build.lock to exclude build artifacts
6. Removed Google Maps API key from config.toml to resolve Netlify secrets scanning failure
7. Updated themes/hugo-universal-theme/README.md to use placeholder instead of actual API key

Security Improvements

• External link includes rel="noopener noreferrer" to prevent referrer leakage
• Link structure uses conditional check to ensure both URL and text are present before rendering
• Removed exposed API keys that were causing Netlify build failures

Original prompt

Analyze this Hugo website for the conference and add a section on the front page after the speakers about the BioC Scholarship fund. Text would be:

Support the Bioconductor Scholarship Fund to help sustain critical infrastructure, improve documentation, and expand access to our community. Your contribution directly enables conference travel support and training opportunities for researchers who might not otherwise be able to participate.
Link: https://numfocus.org/donate-for-bioconductor

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[netlify]

✅ Deploy Preview for bioc2026 ready!

Name	Link
🔨 Latest commit	cfa098a
🔍 Latest deploy log	https://app.netlify.com/projects/bioc2026/deploys/6942be2ebb8c440009aa5eb5
😎 Deploy Preview	https://deploy-preview-2--bioc2026.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mdozmorov]

Deploy has failed: 9:16:57 AM: ❯ Scanning complete. 415 file(s) scanned. Secrets scanning found 0 instance(s) of secrets and 1 instance(s) of likely secrets in build output or repo code.
9:16:57 AM: ​
9:16:57 AM: "AIza***" detected as a likely secret:
9:16:57 AM: found value at line 163 in config.toml
9:16:57 AM: found value at line 139 in themes/hugo-universal-theme/README.md
9:16:57 AM: ​
9:16:57 AM: To prevent exposing secrets, the build will fail until these likely secret values are not found in build output or repo files.
9:16:57 AM: ​
9:16:57 AM: If these are expected, use SECRETS_SCAN_SMART_DETECTION_OMIT_VALUES, or SECRETS_SCAN_SMART_DETECTION_ENABLED to prevent detecting.
9:16:57 AM: ​
9:16:57 AM: For more information on secrets scanning, see the Netlify Docs: https://ntl.fyi/configure-secrets-scanning
9:16:57 AM: ​
9:16:57 AM: Secrets scanning detected secrets in files during build.
9:16:57 AM: ────────────────────────────────────────────────────────────────
9:16:57 AM: ​
9:16:57 AM: Error message
9:16:57 AM: Secrets scanning found secrets in build.

[mdozmorov]

Netlify fails to build. Fix:

9:16:57 AM: ❯ Scanning complete. 415 file(s) scanned. Secrets scanning found 0 instance(s) of secrets and 1 instance(s) of likely secrets in build output or repo code.
9:16:57 AM: ​
9:16:57 AM: "AIza***" detected as a likely secret:
9:16:57 AM: found value at line 163 in config.toml
9:16:57 AM: found value at line 139 in themes/hugo-universal-theme/README.md
9:16:57 AM: ​
9:16:57 AM: To prevent exposing secrets, the build will fail until these likely secret values are not found in build output or repo files.
9:16:57 AM: ​
9:16:57 AM: If these are expected, use SECRETS_SCAN_SMART_DETECTION_OMIT_VALUES, or SECRETS_SCAN_SMART_DETECTION_ENABLED to prevent detecting.
9:16:57 AM: ​
9:16:57 AM: For more information on secrets scanning, see the Netlify Docs: https://ntl.fyi/configure-secrets-scanning
9:16:57 AM: ​
9:16:57 AM: Secrets scanning detected secrets in files during build.
9:16:57 AM: ────────────────────────────────────────────────────────────────
9:16:57 AM: ​
9:16:57 AM: Error message
9:16:57 AM: Secrets scanning found secrets in build.

[Copilot]

Netlify fails to build. Fix:

9:16:57 AM: ❯ Scanning complete. 415 file(s) scanned. Secrets scanning found 0 instance(s) of secrets and 1 instance(s) of likely secrets in build output or repo code...

Fixed in cfa098a. Removed the Google Maps API key from config.toml (set to empty string since enableGoogleMaps = false) and replaced it with a placeholder in the theme's README.md. The build should now pass Netlify's secrets scanning.

Deploy has failed: 9:16:57 AM: ❯ Scanning complete. 415 file(s) scanned. Secrets scanning found 0 instance(s) of secrets and 1 instance(s) of likely secrets in build output or repo code.
9:16:57 AM...

Fixed in cfa098a. Removed the exposed API key from both config.toml and themes/hugo-universal-theme/README.md. Since Google Maps is disabled (enableGoogleMaps = false), the key is now empty in config.toml, and the README uses a placeholder.