-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tbcct 260 fe implement methodology section #254
base: dev
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
e0ac989
to
170b29d
Compare
170b29d
to
bc0f808
Compare
const navItems = useMemo(() => { | ||
return METHODOLOGY_SECTIONS.map(({ id, title, href }) => ({ | ||
id, | ||
label: title, | ||
href, | ||
})); | ||
}, []); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't METHODOLOGY_SECTIONS
static content? I would move this parse out of the Methodology function as there is nothing the parse depends on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Will do that
Scrolling down, the sidebar jumps from "Project costs – assumptions and methodology" to "Qualitative scorecard details and sources" without passing through "Model assumptions". |
Added Methodology Page and Components
Changes
Jira