Skip to content

docs: redistribute faq content to relevant sections (fixes #39)#42

Closed
MChandrahas wants to merge 2 commits into
canonical:mainfrom
MChandrahas:fix/39-redistribute-faq
Closed

docs: redistribute faq content to relevant sections (fixes #39)#42
MChandrahas wants to merge 2 commits into
canonical:mainfrom
MChandrahas:fix/39-redistribute-faq

Conversation

@MChandrahas
Copy link
Copy Markdown

Description

This PR addresses issue #39 by redistributing the FAQ content into relevant documentation sections to improve context and discoverability.

Changes

  • Deleted docs/explanation/faq.md.
  • Moved relevant FAQ content to docs/explanation/mode-of-operation.md and docs/explanation/slices.md.
  • Updated docs/explanation/index.md to remove the reference to the FAQ page.

QA Steps

  1. Verify that docs/explanation/faq.md is deleted.
  2. Check docs/explanation/index.md to ensure the FAQ link is removed.
  3. Verify that the moved FAQ content appears correctly in docs/explanation/mode-of-operation.md and docs/explanation/slices.md.

@MChandrahas
Copy link
Copy Markdown
Author

Hi @asanvaq , I have made the necessary changes and made a commit. Please verify and let me know if any changes are needed. Thanks.

@asanvaq asanvaq self-requested a review December 12, 2025 07:41

### Package naming

Package names must be the same as the package names in the archive, so that
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.

This is redundant. It's basically saying: "the package names must be the same as the package names".

It might have made sense in the FAQ, but this page is about slices, and thus "naming convention" refers to the slices naming convention. There's no package naming, cause there are no packages in chisel, only references to the package a slice comes from

@cjdcordeiro
Copy link
Copy Markdown
Collaborator

PS this change also makes the "modes-of-operation" page look ugly due to varying lengths of text across steps

Comment on lines +32 to +34
definitions<slice_definitions_ref>` while validating the release and checking for
conflicting paths across packages. Slice definitions for each Ubuntu release are
located in the corresponding `ubuntu-XX.YY` branch of the {{chisel_releases_repo}}.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This information is already in docs/reference/chisel-releases/index.md, there is no need to repeat it here.

Comment on lines +60 to +62
The supported archives are described at
{ref}`chisel_yaml_format_spec_archives`; non-Ubuntu archives and PPAs are not
supported.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This information is already in docs/reference/chisel-releases/slice-definitions.md, so there is no need to repeat it.

@asanvaq
Copy link
Copy Markdown
Contributor

asanvaq commented Feb 16, 2026

Hi @MChandrahas! Are you still planning on continuing with this?

@barbaravalera
Copy link
Copy Markdown
Contributor

Hi @asanvaq, is this issue still open? I could work on it if it is.

@asanvaq
Copy link
Copy Markdown
Contributor

asanvaq commented May 15, 2026

Hi @barbaravalera! Thank you for your interest, the issue is still open. Could you please comment on #39 so I can assign it to you? Thanks!

@asanvaq
Copy link
Copy Markdown
Contributor

asanvaq commented May 25, 2026

Closing as merged in #64

@asanvaq asanvaq closed this May 25, 2026
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.

4 participants