Skip to content

Improve structure of webpage#412

Merged
kara-mela merged 1 commit into
pan-ontologies:masterfrom
kara-mela:ISS363-improve-webpage-structure
Jun 5, 2026
Merged

Improve structure of webpage#412
kara-mela merged 1 commit into
pan-ontologies:masterfrom
kara-mela:ISS363-improve-webpage-structure

Conversation

@kara-mela
Copy link
Copy Markdown
Collaborator

Motivation

The current structure of the homepage feels crowded and arbitrary. I suggest to update it and group the topics.

Modification

We now have three top level topics: Home, Browse, and Documentation. Home includes the 'Scope of PaNET' and 'Applications'. Browse forwards to the 'Ontology Specification' page (widoco). Documentation includes 'Standard Operation Procedure', 'Git Workflow', 'Build the Robot Environment', and 'Make a Release'.

Additionally, the navigation layout has been improved and is now dynamic (based on the _data/navigation.yml).

Result

The structure of the webpage is clearer and more intuitive.

Related Issues

Closes #363

Copy link
Copy Markdown
Collaborator

@eilmiv eilmiv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. I like the new structure. I reviewed it as "Request changes" because of the broken purple highlight of the nav item on the index.html. Otherwise, there are just some small comments.

Comment thread docs/_data/navigation.yml Outdated
Comment on lines +3 to +7
link: "/index.html"
description: General information on PaNET
subnav:
- name: Scope of PaNET
link: "/index.html"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
link: "/index.html"
description: General information on PaNET
subnav:
- name: Scope of PaNET
link: "/index.html"
link: "/"
description: General information on PaNET
subnav:
- name: Scope of PaNET
link: "/"

The panet-purple highlight is missing when visiting the main page. This could be solved, if "/" instead of "/index.html" is used here.

Comment thread docs/_includes/navigation.html Outdated
Comment on lines +4 to +27
{% if item.subnav %}
<li class="nav-1st">
<a href="{{ item.link | relative_url }}" {% if page.url == item.link %} class="focus" {% endif %} class="nav-link">
{{ item.name }}
</a>
<div class="nav-2nd">
<ul>
{% for subitem in item.subnav %}
<li>
<a href="{{ subitem.link | relative_url }}" {% if page.url == subitem.link %} class="focus" {% endif %} class="nav-link">
{{ subitem.name }}
</a>
</li>
{% endfor %}
</ul>
</div>
</li>
{% else %}
<li>
<a href="{{ item.link | relative_url }}" {% if page.url == item.link %} class="focus" {% endif %} class="nav-link">
{{ item.name }}
</a>
</li>
{% endif %}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{% if item.subnav %}
<li class="nav-1st">
<a href="{{ item.link | relative_url }}" {% if page.url == item.link %} class="focus" {% endif %} class="nav-link">
{{ item.name }}
</a>
<div class="nav-2nd">
<ul>
{% for subitem in item.subnav %}
<li>
<a href="{{ subitem.link | relative_url }}" {% if page.url == subitem.link %} class="focus" {% endif %} class="nav-link">
{{ subitem.name }}
</a>
</li>
{% endfor %}
</ul>
</div>
</li>
{% else %}
<li>
<a href="{{ item.link | relative_url }}" {% if page.url == item.link %} class="focus" {% endif %} class="nav-link">
{{ item.name }}
</a>
</li>
{% endif %}
<li class="nav-1st">
<a href="{{ item.link | relative_url }}" {% if page.url == item.link %} class="focus" {% endif %} class="nav-link">
{{ item.name }}
</a>
<div class="nav-2nd">
<ul>
{% for subitem in item.subnav %}
<li>
<a href="{{ subitem.link | relative_url }}" {% if page.url == subitem.link %} class="focus" {% endif %} class="nav-link">
{{ subitem.name }}
</a>
</li>
{% endfor %}
</ul>
</div>
</li>

Is there a reason for distinguishing between with and without subitems, or could it be simplified like this?

Comment thread docs/_data/navigation.yml Outdated

- name: Browse
link: "https://pan-ontologies.github.io/PaNET/index-en.html"
description: Ontology Specification page
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see where this description is used. Maybe add it as title to the link? (just an idea)

<a href="..." title="{{ item.description }}">

Motivation

The current structure of the homepage feels crowded and arbitrary. I suggest
to update it and group the topics.

Modification

We now have three top level topics: Home, Browse, and Documentation.
Home includes the 'Scope of PaNET' and 'Applications'.
Browse forwards to the 'Ontology Specification' page (widoco).
Documentation includes 'Standard Operation Procedure', 'Git Workflow', 'Build
the Robot Environment', and 'Make a Release'.

Additionally, the navigation layout has been improved and is now dynamic
(based on the _data/navigation.yml).

Result

The structure of the webpage is clearer and more intuitive.

Related Issues

Closes pan-ontologies#363
@kara-mela kara-mela force-pushed the ISS363-improve-webpage-structure branch from 7487bfd to efa62d0 Compare June 4, 2026 13:13
@kara-mela
Copy link
Copy Markdown
Collaborator Author

Hi @eilmiv for the detailed review! I implemented all of your suggestions and amended them.

@kara-mela kara-mela requested a review from eilmiv June 4, 2026 13:15
@kara-mela kara-mela merged commit dc8f84f into pan-ontologies:master Jun 5, 2026
3 of 4 checks passed
@kara-mela kara-mela deleted the ISS363-improve-webpage-structure branch June 5, 2026 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve the structure of the webpage

2 participants