Opened 2 years ago

Last modified 2 months ago

#1859 assigned defect

Outdated #fragments for common-structures in Network Database + Tunnel Routing page

Reported by: anonimal Owned by: slumlord
Priority: trivial Milestone: undecided
Component: www/i2p Version: 0.9.26
Keywords: Cc: sadie, alex_wykoff, alex_the_designer, zab
Parent Tickets:

Description

https://geti2p.net/en/docs/spec/common-structures#struct_RouterInfo

should be

https://geti2p.net/en/docs/spec/common-structures#routerinfo

etc.

These fragments are used throughout the page, at least for the specification links.

Subtickets (add)

Change History (11)

comment:1 Changed 2 years ago by anonimal

Also effects Tunnel Routing page. This issue may be elsewhere throughout the site.

Re-naming ticket.

comment:2 Changed 2 years ago by anonimal

  • Summary changed from Outdated #fragments for common-structures in Network Database page to Outdated #fragments for common-structures in Network Database + Tunnel Routing page

comment:3 Changed 11 months ago by meeh

This seems to be fixed?

comment:4 Changed 7 months ago by zzz

  • Owner set to slumlord
  • Status changed from new to assigned

assigning to slumlord to verify and fix or close

comment:5 Changed 7 months ago by slumlord

Doesn't look fixed to me.

e.g. in common-structures
line 824:

<li>For <a class="reference external" href="/en/docs/spec/i2np#struct_GarlicClove">Garlic Cloves</a>, the Certificate is always NULL, no others are currently

while on i2np
line 726:

<div class="section" id="garlicclove">

No mention of #struct_GarlicClove there at all.

Checking in i2p.www/i2p2www/spec/common-structures.rst
line 353:

.. _Garlic Cloves: {{ site_url('docs/spec/i2np') }}#struct_GarlicClove

This may be a matter of a mass find & replace but I will hold off on that until we can figure out all of the changes that need to be made to get our documentation to a consistent state.

comment:6 Changed 6 months ago by zzz

There's some sort of page generation macro magic that str4d added that changed all the anchors. He then added them back with lines like:

.. _struct-GarlicClove

which then get converted to ids in the HTML. You have to view-source in the browser to see HTML, they aren't in the RST markdown.

It appears that the problem is that a struct_GarlicClove fragment won't match a struct-GarlicGlove? HTML ID. Dash vs. underscore. Not sure if _struct_GarlicClove is allowed by the markdown or not. If so, you could change the markdown. If not, you'd have to change all the links. Suggest you ask str4d for guidance.

comment:7 Changed 6 months ago by slumlord

str4d hasn't responded to any of my dozen messages over the past year and a half since meeting him, sending him a message would just be a waste of time for me. I'll try too look at the code a little more, thanks for the pointers.

comment:8 Changed 4 months ago by zzz

  • Cc sadie alex_wykoff alex_the_designer zab added

More info on the magic - maybe - see the mtn log for i2p2www/spec/spectags - or maybe it's completely unrelated.

cc'ing alex as he may be making better progress on understanding the site as a part of his redesign work. The website backend is unsupported at this point as str4d is unresponsive over the last two years. We need to grow a new support person or team from scratch. If it's not slumlord then maybe it's alex or maybe it's time to go find somebody new. This ticket is trivial but we have much bigger changes coming. If we can't cover it ourselves we need to budget for hiring somebody next year.

comment:9 Changed 4 months ago by sadie

happy to take a crash course ;)

comment:10 Changed 2 months ago by slumlord

I'm happy to contribute to to website stuff but it's difficult to sit at a computer separated by a couple of timezones from everyone else and try to figure out things with little documentation/direction.

Perhaps me, Sadie, Alex and anyone else interested/capable/bored can have a meeting during 35C3 to get a better understanding of how the website stuff works as well as figure out processes for carrying out maintenance on the website as we move forward so that if we transition to a new website system we'll have a team & processes in place for keeping things in good, maintainable condition.

comment:11 Changed 2 months ago by sadie

This is a good course of action. We need to create a plan for this that is maintainable and this should be discussed in Leipzig.

Note: See TracTickets for help on using tickets.