Skip to content

feat: Create landing webpage with Firebase Remote Config–driven Play Store link#271

Draft
Copilot wants to merge 2 commits intodevelopfrom
copilot/create-webpage-playstore-link
Draft

feat: Create landing webpage with Firebase Remote Config–driven Play Store link#271
Copilot wants to merge 2 commits intodevelopfrom
copilot/create-webpage-playstore-link

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 28, 2026

Adds a static landing page at apps/webpage/ deployable to https://zandercowboy.github.io/multichoice/. The Google Play button URL is driven at runtime by Firebase Remote Config (play_store_url key), with a hard-coded fallback.

New files

  • apps/webpage/index.html – Single-file landing page (HTML/CSS/ES module JS). Fetches play_store_url from Firebase Remote Config via the JS SDK CDN; falls back to the static Play Store URL on failure.
  • apps/webpage/assets/ – App icon + screenshots sourced from the existing play_store/ directory.
  • apps/webpage/README.md – Documents Remote Config key, deployment, and required GitHub Secrets.

CI/CD

  • .github/workflows/pages_workflow.yml – Deploys apps/webpage/ to gh-pages on push to main (path-filtered to apps/webpage/**). Injects Firebase web-app config from six GitHub Secrets via sed before publishing with peaceiris/actions-gh-pages@v4.

Flutter model update

  • FirebaseConfigKeys – Added playStoreUrl('play_store_url') so the Flutter app and the webpage share the same Remote Config key.

Firebase Remote Config integration

rc.defaultConfig = { play_store_url: FALLBACK_URL };
await fetchAndActivate(rc);
const url = getString(rc, 'play_store_url') || FALLBACK_URL;
document.getElementById('play-link').href = url;

Required one-time setup

  1. Add six FIREBASE_* GitHub Secrets (see apps/webpage/README.md).
  2. Enable GitHub Pages → source: gh-pages branch.
  3. Add a play_store_url string parameter in Firebase Remote Config.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • orpetron.com
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>FEAT: Create Webpage pointing to Playstore</issue_title>
<issue_description># Webpage

  • Create a simple webpage in the repo that can be accessed with https://zandercowboy.github.io/multichoice/ or multichoice.zanderkotze.co.za

  • Here is an example of a desired view: https://orpetron.com/sites/lazy-ant/

  • Since we are using a monorepo, this site's code needs to be added under apps.

  • It contains an image of the app, with a description, and a Google Play button pointing to Google Play Store.

  • Set up gh-pages and a protected branch.

  • The Google Play button link needs to be remotely configured using Firebase Remote Config. Add Remote Config to Codebase #118</issue_description>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

… integration

Co-authored-by: ZanderCowboy <59666243+ZanderCowboy@users.noreply.github.com>
Copilot AI changed the title [WIP] Add webpage with Google Play button to repository feat: Create landing webpage with Firebase Remote Config–driven Play Store link Feb 28, 2026
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants