• Current page does not respond with a 200 when offline
  If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

• start_url does not respond with a 200 when offline
  No usable web app manifest found on page.
  A service worker enables your web app to be reliable in unpredictable network conditions. Learn more.

• Lua scripting (/packetcraft/lua_scripts.md)
• Scripting (/packetcraft/scripting.md)

• Content is not sized correctly for the viewport
  The viewport size is 808px, whereas the window size is 1440px.
  If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.

• What does having some of the outputs in parentheses mean?

• I really think this table would benefit from some quick links to each tool, or a tool-tip for each tool - something that just reminds the reader what each one does. Perhaps also some examples too. And one more suggestion would be to include sample output when you show a sample command-line - helps me to understand better what the command is doing. I write this from the point of view of someone who was arrived at this page with a google search, so without the context of the rest of tshark.dev - someone just looking for a quick answer.

• Possibly show samples for json format, explain what ek output format is.

• Small typo, confrom -> conform

Cheers @gcla

Convert the <img... to in parsing script

It looks like the webdev consensus is that they add noise, especially for technical articles

This should show up as an issue

Current Search

Upper lefthand corner shows a list of pages that match content

Desired Search

Page opens showing context, like google results so it's easier to find things. Specifically, have link at the top with a paragraph below where the terms occur in context, ideally highlighted as well.

/capture/limit_size.md

Instead of utteranc.es.

https://wiki.wireshark.org/SampleCaptures
and what it links to.

This should be a table with available online packet captures, stats about them (protocols involved), duration, number of packets, and description from the website

There are a couple right now, but this section should be significantly larger

This should be easy to achieve by manually changing the rectangles in svgs.

Feedback from Jasper:

The "Sanitze the Packet Capture" mentions "reordercap" but doesn't explain what could cause packets to be out of order. This is one of the parts where I think you'll add more content later to explain in greater detail why someone might need to use those tools.

This covers /share/pcap_preparation/#sanitize-the-packet-capture, /edit/reordercap

The problem is that people refer to both the GUI and project as a whole as "Wireshark".

Make it clear in the README when you are referring to tshark, GUIreshark, and the Wireshark project generally. This could mean using lowercase wireshark to refer to the gui or using "GUIreshark".

It should be possible to increase the size in the theme.

Summary is only 2 sentences, but should be longer (maybe explain history and relationship with Wireshark?)

You can still use the minimap, but text is missing from the rectangles.

Text in mermaid map is not visible on small browser widths or mobile screens. Changing from graph type LR to TD for specific widths (requires testing) would fix this.

It may make sense to hide the mermaid map if the width becomes too small.

Create a standard for attributing articles and stick to it (year, name, article title/link, description). You might as well make a pre-commit hook for this to make sure you don't lose this consistency.

/analyze/add_context/name_resolution.md

/analyze/packet_hunting.md

This was recognized as an issue in minify and was fixed in v2.5.1.

Now we just need to wait for it to percolate into hugo versions so that in netlify commands, --minify can be specified.

Should be after intro and prior to table of contents. Use 50% width

• Form elements do not have associated labels
  Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

  Failing Elements
  input#search-by
  

For existing articles

Cover how Wireshark fits into its niche and how other tools also play a part in this ecosystem.

• via Jasper

Doesn't need to be obtrusive, just something that's visible

I didn't have Lucida Console.

4 files are resources not found. Redownload them from learn theme to /static/webfonts.

/webfonts/fa-regular-400.svg
/webfonts/fa-regular-400.woff
/webfonts/fa-regular-400.ttf
/webfonts/fa-regular-400.woff2

• Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.

Multiple people I've shown this website to have tried to click it. It should be a link to something (Like pcap formats) or not exist.

/capture/capture_filters.md

Lighthouse identifies multiple ways to speed up the website. Do those.

• [id] attributes on the page are not unique
  The value of an id attribute must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.

  Failing Elements
  
  text#text3
  text#mermaid-1560775179966Text
  

/analyze/tshark_analysis.md

• Background and foreground colors do not have a sufficient contrast ratio.
  Low-contrast text is difficult or impossible for many users to read. Learn more.

  Failing Elements
  input#search-by
  a.highlight
  a.highlight
  a.highlight
  a.highlight
  a.highlight
  ...
  

• Create stub articles for each planned article
• Finish mermaid map with planned articles
• Add a link for every mermaid map item

Should be first article in /capture

• via Jasper

https://utteranc.es/

This should render as a warning, but just renders as text:

{{% notice warning %}}
Caution: Flying monkeys may cause problems
{{% /notice %}}

Each section should have an intro (##) which explains exactly what the section contains and what you can do with that information.

The introduction for main page should say something like (but as clearly and with as short sentences as possible):

tshark.dev exists to help you script your pcap pipeline using tshark and friends. Bash is used throughout, with the expectation that it is cross-platform with the advent of WSL on Windows.

• Lists do not contain only <li> elements and script supporting elements (<script> and <template>)
  Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.

This will depend on hugo-learn vs readthedocs format

Tshark | Sample Interfaces

Default interfaces on Windows, Macos, Linux, and FreeBSD

http://localhost:1313/capture/sources/sample_interfaces/

• Tap targets are not sized appropriately
  29% appropriately sized tap targets
  Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
  Tap target (links in the TOC are marked as hits)

• Ensure text remains visible during webfont load
  Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more

• Does not register a service worker that controls page and start_url
  The service worker is the technology that enables your app to use many Progressive Web
  App features, such as offline, add to homescreen, and push notifications. Learn more.

• Web app manifest does not meet the installability requirements
  Failures: No manifest was fetched, No <meta name="theme-color"> tag found.
  Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.

Greetings, fire here!

@pocc recently invited @fire-bot to this repository. Before fire is enabled, @pocc needs to complete a few steps:

Complete fire setup now

Only @pocc will be able to enable fire using the above link. If someone added fire by mistake, feel free to remove @fire-bot from your repo's collaborators.

/packetcraft/deconstructing_pcap.md

Should go into it's own section with pcap/pcapng format