-
Notifications
You must be signed in to change notification settings - Fork 48
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
Update user documentation structure #414
Conversation
Revised content on existing pages to have an unifirm style across the user documentation
i see one problem now...the links to the doc we have added to the D2.5 deliverables will be incorrect ..so we should revise them ASAP when we approve this PR |
great work! let's make the linter happy and then we can have a preview and review the changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Added a few comments, mainly letting other service owners review the content for their services.
Once it lints well we can enable the preview.
EGI-ACE D2.5 updated |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
Looks good! |
I agree. That will get improved when the Getting Started part gets revised next. A lot of stuff about how to request access, the architecture, and more from D2.3 and D2.5 need to be added. But it is not what this PR should fix.
The CLI page starts with this text, that I think is enough to not leave the impression that this is the CLI that can handle anything: "The various public EGI services can be managed and used/accessed with a wide variety of command-line interface (CLI) tools. The documentation of each service contains a summary of the CLIs that can be used with that service, together with recommendations on which one to use in what context." FedCloud CLI is more or less "the CLI" for EGI, a lot of docs pages refer to it (there were many places that were introducing fedcloudcli, now all those refer to |
@andrea-manzi I did a lot of changes in the top pages for the data services. uniformized titles and subtitles (e.g. no links or acronyms in titles), added a What is it? paragraph to each. please review them, let me know if it's good (or you can improve it further in future PRs). Data TODOs:
|
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
we should remove draft: true from the openRDM page |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
CHanged linktitles for data management services
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
As the servive is to be renamed too
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
1 similar comment
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
Should we just remove the taskforce page in this PR? It's not bringing any value right now and I fear we will be postponing moving it forever. It simply does not belong to the docs.egi.eu but it's more a TCB-like activity and should be documented as such in confluence |
Added draft flag, removed links to it. |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, let's go for it
Documentation preview deployed!Available at https://docs.egi.eu/documentation/414 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @thebe14
Summary
The documentation needs some changes to the structure, in order to accommodate new services and to make it easier to navigate. A lot of (most) content from the EGI-ACE D2.3 and D2.5 should end up in our user documentation.
Related issue : Implements #411