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

Add more categories #25

Open
ChristianGreiner opened this issue May 24, 2018 · 2 comments
Open

Add more categories #25

ChristianGreiner opened this issue May 24, 2018 · 2 comments
Labels
Discussion Nothing to be done until decided otherwise Improvement Extended or improved info on topic Infrastructure Area: Project infrastructure, meta-issues, refactoring and bigger high level changes

Comments

@ChristianGreiner
Copy link

At the moment we have following "categories":

  • Introduction
  • Tutorials
  • Basic Topics
  • Advanced Topics
  • Contributing

I think it would be more helpful if we change or add some more categories like:

  • Duality Editor (all editor features, extending the editor)
  • Graphics (e.g. Shaders, Animations)
  • Physics (Rigid Bodies, Forces)
  • Coding (Components, plugins)
  • Audio (3D Sound, Music, Sound Effects)
  • Platform (Deployment on Windows (and Linux / Mac)

What do you think?

@ChristianGreiner ChristianGreiner changed the title Categorize some topics Add more categories May 24, 2018
@ilexp ilexp added Improvement Extended or improved info on topic Discussion Nothing to be done until decided otherwise Infrastructure Area: Project infrastructure, meta-issues, refactoring and bigger high level changes labels May 26, 2018
@ilexp
Copy link
Member

ilexp commented May 26, 2018

I think having better categories is a great idea, but we should also utilize nested pages as well to keep the number of top-level pages down, see this comment.

I think it would be more helpful if we change or add some more categories like:

Duality Editor (all editor features, extending the editor)
Graphics (e.g. Shaders, Animations)
Physics (Rigid Bodies, Forces)
Coding (Components, plugins)
Audio (3D Sound, Music, Sound Effects)
Platform (Deployment on Windows (and Linux / Mac)

Looks reasonable to me, would maybe adjust one or to items slightly. Maybe it would make sense to pull apart "Basic Topics" and "Advances Topics" and re-sort their items into the new categories. How about something like:

  • Introduction: Home, Should You Use, Community, Meta
  • Tutorials: Getting Started and other step-by-step tutorials
  • Basics: GameObjects, Components, etc.
  • Graphics: Shaders, Animations
  • Audio : 3D Sound, Music, Sound Effects
  • Physics: RigidBodies, shapes, forces, etc.
  • Editor: Editor features, extending the editor
  • Platform: Deployment on various platforms, lowlevel platform interfaces, backend dev and info
  • Contributing: How to contribute, Duality dev, maintenance topics

@ilexp
Copy link
Member

ilexp commented Feb 10, 2019

Added some features to our Jekyll setup to make it easier to do bigger category changes across docs versions.

Progress

  • Introduced a versioned "Home" page to allow access to top-level pages that no longer exist in the latest version and ease navigation within old docs.
  • Top-level pages to be displayed in Home sidebar are now determined automatically based on their parent and category variables.
  • Replaced top-level category definition with a generic array of category descriptions that does not imply their display in the sidebar. Only categories that are used in the current versions docs will be displayed. Different docs versions can use different categories.
  • Child / sibling page display in the sidebar is now sorted by displayOrder.
  • Pages can now specify formerPaths in order to allow access to all versions of a page even when the page was renamed or moved to a different folder / URL.
  • Added explicit defaults for all used / custom Jekyll Front Matter variables in _config.yml, also serving as a small documentation on how to use each of them.

ToDo

  • Define new top-level categories and page hierarchy.
  • Apply the new structure, but only to the v3 version of the docs. Keep the old docs as they are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Nothing to be done until decided otherwise Improvement Extended or improved info on topic Infrastructure Area: Project infrastructure, meta-issues, refactoring and bigger high level changes
Development

No branches or pull requests

2 participants