redesign: prepare landing page for new design

[preschian]

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.

PR type

• Bugfix
• Feature
• Refactoring

What's new?

• prepare landing page for new design Redesign Landing page #3844 (comment)
• access new design with ?redesign=true
• existing design should be still ok
• Refactoring components and redesign #3710 (comment)

Before submitting Pull Request, please make sure:

• My contribution builds clean without any errors or warnings
• I've merged recent default branch -- main and I've no conflicts
• I've tried to respect high code quality standards
• I've didn't break any original functionality
• I've posted a screenshot of demonstrated change in this PR

Optional

• I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
• I've tested PR on mobile and everything seems works
• I found edge cases
• I've written some unit tests 🧪

Had issue bounty label?

• Fill up your KSM address: Payout

Community participation

• Are you at KodaDot Discord?

Screenshot

• My fix has changed something on UI; a screenshot is best to understand changes for others.

[netlify]

✅ Deploy Preview for koda-nuxt ready!

Name	Link
🔨 Latest commit	31f693d
🔍 Latest deploy log	https://app.netlify.com/sites/koda-nuxt/deploys/63197a4932797b00083c2293
😎 Deploy Preview	https://deploy-preview-3895--koda-nuxt.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[preschian]

hi, I need your feedback, should we go with this approach or not? the goal is, we can start redesigning components without blocking deployment to production. because the new design only can be accessed with query parameters

#3710 (comment)

alternative from query parameters:

• custom cookie
• custom http-header
• env variable

[roiLeo]

wait what? why this way?
My suggestion would be to manage a new branch and cherry-pick new version of landing

[preschian]

wait what? why this way?

I thought this way was easier. but if we already have another simpler solution I will follow it 👍

[preschian]

My suggestion would be to manage a new branch and cherry-pick new version of landing

for this, does it means we have another big branch for a redesign? for example main-redesign

[roiLeo]

for this, does it means we have another big branch for a redesign? for example main-redesign

yes! maybe with another branch name, since we're migrating app to use vue3 composition api

[preschian]

yes! maybe with another branch name, since we're migrating app to use vue3 composition api

I thought that with another big branch would be difficult once ready to merge into the main branch, because of some file conflicts

but, no issue for me if everyone prefers that way 👍

[roiLeo]

but, no issue for me if everyone prefers that way 👍

Let's wait for another developer's point of view

[yangwao]

uno momento 🤌
ill drop wisdom to discussion thread 🧵

[roiLeo]

Since we're going to use new typo, different font-size & update components (inputs, select, dropdown) design. I would be in favor to make these developments on a new branch so as not to disrupt the existing one.
I find that it might be difficult to maintain 2 different design system on the same project/branch.

[preschian]

Since we're going to use new typo, different font-size & update components (inputs, select, dropdown) design. I would be in favor to make these developments on a new branch so as not to disrupt the existing one. I find that it might be difficult to maintain 2 different design system on the same project/branch.

maybe describe and define the branch name in here #3710. so on every redesign PR can follow the guideline to that link

[yangwao]

I've dropped some wisdom #3710

define the branch name

canary

Since we're going to use new typo, different font-size & update components (inputs, select, dropdown) design. I would be in favor to make these developments on a new branch so as not to disrupt the existing one.

just for the landing page, I promise 🤞🥹

[preschian]

ready for review 🙏🏻

it's decided that we use query parameters for the landing page only #3710 (reply in thread). the goal is still the same, hopefully not break/block the existing design while creating a new redesign component

[codeclimate]

Code Climate has analyzed commit 31f693d and detected 0 issues on this pull request.

View more on Code Climate.

[yangwao]

yas, let's kick this off! :)

works old version and the new one seems div containers ready to be there.

pay 100

[yangwao]

😍 Perfect, I’ve sent the payout
💵 $100 @ 51.94 USD/KSM ~ 1.925 $KSM
🧗 DY4SQF2iD456tH89aQtz5wv1EV3BbSW8wKKuMcwbmXaj1pM
🔗 0x926dced7f7648ebc43def691b88111f371532bafea39338a1ee731110078a9a4

🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues