-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serve basic pages from content-store #3
Conversation
a018e9e
to
4180fac
Compare
@@ -1,5 +1,23 @@ | |||
class ApplicationController < ActionController::Base | |||
# Prevent CSRF attacks by raising an exception. | |||
# For APIs, you may want to use :null_session instead. | |||
include Slimmer::Headers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably best not to include any of the slimmer bits to avoid conflicts as @edds is adding them separately in the work he's doing.
Basic functionality to get an item to the content store and display it on a page. Views are very basic at this point, and controller just passes the content hash directly to the page.
4180fac
to
1416d6f
Compare
"public_updated_at": "2012-12-17T15:45:44.000+00:00", | ||
"publishing_app": "whitehall", | ||
"redirects": [], | ||
"rendering_app": "whitehall-frontend", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was expecting this to be government-frontend
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dsingleton Good catch, updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should only be government-frontend
when the new app is actually rendering the content on GOV.UK. For now, we're pushing case studies into content store with the existing whitehall frontend app as the rendering app. Once we are happy that the frontend app is fully rendering the content, we will switch the rendering app to government-frontend
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted :)
67e88a3
to
92ce3c2
Compare
92ce3c2
to
3461b95
Compare
Serve basic pages from content-store
👍 👍 |
This commit updates the A/B test variant for related links from RelatedLinksABTest2 to RelatedLinksABTest3. This is to support the third iteration of the A/B test which is using a new set of related link data.
Update related links A/B test variant for test #3
This commit adds an additional `C` variant for the upcoming related links A/B test iteration #3. In the previous test we saw some users who had the control variant cookie, yet navigated via the related links which are only shown on the `B` variant. In order to check if there are any problems with our A/B testing framework, in addition to making the data collection easier for later analysis, we are introducing the new `C` variant which will become our test variant. How the variants now work are as follows: - `A` variant: No users should ever end up in this variant, as our CDN will be configured it to assign 0% of users. If users do end up in this variant, we may have issues with our A/B testing framework which will require further investigation. - `B` variant: Our control variant, where related links will not be changed in any way. - `C` variant: Our test variant, where related links will be changed to use our generated links for the sample involved.
Get an item from the content store and display it on a page. Views are very basic at this point, and controller just passes the content hash directly to the page.