Skip to content
This repository has been archived by the owner on May 25, 2023. It is now read-only.

Denperidge-Redpencil/semantic-docs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Note: Deprecated

  • In terms of its original end functionality (implementing automated documentation in the current semantic.works website): superceded by automated-frontend-semantic-works.
  • In terms of its codebase (a Python-based git repo collector), re-written and re-worked into repo-collector

Semantic Docs

A draft for a zero upkeep documentation for mu-semtech.

  • Leverages API's to grab all public mu-semtech repos.
  • Automatically categorises repos using the mu-semtech naming scheme.
  • Manual overrides are possible to hide or move repos between categories.
  • Grabs and renders repository README's to generate documentation.
  • Easily customisable.
  • Requires no client-side JavaScript nor any non-static hosting.
  • Can be configured to automatically run on repo changes.

Usage

pip3 install -r requirements.txt
python3 app/index.py

Note: if the server you're using to view the generated .html files doesn't support navigating to /index and instead requires /index.html, you can change the nav generation in the base template.

Should this be used?

Pros:

  • No Javascript nor server needed! The content will be displayed immediately with no client-side nor server-side rendering required.
  • While currently implemented for GitHub, adapting this for a different host should require minimal effort, as as good as all GitHub specific code is separated in a different file.
  • Using Repository Webhooks the documentation can automatically be updated whenever changed, not even requiring manual intervention when new repositories are added or current repositories are archived/removed.
  • The url changes depending on which documentation you select (although that not being the case in the current docs could also be fixed over time).

Cons:

  • Not a onepager like the current front-end.
  • It's less in-tune with mu-semtech (having the docs made in Ember feels fitting due to the large adaptation of Ember in the organisation).
  • It currently looks not-very-good to say it lightly, although this can be fixed by implementing the existing styling of the original docs.

License

The documentation imported belongs to mu-semtech. The code I've written is under the MIT License.

About

Seeing if I can automate mu-semtech documentation generation!

Resources

License

Stars

Watchers

Forks