Add specification on top-nav

[Dindihub]

This PR covers issue #18

Moved specification on top-nav following a recommendation on the TUF documentation analysis

Please review @chalin @lukpueh

[netlify]

✅ Deploy Preview for tufio ready!

Name	Link
🔨 Latest commit	f497541
🔍 Latest deploy log	https://app.netlify.com/sites/tufio/deploys/66cecc58c89c250008549518
😎 Deploy Preview	https://deploy-preview-23--tufio.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[chalin]

Now that I'm seeing this, I think that we can rework (simplify) this. See inline comments.

[Dindihub]

This is ready for another review @chalin

[lukpueh]

The text reads like a general TUF project overview, and only vaguely prepares the reader for the specification.

I suggest to remove it and just leave the index. Or add a small paragraph about what the user will find in the spec. Maybe you can take inspiration from this talk. More specifically, about how the spec defines a detailed client updater workflow and otherwise TUF repo primitives (roles, metadata, delegations), which can be used as building blocks.

[Dindihub]

The text reads like a general TUF project overview, and only vaguely prepares the reader for the specification.

I suggest to remove it and just leave the index. Or add a small paragraph about what the user will find in the spec. Maybe you can take inspiration from this talk. More specifically, about how the spec defines a detailed client updater workflow and otherwise TUF repo primitives (roles, metadata, delegations), which can be used as building blocks.

@lukpueh Okay. I'll try. Thanks

[Dindihub]

@lukpueh I have edited the section and added in the video you shared for reference. Let me know what you think.

[chalin]

@lukpueh and I seem to have the same idea of having a single page (in fact, that is what I tried to convey in my round of comments from earlier).

Please make the changes suggested in the comments of this review.

[chalin]

LGTM.

There will be followup improvements to make (e.g., possibly not using type: docs or maybe hiding the left nav, but that can be done later.