Skip to content
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

Upgraded the documentation to use the latest docfx tool #1143

Merged
merged 8 commits into from
Apr 1, 2024
Merged

Upgraded the documentation to use the latest docfx tool #1143

merged 8 commits into from
Apr 1, 2024

Conversation

paulushub
Copy link
Contributor

@paulushub paulushub commented Feb 4, 2024

Note

For the documentation review, I have deployed the output to GitHub-Pages on my fork.
URL: https://paulushub.github.io/SVG/

Nerdbank.GitVersioning is currently generating error in docs build, probably because it is building on my fork!

Description

  • Updated the builddocs.yml to the new docfx workflow format.
  • Renamed the doc to Docs
  • Moved the doc/*.md files to Docs/articles/*.md
  • Moved the docfx.json to Docs/docfx.json (updated to support latest docfx version)
  • Moved the index.md to Docs/index.md

Type of change

  • Documentation changes, no change in main source codes (non-breaking change which fixes an issue)
  • This change does not require a documentation update
  • A Docs/Readme.md file, to be included as Readme file in NuGet Package.
  • Update revision notes
  • Resolved review issues.

How Has This Been Tested?

  • Docfx builds locally with a warning (can be ignored), due to the generator.

@paulushub paulushub self-assigned this Feb 4, 2024
Docs/articles/ReleaseNotes.md Outdated Show resolved Hide resolved
Docs/articles/ReleaseNotes.md Outdated Show resolved Hide resolved
.github/workflows/builddocs.yml Show resolved Hide resolved
Docs/articles/Introduction.md Outdated Show resolved Hide resolved
Docs/articles/Introduction.md Outdated Show resolved Hide resolved
Docs/Readme.md Show resolved Hide resolved
Docs/docfx.json Outdated
"_enableSearch": true,
"pdf": false,
"pdfTocPage": false,
"_appFooter": "<div class=\"d-flex flex-column flex-sm-row justify-content-between pt-1\"><p> &copy; 2013 - 2024 SVG-NET</p><p>Made with <a href=\"https://dotnet.github.io/docfx\">DocFX</a></p></div>",
Copy link
Member

Choose a reason for hiding this comment

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

Not sure about that copyright. It has been Microsoft, then vvvv, then svg-net - maybe these should be noted separately for the respective years.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not really sure it was a Microsoft software as those days a project created by Visual Studio included Properties/AssemblyInfo.cs with the copyright portion marked as (c) Microsoft.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, and that AssemblyInfo.cs is still there, which has AssemblyCopyright("Copyright © Microsoft 2006").

Copy link
Member

Choose a reason for hiding this comment

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

So, if we want to have a copyright here, it should be (c) 2006 Microsoft, and maybe also 2011 vvvv group, though I would ask @tebjan about this one.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See the Nuget Package: Copyright © vvvv.org. I thought you said it was transferred to SVG-NET.

Copy link
Member

Choose a reason for hiding this comment

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

The repository was transferred, but that does not mean that the copyright will disppear, as far as I understand (mind you, I'm not a lawyer, and I understand very little about this stuff).
What I have seen in similar situations is something like this:
© Copyright 2009 Microsoft. All Rights Reserved. © Copyright 2011 vvvv Group. All Rights Reserved. © Copyright 2021 SVG.NET Contributors
This is admittedly a mouthful, not sure if we really need this. Still would like @tebjan to comment on this.

Copy link
Contributor

@tebjan tebjan Mar 25, 2024

Choose a reason for hiding this comment

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

© Copyright 2009 Microsoft. All Rights Reserved. © Copyright 2011 vvvv Group. All Rights Reserved. © Copyright 2021 SVG.NET Contributors

This looks good! I would go with that. Thanks for considering.

Docs/index.md Show resolved Hide resolved
Docs/namespaces/Svg.ExtensionMethods.md Outdated Show resolved Hide resolved
Docs/api/index.md Show resolved Hide resolved
Docs/articles/GettingStarted.md Outdated Show resolved Hide resolved

## Downloads
The SVG-NET is available as [NuGet Package](https://www.nuget.org/packages/svg).
The respository includes
Copy link
Contributor

Choose a reason for hiding this comment

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

respository -> repository ??

* Added: Support for .NET 4.7.2, .NET 4.8.1 and .NET 8.0.
* Added: A new project, `Tests/Svg.Tests.Common` for sharing codes between test applications.
* [Breaking change] The support for .NET 8 resulted in a breaking change to the signature of methods in `CoordinateParser`.
* [Breaking Change] The support for .NET 8 resulted in a breaking change to the signature of methods in `CoordinateParser`.
* The changes are needed to fix a compiler error `CS8352`.
* The use of read-only arguments as referenced variable is not necessary.
* The use of `ref` in the function arguements resulting in `CS8352` error are all removed.
Copy link
Contributor

Choose a reason for hiding this comment

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

arguements -> arguments

Docs/articles/ReleaseNotes.md Show resolved Hide resolved
@mrbean-bremen
Copy link
Member

Off-topic: this PR is actually not relevant for a patch release, and may still take a while to get finally consolidated. Would it be ok if I made a patch release without it (see #1147)?

@paulushub paulushub removed their assignment Feb 22, 2024
@mrbean-bremen
Copy link
Member

Re: typos - we probably need a type checker hook to make this easier - I use this in my Python repos... It is easy to overlook typos.

As for the patch release - I'll probably just do it - releases are cheap!

paulushub and others added 7 commits February 22, 2024 20:46
- Updated the builddocs.yml
- Renamed the doc to Docs
- Moved the doc/*.md files to Doc/articles/*.md
- Moved the docfx.json to Doc/docfx.json
- Moved the index.md to Doc/index.md
- Updated actions versions
- clarified the organization transfer
- removed using company except in the global README
- Added Infrastructure section
- Updated namespace descriptions
Copy link
Contributor

@tebjan tebjan left a comment

Choose a reason for hiding this comment

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

As mrbean proposed.

Docs/docfx.json Outdated
"_enableSearch": true,
"pdf": false,
"pdfTocPage": false,
"_appFooter": "<div class=\"d-flex flex-column flex-sm-row justify-content-between pt-1\"><p> &copy; 2013 - 2024 SVG-NET</p><p>Made with <a href=\"https://dotnet.github.io/docfx\">DocFX</a></p></div>",
Copy link
Contributor

@tebjan tebjan Mar 25, 2024

Choose a reason for hiding this comment

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

© Copyright 2009 Microsoft. All Rights Reserved. © Copyright 2011 vvvv Group. All Rights Reserved. © Copyright 2021 SVG.NET Contributors

This looks good! I would go with that. Thanks for considering.

@mrbean-bremen
Copy link
Member

I'm going to merge this now, as all problems seem to be resolved (I updated the copyright in the last commit).
If more changes are needed, we can make new PRs.

@mrbean-bremen mrbean-bremen merged commit 398411e into svg-net:master Apr 1, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants