Conversation
- dark-brand.yml: declare a real dark palette (near-black background, off-white foreground, dark surface for 'light' role) instead of duplicating the light palette; move dark mono colors into brand - dark-theme.scss: drop SCSS defaults now owned by dark-brand.yml, fix malformed $light value, remove the body.quarto-light .alt-background copy-paste bug and dead commented button styles - light-theme.scss: remove $link-color override so the brand's dark-blue link color applies in light mode - styles.css: stop redeclaring brand fonts and pt-based heading sizes - index.css: remove conflicting/unused .nav-pills active rules - both themes: override litera's serif paragraph font with the brand base font (this is why styles.css previously forced Arimo on p) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ing pages - _quarto.yml: replace the single global sidebar (all ~150 pages on every page) with named per-section sidebars using Quarto hybrid navigation; raise collapse-level to 2 now that each sidebar covers one section - Add landing pages for sections that previously deep-linked into sub-content: MEL, Research Transparency, Fieldwork Management, Survey and Respondent Tracking, and Communicating and Using Data - Point navbar Topics entries for MEL and Research Transparency at the new landing pages instead of child pages Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Add categories metadata (tutorial / how-to / reference / explanation) to every content page, derived from existing keywords and filenames with manual classification where keywords were silent - New diataxis-badge Lua filter maps categories to a badge rendered by the title-block partial above each page title - Badge styling in styles.css with AA-contrast colors per type in both light and dark modes - New how-to-guides.qmd hub: filterable table listing of every page categorized how-to; navbar How-to Guides menu (which listed 5 of 30 guides) becomes a direct link to the hub - Give the two under-construction Stata pages minimal frontmatter so they carry titles and no longer warn during listing scans Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Feature cards: add the missing Data Security and Research Transparency sections (8 -> 10 cards) and order them to match the navbar and sidebar - Add a "New to the Hub?" strip with three entry points keyed to the research lifecycle (starting a project / collecting data / analyzing and sharing) - Hero: replace the arbitrary Get Started -> Research Design button with Browse How-to Guides; give dark mode its own deep-green gradient and darken the light gradient's bright end for 3:1 text contrast - Darken the primary action button so white label text passes AA - Remove dead hero-image/hero-animation and hello-quarto CSS (no markup references them anywhere) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…nventions - page-template.qmd: add the categories (Diataxis) field and the de-facto lead-summary and Key Takeaways patterns pages already use - CONTRIBUTING.qmd: fix the frontmatter example (description -> abstract, matching every real page), document the categories field, sidebar registration for new pages, and the shared section-landing style - styles.css: style .custom-summary-block, used on 20 pages but previously rendered as an unstyled div - _quarto.yml: unify the software taxonomy with software/index.qmd - Development Environments groups VS Code with Virtual Environments, and the navbar menu gains Software Overview and Virtual Environments - Refresh the stale freeze cache for software/python/index.qmd, clearing the long-standing unresolved-link warning for software/guides/venv.qmd Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Summary 🚀
What does this PR do? 📝
WORK IN PROGRESS - not yet ready for review
Reviewing the UX design of the website and addressing fixes
Why is this change needed? 🤔
How was this implemented? 🛠️
How to test or reproduce? 🧪
Screenshots (if applicable) 📷
Checklist ✅
Reviewer Emoji Legend
:code::smiley::+1::100:...and I want the author to know it! This is a way to highlight positive parts of a code review.
:star: :star: :star:And I am providing reasons why it needs to be addressed as well as suggested improvements.
:star: :star:And I am providing suggestions where it could be improved either in this PR or later.
:star:...and consider this a suggestion, not a requirement.
:question:This should be a fully formed question with sufficient information and context that requires a response.
:memo::pick:This does not require any changes and is often better left unsaid. This may include stylistic, formatting, or organization suggestions and should likely be prevented/enforced by linting if they really matter
:recycle:Should include enough context to be actionable and not be considered a nitpick.