Hello @DMburugu! By landing page, are you referring to an event page? And are there some examples you can provide of the landing pages that Growth has created in the past and the context/story behind their use? This would help us understand the request a bit better. Thank you in advance!

"Landing page" in this context refers to a customized version of Special:CreateAccount page with specific messaging and visuals based on where the user signed up from (via donor email, during a campaign event etc). So far these customizations are treated as one-off changes, meaning that we don't have a content management system and each version requires code changes.

Campaign	URL	Screenshot	Use case
None (default Special:CreateAccount)	enwiki		Generic
JOSA Jan 2022	arwiki		Event
GLAM Latin America	eswiki		Event
Recurring Donor	enwiki		Email
Growth Advancement	eswiki		Email
Growth Marketing Video	enwiki		Ad

Hey @ifried, Does the response from @mewoph clarify your question.

Hello, @DMburugu & @mewoph , thanks for clarifying. Two follow-up questions:

1. Are there any stakeholders currently awaiting any new work/releases/bug fixes on this feature? The Campaigns team is pretty busy now, and we don't have any capacity to take on any more feature work in our current roadmap (and that won't change for a while).
2. Is there any urgency regarding when we provide a response?

Once we have more information, we will discuss this and get back to you. Thanks!

1. Are there any stakeholders currently awaiting any new work/releases/bug fixes on this feature? The Campaigns team is pretty busy now, and we don't have any capacity to take on any more feature work in our current roadmap (and that won't change for a while).
2. Is there any urgency regarding when we provide a response?

Hi @ifried, the direct stakeholders for this feature would be teams that have to create such pages for recurring but short campaigns. So far these would be the Marketing, Fundraising and Events teams given our past work with them.

On the question of urgency with regards to a response, you can give one in the next 3 - 4 weeks with an estimate(however ridiculous in the future it may be) regarding any intent to explore creating a feature. I do understand the bandwidth limitation your team is facing as well at the moment.

Thanks, @DMburugu! Is any specific work/bug fixes/feature development/new landing page development expected from the stakeholders? We don't have any capacity to take on extra work in our roadmap this fiscal year (and probably next fiscal year too), so we would need to know if any work on this feature is expected within this fiscal year (or, if not, when)?

Also, you mentioned creating a feature. Which feature would this be? This would be a project to generalize the landing page? If yes, we don't have any capacity to work on this anytime soon, unfortunately. But, once we know exactly what the stakeholders are expecting and when they expect it (if anything), we can discuss as a team. Thanks.

Thanks.

This is early on but the stakeholders would expect a CMS style or configurable landing page which can accommodate a couple of base templates to choose from given the work done in the past. This would allow them to generate their own landing page instead of having it hard coded every time there's an event. This idea would avoid bloating up the code base with a lot of temporary work and increase maintenance.

We don't expect this any time soon but we wanted to bring it up for exploration.

@ifried I hope that helps paint an initial picture.

I think this is easy enough that we should just do it:

• add a "landing page template" and "landing page template parameter map" field to the campaign configuration we already have
• instead of the current hacky partially-hardcoded logic for calling different landing page generation methods based on the campaign parameter, map landing page template names to these functions, pass the paramater maps to these functions, and parametrize image/video file names and text (or more precisely, message keys)
• everything we currently have fits into two templates: hero image + title + body + three "benefit" bullets (omitted in some campaigns), and the same with video instead of image (and slightly different HTML markup). The trickiest part is handling the bullet icons and their ResourceLoader dependencies, and that seems manageable as well.

As for the Campaigns team, thanks for providing the extra context, @DMburugu. Apologies for the slow response. I've been struggling with how to respond, since 1) I can definitely see how this is relevant to & useful to Campaigns work, and 2) We're a new team, with a first project being built by developers who only joined a few months ago, so we need to be very careful about scope creep & taking on extra work. We are planning that our first project (i.e., building a registration solution) will be our primary focus until the end of Q2 of 2022/2023 at this point. We haven't set firm plans in place for what work will come after that, though I can certainly see the possibility of us exploring this in the future, especially if we receive some technical support from Growth engineers. I just don't know when, and we cannot commit to a timeline at this point. I'm supposed to have a chat with Marshall about Growth & Campaigns soon, so we can maybe discuss this in the meeting.

In T304506#7846198, @Tgr wrote:

I think this is easy enough that we should just do it:

Filed T307521: Support templating for Growth campaign landing pages for that.