Skip to content

Add user manual content with structured sections and table of contents #8

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

Merged
merged 15 commits into from
Apr 15, 2025

Conversation

Sam-Max
Copy link
Contributor

@Sam-Max Sam-Max commented Apr 13, 2025

  • Updated the site navigation to include a link to the new user manual under the Resources menu.

@CLAassistant
Copy link

CLAassistant commented Apr 13, 2025

CLA assistant check
All committers have signed the CLA.

@sanity
Copy link
Contributor

sanity commented Apr 13, 2025

the manual/ directory inside content/ should be moved inside the content/resources/ directory so that it coresponds to putting it under the Resources menu item.

@@ -8,7 +8,7 @@ links:
text: "Video Talks"
icon: "fas fa-video"
color: "is-medium-blue"
- url: "https://docs.freenet.org/"
- url: "/manual/"
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be /resources/manual

@@ -0,0 +1,64 @@
**NOTE:** This document is a work in progress. You can [submit an issue](https://github.com/freenet/freenet-core/issues/new?labels=A-documentation) if you find a problem or have a suggestion. The source for this documentation is in our repository at [freenet-core/docs/src](https://github.com/freenet/freenet-core/tree/main/docs/src). We welcome pull requests.
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we need to copy this README.md file over.

@@ -73,6 +73,12 @@ theme = "freenet"
name = "Contribute"
weight = 10

[[menu.main]]
Copy link
Contributor

@sanity sanity Apr 13, 2025

Choose a reason for hiding this comment

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

I think you will also need to add menu entries for each of the pages in the manual, nested under the Manual section

- Updated the site navigation to include a link to the new user manual under the Resources menu.
@@ -79,6 +79,12 @@ theme = "freenet"
weight = 14
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't this be "/resources/manual/" to correspond to the directory structure under content/?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is fixed in the commit 2ec81f9, the last one, here I was playing with Aider, and it made that commit.


Freenet contracts must implement the [`ContractInterface`](https://docs.rs/freenet-stdlib/latest/freenet_stdlib/prelude/trait.ContractInterface.html) trait:

```rust
Copy link
Contributor

Choose a reason for hiding this comment

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

While this should change infrequently it would still be nice to pull it directly from the repo.


Software that uses Freenet as a back-end. This includes native software
distributed independenly of Freenet but which uses Freenet as a back-end
(perhaps bundling Freenet), and [web applications](/manual/glossary#web-application)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be /resources/manual/...?

@Sam-Max Sam-Max changed the title WIP: Add user manual content and update site navigation Add user manual content with structured sections and table of contents Apr 15, 2025
@sanity sanity marked this pull request as ready for review April 15, 2025 16:01
@sanity sanity merged commit af875d8 into freenet:main Apr 15, 2025
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants