Cloudflare Pages Function | JavaScript (Backend) Dev -- 3
Budget: €36 – €0 EUR
We are a national tourism organisation currently setting up a A/B-testing 'framework' for landingpages (custom subdomain based). Cloudflare Pages seems to be a perfect fit in regards to our requirements. We have managed to get a first dummy instance up and running involving middleware.js (compare https://developers.cloudflare.com/pages/how-to/use-worker-for-ab-testing-in-pages/ -> last script at the bottom of the page). We would like to enhance the involved Pages Function (middleware.js) by a few set requirements. In the following the foreseen project steps and requirements:
* Initial alignment call (via MS Teams): Talk through the requirements. Clarify the dummy instance setup including access topics. Set the timeline for the project. Varia topics and questions to be clarified.
* Verification of middleware.js upfront micro-adjustment: To get middleware.js up&running a micro-adjustmemnt seemed to be needed. Requirement: Review and verification of this micro-adjustment.
* middleware.js script enhancement I:
i) If feasible without a redirect, the test (B) page-version shall be located in a dedicated subfolder and the subfolder is displayed in the URL. If not feasible without a redirect, both page-versions (A & B) are to be located in the root-folder as pre-given in middleware.js. In both cases the name of the two pages (without extension) needs to be displayed in the URL.
Schematically: A: 1.html resp. B: 2.html // Subfolder-approach: .../1 resp. .../test/2 // Root-approach: .../1 resp. .../2
ii) If a page-version is dedicatedly called (e.g. A: .../1), the corresponding page shall be displayed indepedent of any pre-set "ab-test-cookie" value.
iii) Any query-paramters are strictly perserved. Schematically: …/?foo=bar&bar=foo#nav -> A: …/1?foo=bar&bar=foo#nav
* middleware.js script enhancement II (as an optional add-on to I): As an alternative to a (B) page-version, there is an option to point to an entire URL on a different subdomain (redirect required we guess).
* middleware.js script enhancement III: The "ab-test-cookie" lifetime is set to a dedicated value (Max-Age or Expires).
* Project acceptance call (via MS Teams): Talk through the scripts (to be deployed upfront on dummy instance). Estimation of effort required: 1 hour
* In reserve (to be taken into account in your bid): 1-2 hours
Acceptance criteria: The provided scripts are briefly commented, tested and running on dummy instance.
Last but not least: In your bid please outline shortly your previous track record in terms of Cloudflare Pages Functions and/or Workers as well as your Javascript (Backend) savviness.
Thanks!
* Initial alignment call (via MS Teams): Talk through the requirements. Clarify the dummy instance setup including access topics. Set the timeline for the project. Varia topics and questions to be clarified.
* Verification of middleware.js upfront micro-adjustment: To get middleware.js up&running a micro-adjustmemnt seemed to be needed. Requirement: Review and verification of this micro-adjustment.
* middleware.js script enhancement I:
i) If feasible without a redirect, the test (B) page-version shall be located in a dedicated subfolder and the subfolder is displayed in the URL. If not feasible without a redirect, both page-versions (A & B) are to be located in the root-folder as pre-given in middleware.js. In both cases the name of the two pages (without extension) needs to be displayed in the URL.
Schematically: A: 1.html resp. B: 2.html // Subfolder-approach: .../1 resp. .../test/2 // Root-approach: .../1 resp. .../2
ii) If a page-version is dedicatedly called (e.g. A: .../1), the corresponding page shall be displayed indepedent of any pre-set "ab-test-cookie" value.
iii) Any query-paramters are strictly perserved. Schematically: …/?foo=bar&bar=foo#nav -> A: …/1?foo=bar&bar=foo#nav
* middleware.js script enhancement II (as an optional add-on to I): As an alternative to a (B) page-version, there is an option to point to an entire URL on a different subdomain (redirect required we guess).
* middleware.js script enhancement III: The "ab-test-cookie" lifetime is set to a dedicated value (Max-Age or Expires).
* Project acceptance call (via MS Teams): Talk through the scripts (to be deployed upfront on dummy instance). Estimation of effort required: 1 hour
* In reserve (to be taken into account in your bid): 1-2 hours
Acceptance criteria: The provided scripts are briefly commented, tested and running on dummy instance.
Last but not least: In your bid please outline shortly your previous track record in terms of Cloudflare Pages Functions and/or Workers as well as your Javascript (Backend) savviness.
Thanks!