-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
BIM workbench is not fully documented #14084
Comments
It is new to me that we use GitHub to track the documentation effort. When was that decided?? |
Please stop creating related issues. |
I don't think it was, but why not? I don't see well where else it could be tracked efficiently, and it might be a good thing so we try to have the doc in shape for 1.0. The day the doc is in its own repo, of course, that will be better, that's where we'll track things... But this should be discussed somewhere |
@furgo16 could you please use this issue for tracking documentation? I've noticed you started creating issues for every command. |
I can think of several reasons. But we should not have that discussion here. |
Agreed. Let's bring the topic up during next M3 meeting maybe |
@furgo16 nice script BTW! Maybe something like that could also be used to regenerate the tools table at https://wiki.freecad.org/BIM_Workbench |
I filed this issue with the spirit of contributing. The intention was to serve as the central point to organize the effort (similar to a GitLab epic) , with an issue task list and issues for every command, to more easily track the status. But also importantly to encourage other contributors to pick a task and complete the BIM documentation collaboratively. Those separate issues could also be managed in projects, similarly to what was done with the TNP effort. Regardless of the platform, I personally can only see advantages in using the same tools to manage documentation as code, especially if there is eventually a migration to markdown files for docs. Yet others might see this differently, which is absolutely fine. Constructive debate is one of the great things about open source. I was not anticipating filing this issue could stir negative feelings. Apologies for that, as it was not my intention. Feel free to close it if not desired. No hard feelings, happy to keep contributing in another area of the project if that's useful. Thanks. |
Thanks, I had thought about that as well! I would have liked to add each command's icon to the table. In the end, I could not figure out a way to retrieve the icons (and to upload them without manual steps), so I kept it simple as it is. |
A few notes from a clueless BIM user
|
Documentation has a lot of those quirks 😅 Hopefully very soon we'll remove that "documentation is in process" note :) The welcome screen also needs a rework anyway. Regarding last year's GSoC project, it basically still lacks functionality and didn't reach yet all the goals we wanted, so it's kind of stalled currently, and we are still using the wiki for now. But indeed after the release we need to retake that effort |
Problem description
Now that the Arch workbench is becoming the BIM workbench, there are a number of additional commands in the later that need to be documented.
This issue collects an overview and a list of tasks to organize the documentation effort.
Documentation tasks
Overview: documentation status
Full version info
Subproject(s) affected?
Arch
Anything else?
The overview table can be regenerated running this code on the Python console, with the BIM workbench active. Improvements welcome:
The text was updated successfully, but these errors were encountered: