Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E escet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
    • Locked Files
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Eclipse ESCET (Supervisory Control Engineering Toolkit)
  • escet
  • Issues
  • #73
Closed
Open
Issue created May 03, 2021 by Dennis Hendriks@ddennisMaintainer

Rethink documentation sets structure

We currently have the following documentation sets/structure:

  • Eclipse ESCET documentation
    • Chi documentation
    • CIF documentation
    • SeText documentation
    • ToolDef documentation

The Eclipse ESCET documentation includes the project documentation, developer documentation and documentation about the common parts/folder.

We may want to restructure it. Let's discuss here how to improve it, and what we want.

Note that this issue is about the documentation sets that are distinguishable by end users. It is not about where the sources of the documentation sets are put in the Git repository, and whether these should be all together or spread out, as that is part of #102 (closed).

Edited Oct 06, 2021 by Dennis Hendriks
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent