You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the competition days themselves we have a custom version of the homepage which is managed in https://github.com/srobo/competition-website/. However we're also likely to have a bit more traffic in the week or so leading up to the competition and afterwards too -- both from press we're inviting to the event and from parents and other people that competitors are telling about the event.
It therefore might be good to have a variant of the homepage which makes more of the event. Broadly I'm imagining the messaging beforehand would cover two things:
that the event is the culmination of the year's work
advertising that the website homepage will have live updates once the competition is underway
The messaging afterwards would have a slightly different approach:
that the event is the culmination of the year's work
prominently celebrating the event (maybe featuring the blog post)
This would likely fit into the existing template rather than being a whole separate page, though it might make sense for it to be a separate include file so that enabling/disabling it is easy.
The text was updated successfully, but these errors were encountered:
PeterJCLaw
changed the title
(Idea) Customise the homepage in the days leading up to the competition
(Idea) Customise the homepage in the days either side of the competition
Apr 21, 2022
For the competition days themselves we have a custom version of the homepage which is managed in https://github.com/srobo/competition-website/. However we're also likely to have a bit more traffic in the week or so leading up to the competition and afterwards too -- both from press we're inviting to the event and from parents and other people that competitors are telling about the event.
It therefore might be good to have a variant of the homepage which makes more of the event. Broadly I'm imagining the messaging beforehand would cover two things:
The messaging afterwards would have a slightly different approach:
This would likely fit into the existing template rather than being a whole separate page, though it might make sense for it to be a separate
include
file so that enabling/disabling it is easy.The text was updated successfully, but these errors were encountered: