Design Engineer 001 Submission — Abang Tah

[abangtah]

Figma:
https://www.figma.com/design/h2lGs98T4DiSqr0ggVMrfR/Untitled?node-id=0-1&p=f&t=alTdKB12BL4nYo8p-0

Summary:
This submission refines the AI-generated wireframe into a conversion-focused landing page aligned with Signalflow’s brand system. All changes were made with a focus on real enterprise conversion behavior, not just aesthetics.

Key improvements:

• Introduced product UI in the hero section to immediately establish credibility
• Strengthened visual hierarchy, highlighting key stats and proof
• Reworked layout flow to guide decision-making (Hero → Proof → Features → CTA)
• Applied consistent spacing, typography, and component structure according to the brand guide
• Structured sections to support future experimentation and optimization (conversion-driven thinking)

Files are contained within:
challenges/design-engineer-001/submissions/abang-tah/

[sandiegodj]

@123abang Strong conversion thinking. Before we move forward, can you do a quick
pass to bring the implementation tighter to the brand guide?

[abangtah]

Hello Sandie, Quick clarification — when you say tighten to the brand guide, do you mean a strict pass on colors, spacing, typography, and components, or also adjusting layout where needed?

…

On Wed, Mar 18, 2026 at 04:32 David Janczyn ***@***.***> wrote: *sandiegodj* left a comment (FunnelEnvy/outperform#2) <#2 (comment)> @123abang <https://github.com/123abang> Strong conversion thinking. Before we move forward, can you do a quick pass to bring the implementation tighter to the brand guide? — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5IBCYJVXXSFXQKYZBAYNOL4RIKGVAVCNFSM6AAAAACWUJJX3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANZZGM4DIOBYGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sandiegodj]

@123abang Strict pass on tokens, (colors, typography, spacing etc.) layout is your call.

[abangtah]

Okay I’ll do that now . And update it when I do I will let you know . Have a great day

…

On Wed, Mar 18, 2026 at 15:10 David Janczyn ***@***.***> wrote: *sandiegodj* left a comment (FunnelEnvy/outperform#2) <#2 (comment)> @123abang <https://github.com/123abang> Strict pass on tokens, (colors, typography, spacing etc.) layout is your call. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5IBCYINH4HV4EBYUDTW6SD4RKU3TAVCNFSM6AAAAACWUJJX3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBSHA3DGMBSGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[abangtah]

Done — I’ve tightened the implementation to strictly follow the Signalflow brand tokens (colors, typography, spacing, and component specs). Also cleaned up minor inconsistencies for better alignment. Would appreciate a quick pass to confirm this is now aligned with what you had in mind.

…

On Wed, Mar 18, 2026 at 3:12 PM Abang Tah ***@***.***> wrote: Okay I’ll do that now . And update it when I do I will let you know . Have a great day On Wed, Mar 18, 2026 at 15:10 David Janczyn ***@***.***> wrote: > *sandiegodj* left a comment (FunnelEnvy/outperform#2) > <#2 (comment)> > > @123abang <https://github.com/123abang> Strict pass on tokens, (colors, > typography, spacing etc.) layout is your call. > > — > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A5IBCYINH4HV4EBYUDTW6SD4RKU3TAVCNFSM6AAAAACWUJJX3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBSHA3DGMBSGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[sandiegodj]

Hey @123abang - looks like your force-push may have reverted your changes. The branch is back on the original commit (bb3eb85) and the code still shows Tailwind CDN with no custom properties. You probably had the updated version on c4eeec7. Can you check and re-push?

[abangtah]

Just pushed the updated version and opened the PR: #9 Aligned the implementation strictly with the brand tokens as discussed. Would appreciate a quick pass when you get a moment.

…

On Thu, Mar 19, 2026 at 3:09 PM David Janczyn ***@***.***> wrote: *sandiegodj* left a comment (FunnelEnvy/outperform#2) <#2 (comment)> Hey @123abang <https://github.com/123abang> - looks like your force-push may have reverted your changes. The branch is back on the original commit ( bb3eb85 <bb3eb85>) and the code still shows Tailwind CDN with no custom properties. You probably had the updated version on c4eeec7 <c4eeec7>. Can you check and re-push? — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5IBCYOVQE3OXXDAMUIBPNL4RP5QBAVCNFSM6AAAAACWUJJX3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOJQGQYDSMZQG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[abangtah]

Hello David just wanted to follow up on my submission here: #9 Would love your feedback whenever you get a moment.

…

On Thu, Mar 19, 2026 at 20:30 Abang Tah ***@***.***> wrote: Just pushed the updated version and opened the PR: #9 Aligned the implementation strictly with the brand tokens as discussed. Would appreciate a quick pass when you get a moment. On Thu, Mar 19, 2026 at 3:09 PM David Janczyn ***@***.***> wrote: > *sandiegodj* left a comment (FunnelEnvy/outperform#2) > <#2 (comment)> > > Hey @123abang <https://github.com/123abang> - looks like your force-push > may have reverted your changes. The branch is back on the original commit ( > bb3eb85 > <bb3eb85>) > and the code still shows Tailwind CDN with no custom properties. You > probably had the updated version on c4eeec7 > <c4eeec7>. > Can you check and re-push? > > — > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A5IBCYOVQE3OXXDAMUIBPNL4RP5QBAVCNFSM6AAAAACWUJJX3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOJQGQYDSMZQG4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >