ontoportal / documentation

Source code for OntoPortal user, admin and developer guides
https://ontoportal.github.io/documentation
BSD 2-Clause "Simplified" License
3 stars 9 forks source link

Feature: Migrate the docs to the just-the-docs template #4

Closed syphax-bouazzouni closed 1 year ago

syphax-bouazzouni commented 1 year ago

Context

From our discussions

I extracted this action item " being able to search in the doc ", but to do that I needed to use a template (theme) that implement it. I did choose https://just-the-docs.github.io/just-the-docs/

Preview

See https://ontoportal-lirmm.github.io/documentation/administration

I migrated all the existent content and kept the same configuration data (status, description, order,....)

What's new

jonquet commented 1 year ago

Looks good to me. Same docs that @graybeal did earlier but searchable and with a menu on the left. Awesome, exactly what was missing. It does not address everything in pur documentation story, but it consolidates the choice of the github.io approach. Ok to merge for me. Waiting for the others opinion.

jonquet commented 1 year ago

I recommend including a FAQ section for listing bug-fixing for commonly known issues for quick reference. e.g., the number of visits not being updated, the ontology page taking a long time to show the list of ontologies, the group cannot be updated for an ontology, etc. Over time, this FAQ section may become a troubleshooting guide and even a guided search may be built on top in the distant future.

@arsarkar OK. thanks for suggestion. Can you transform this into a feature request on the issues section.

arsarkar commented 1 year ago

I approve from my side!

xeniacs commented 1 year ago

It looks good Syphax! Will the section about documentation configuration be visible to all who visit the page? If so, do you think this might be confusing to them?

syphax-bouazzouni commented 1 year ago

It looks good Syphax! Will the section about documentation configuration be visible to all who visit the page? If so, do you think this might be confusing to them?

Hi @xeniacs, thanks for your feedback. Yeah it will be visible and certainly it is confusing for visitors. I will surely remove/hide it in the future, but for now this PR is just about the technology behind the scene.

After I will let you @xeniacs , @jonquet , @graybeal, ... take the responsibilities of the editorial part (see discussion https://github.com/ontoportal/ontoportal-project/discussions/1)

And also can you please "approve this PR" if you agree with the change.

graybeal commented 1 year ago

There is a troubleshooting page (or two) and that/they may be repurposed into what you suggest. I think organizing them thematically may help people zero in on what they need.

syphax-bouazzouni commented 1 year ago

Hi @graybeal , thanks for the approvement.

Caveats: I'm not capable of reviewing changes on 191 files, and I'm not technically proficient enough to understand what I'm looking at in this pull request. (Would be happy to have someone take the hour or three it would take to teach me....)

It's not really important to understand the technical behind, in this pull request you only need to check if it respond to our requirements for a centralized documentation for the alliance.

But yeah I have no problem "to take the hour or three hour" to explain it if needed,

Although what it is really important to document (in my opninoin) , is a "how to contribute to the documentation" page

It is not clear to me that when the pull request is approved, the existing location of the docs https://ontoportal.github.io/administration/ will be serving this new material. I assume it will, but I think this is necessary because everything points to that location.

In summary: "Yes"

In details:

Note: All the bellow sections discuss about the what's next and like it's not propose of this PR, I will transfer it after to our discussion about the doc and transform the actions to issues (if apporeved).

Yes, it will be the same, but we will have an editorial problem after.

That are:

In summary, the next actions after the merge (that I would propose) are:

graybeal commented 1 year ago

head to read this twice, but I think I got it with a few clarifications:

There is a page that describes in detail how to work with the documentation (I'm sure you are aware of that). But several caveats about that existing page:

Also, none of the 3 or so internal links that I've tested have worked. It may have to do with the way I used absolute or relative links, which IIRC were a little weird in the previous technology.

syphax-bouazzouni commented 1 year ago

create new documentation repo and host all sub-categories of documentation (like administration) within that

I think that there is no need to create a new repo, just changing the current one name would be enaugh

I updated the bultes đź‘Ť

There is a page that describes in detail how to work with the documentation

Yes, this one: https://github.com/ontoportal/administration/blob/master/docs/README.md, we just need to update it (some infos will be depreacted, e.g there is no need of collections configuration) .

I think also we need to make less a detailed configuration documentation and more a guided tutorial of how to add/edit a page on the documentation. (it's just a proposition, but yes it is the subject of another discussion)

Also, none of the 3 or so internal links that I've tested have worked.

Fixed https://github.com/ontoportal-lirmm/documentation/commit/7e204c17646b5bd85094d134eb0d5ba0f854e7b3