Skip to content

docs: restructure docs#38

Merged
MarkoSagadin merged 1 commit intomainfrom
feature/restructure_docs
Mar 7, 2025
Merged

docs: restructure docs#38
MarkoSagadin merged 1 commit intomainfrom
feature/restructure_docs

Conversation

@MarkoSagadin
Copy link
Collaborator

Description

As we will soon transition from east to twister for the purposes of
release artefacts generations it is expected that some documentation
will have to be written for that.

As the current state of the template repo doesn't really have a nice
place to plug-in that documentation somewhere and since some time passed
since we were last updating the READMEs here, this commit does some
restructuring of the existing docs.

The general idea:

  • Add doc/ folder. It should be used to contain all project specific
    documentation.
  • Add doc/development folder. It should contain all documents that are
    somehow connected with the development aspect of the project.

Areas of interest for the reviewer

Does the restucturing make sense? Are the new READMEs in the right place?

Checklist

  • My code follows the style guidelines as defined by IRNAS.
  • I have performed a self-review of my code.
  • My changes generate no new warnings.
  • I added/updated source code documentation for all newly added or changed functions.
  • I updated all customer-facing technical documentation.

After-review steps

  • I will merge PR by myself.

@github-actions github-actions bot added the pull request Pull request, added automatically by CI. label Feb 28, 2025
Copy link
Collaborator Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@MarkoSagadin MarkoSagadin mentioned this pull request Feb 28, 2025
5 tasks
Copy link
Contributor

@TjazVracko TjazVracko left a comment

Choose a reason for hiding this comment

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

Good stuff. I will comment on twister.yml in the next PR.

I added some comments about things you could still improve in the template and fixed some grammar mistakes.

@MarkoSagadin MarkoSagadin force-pushed the feature/restructure_docs branch from 26935b4 to 4d3c98a Compare March 3, 2025 13:42
As we will soon transition from east to twister for the purposes of
release artefacts generations it is expected that some documentation
will have to be written for that.

As the current state of the template repo doesn't really have a nice
place to plug-in that documentation somewhere and since some time passed
since we were last updating the READMEs here, this commit does some
restructuring of the existing docs.

The general idea:
- Add doc/ folder. It should be used to contain all project specific
  documentation.
- Add doc/development folder. It should contain all documents that are
  somehow connected with the development aspect of the project.
@MarkoSagadin MarkoSagadin force-pushed the feature/restructure_docs branch from 4d3c98a to b5bf535 Compare March 3, 2025 14:15
@MarkoSagadin MarkoSagadin requested a review from TjazVracko March 3, 2025 14:15
@MarkoSagadin MarkoSagadin merged commit c3d2cfb into main Mar 7, 2025
1 check passed
@MarkoSagadin MarkoSagadin deleted the feature/restructure_docs branch March 7, 2025 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pull request Pull request, added automatically by CI.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants