[BOUNTY] Directory page UI improvements

[neatonk]

BOUNTY details: #37
This is a dependency of ipfs/kubo#7536

This PR implements the changes described in #37.

This is an incremental improvement over the previous version of the dir-index.html page and I suggest that a larger restructuring of the page should be considered after this PR is completed. Additional changes informed by a discussion of design constraints (e.g. file size and responsiveness) and developer workflow (e.g. build tools and minification) would lead to greater improvements.

Closes #37

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[jessicaschilling]

Thanks, @neatonk!

This looks good to me but I'd like to have a closer review by the go-ipfs core team. @aschmahmann -- do you have the time, or can you suggest another reviewer?

[jessicaschilling]

@aschmahmann -- just to note, this behaves as intended (meets all the criteria in #37 (comment) ) using the test server described here.

I'm afraid I can't explicitly confirm/deny that the test info gives us enough confidence to merge. Is this something that you or @Stebalien can investigate? Apologies for the inconvenience.

[jessicaschilling]

As noted in #38 (comment) -- this meets all the requirements using the test server, but I still would like @aschmahmann or @Stebalien to confirm that we're confident to merge.

[jessicaschilling]

It wasn’t in the original bounty spec - however, @neatonk, is that something you could take on? We may be able to adjust the bounty as a result.

[jessicaschilling]

One quick note -- can you please make the changes you made in dir-index.html in dir-index-uncat.html as well? Thank!

[neatonk]

@jessicaschilling Is dir-index-uncat.html actually in use? If not, I would prefer to leave it alone. It is not clear how the changes I made should be applied and for what purpose.

[jessicaschilling]

They are both in use, unfortunately. https://github.com/ipfs/dir-index-html#updating does include guidance to touch them both when updating, but this also could have been called out more explicitly in the issue; that's my fault.

[neatonk]

No worries and thanks for pointing that out. However, it looks to me like the two files are already out of sync. That will make it difficult for me to update dir-index-uncat.html to include the changes in this PR.

Below are two possible solutions to this problem. I am in favor of Option B since it would be a better use of time and would not delay this PR.

Option A

First, tap someone who is familiar with previous changes to dir-index.html and ask them to update dir-index-uncat.html to reflect those changes and commit the result. Then I can rebase my branch to include that commit and update dir-index-uncat.html to reflect the changes in this PR.

Option B

Finalize this PR (and bounty) without updating dir-index-uncat.html. Plan to correct this later by building dir-index.html from dir-index-uncat.html (possibly via #6). This is essentially what I was alluding to when I mentioned "developer workflow" above.

[jessicaschilling]

Option B is fine. I'll need to rationalize the two files at a later date before we can release this, but if you're able to get everything working and tested for dir-index.html that's a start.

Agreed that automating as in #6 is the best long-term solution, but we've not got anyone with the bandwidth for that at present.

[lidel]

👍 let's continue in ipfs/kubo#7536

[jessicaschilling]

Also branch chore/reconcile-uncat