Skip to content

many fixes to pages#150

Merged
BBeltz1 merged 19 commits into
masterfrom
dev
Nov 10, 2025
Merged

many fixes to pages#150
BBeltz1 merged 19 commits into
masterfrom
dev

Conversation

@andybeet

@andybeet andybeet commented Nov 10, 2025

Copy link
Copy Markdown
Member

See fixes in PR #149

BBeltz1 and others added 16 commits October 16, 2025 16:54
@BBeltz1
update(harborporpoise): add information from most recent SOE submissi…
321ef25 
…on from contributor
@BBeltz1
update(grayseal): add information from most recent SOE submission fro…
56392d1 
…m contributor
@BBeltz1
update(productivity_anomaly): correct broken repository links to refl…
ff7f474 
…ect new repository ownership
@andybeet
Doc: fix header values to conform
d7fac87
@andybeet
Doc: fix missing reference to FMP field
3af7f98
@andybeet
Doc: edit text as per kristin.precoda
c5b75a4
@andybeet
Doc: reorg needed and missing content added
542f74c
@andybeet
Doc: fix missing data place holder
b445eaa
@andybeet
Doc: created missing aggregate_biomass page and reworked general surv…
f8e3e8a 
…ey data page
@andybeet
Code: add agregate_biomass to book
b048ea5
@andybeet
Doc: add missing survey_shanon page
66f0135
@andybeet
Doc: fixed new link for productivity anomaly
86242c5
@andybeet
fix case change
d76ba84
@andybeet
Doc: content change
78ccf77
@BBeltz1
fix(hudson_river_flow): correct syntax mistake in hudson river flow page
512cccb
@BBeltz1
Merge pull request #149 from NOAA-EDAB/doc_format_changes
98c5abf 
Formatting/content fixes
@andybeet andybeet requested a review from BBeltz1 November 10, 2025 18:29
@andybeet

andybeet commented Nov 10, 2025

Copy link
Copy Markdown
Member Author

@BBeltz1 We'll need to version tech-doc after this merge. v6.0.1

@BBeltz1

BBeltz1 commented Nov 10, 2025

Copy link
Copy Markdown
Collaborator

@andybeet this should be the first entry into v7. Version 6 ended with the publication of SOE 2025. We should discuss this though, because I think it's a bit confusing across our products. I think changing to a versioning system which references the report year might work better. E.g. Tech Doc v2026, Catalog v2026 and Ecodata v2026 would be the next versions to make clear that those images of the repos correspond to SOE 2026. Thoughts?

@andybeet

andybeet commented Nov 10, 2025 •
edited
Loading

Copy link
Copy Markdown
Member Author

I think you are right, mostly because some of these changes are for the next cycle (2026) and it doesnt make sense to version as part of 2025. If these were just mistakes we were fixing then i'd say it would be a new 2025 fix (v6)

@BBeltz1

BBeltz1 commented Nov 10, 2025

Copy link
Copy Markdown
Collaborator

What do you think about changing to vYEAR going forward.. such that all products starting this new SOE cycle will be v2026?

@andybeet

andybeet commented Nov 10, 2025

Copy link
Copy Markdown
Member Author

i think it makes a lot of sense. i support that decision

@BBeltz1

BBeltz1 commented Nov 10, 2025

Copy link
Copy Markdown
Collaborator

Sounds good. I actually have changes to pull into dev before merging this, so let me create that PR quickly.

BBeltz1
BBeltz1 approved these changes Nov 10, 2025
View reviewed changes

@BBeltz1 BBeltz1 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@BBeltz1 BBeltz1 merged commit 5800b29 into master Nov 10, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@BBeltz1 BBeltz1 BBeltz1 approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@andybeet @BBeltz1