stackmuncher / stm-html Goto Github PK

https://stackmuncher.com/Wenzel

Not showing any libraries at all.

Google search results should have more useful info than

to include the top few techs, the date of the last update and available for hire badge

HackerNoon has the date

and Quora has a useful snippet

The snippet should contain enough useful info for the searcher to want to know more.

What the heck is stm-html?

Maybe call it about or about-pages. It should be quite self-descriptive.

This is what the top internal links look like at the moment

https://stackmuncher.com/?CSS | 4,629
https://stackmuncher.com/?Python | 3,319
https://stackmuncher.com/?reStructuredText | 2,456
https://stackmuncher.com/?Rust | 1,907
https://stackmuncher.com/AbenezerMamo | 139
https://stackmuncher.com/ItzKartik | 100

It will probably make more sense to have a directory-like structure for the top technologies. E.g. stackmuncher.com/lang/rust

The old ?rust links should return a permanent HTTP 301 response.

https://stackmuncher.com/mourice-oduor

Website: [email protected]
links to https://github.com/[email protected]

Jul 06 21:45:49.283 WARN stm_html::html::home: Invalid keyword: socks
Jul 06 21:45:49.283 WARN stm_html::html::home: Invalid keyword: converter
Jul 06 21:45:49.283 WARN stm_html::html::home: Invalid keyword: packages
Jul 06 21:45:49.283 WARN stm_html::html::home: Invalid keyword: converters
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: opus
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: treewalkers
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: _html5lib
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: _lxml
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: defs
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: monkey
Jul 06 21:45:49.284 WARN stm_html::html::home: Invalid keyword: DistlibException

Report::reports_included attribute is an array of S3 keys for the reports that are translated into project names on the page.

It is being phased out in favour of a more rich pub projects_included: HashSet<super::report_brief::ProjectReportOverview>

We can't just drop it because all reports would need to be re-processed for the front end to work.
This can be done after total re-processing of all repos for some other more important reason.

Relates to stackmuncher/stm_app#13