SSWConsulting / SSWConsulting/SSW.Website
✨ Accessing "Old" Consulting Pages
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
cc's: @Calinator444 @adamcogan @wicksipedia
Is your feature request related to a problem? Please describe.
We're redesigning the consulting pages (see #3306), but editors or stakeholders might want to see the previous page for comparison.
Describe the solution you'd like
Current behaviour... going to a consulting route page with both a new and old entry in Tina will prioritise showing users the new page.
Proposed solution... Accessing a consulting page with the url query ?old=true guarantees providing the "old" consulting page for that specific route.
Describe alternatives you've considered
An extra path segment ex. consulting/old/{{name}} to guarantee showing the old pages.
Additional context
From the sprint review on 5/12/24.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the consulting route pages and how Tina entries are selected, using issue #3306 for the redesign context. Add support for the ?old=true query on a consulting route so it selects the old page, while the normal route continues to show the new page; verify both URL behaviours.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100