organize hackweek on documentation
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Gaba changed due date to March 21, 2023
changed due date to March 21, 2023
- Gaba removed due date
removed due date
- Gaba changed due date to May 08, 2023
changed due date to May 08, 2023
- Gaba removed due date
removed due date
Collapse replies - Developer
Gaba (@gaba):
Gaba commented:
Applications team's best week for this hackweek is mid-July!
If that's week 28 (7/10-7/16) then sounds good to me! I'd hope not week 29 as I'd be on vacation then (which is a good thing by itself, but...).
1
Collapse replies - Developer
Gaba (@gaba):
Gaba commented: #115 (comment 2910626)
Week 33 from August 14th to August 18th seems to be the best candidate so far.
There will be a bunch of people at CCCamp2023 during that time (at least 7 or 8).
- Gaba changed due date to June 27, 2023
changed due date to June 27, 2023
- Gaba closed
closed
- Gaba moved to tpo/community/hackweek#2 (closed)
moved to tpo/community/hackweek#2 (closed)
- Silvio Rhatto marked this issue as related to #190 (moved)
marked this issue as related to #190 (moved)
- Developer
Some ideas
Dumping some ideas about structural changes that improves the overall documentation ecosystem:
-
Onion MkDocs:
- Provide support for people/teams that want to convert their wikis to or have docs for their projects using Onion MkDocs.
-
Convert some GitLab wikis to GitLab pages using Onion MkDocs:
- Overview: tpo/tpa/team#41119 (comment 2898441)
-
Candidates:
- The Hackweek project itself: https://gitlab.torproject.org/tpo/community/hackweek
- Onion Support Wiki: https://gitlab.torproject.org/tpo/onion-services/onion-support/
- Tor Policies repository: tpo/community/policies#3 (closed)
-
Investigate how Onion MkDocs could be a TPA-RFC-38 wiki replacement (#40909) · TPA / TPA team (tpa rfc 38 new wiki service):
- One approach would be to create a script that import content from some existing GitLab wikis into a single Onion MkDocs instance, to see how it would like to have a convergent "documentation integration" place. How it could be structured? Could it be easily searchable? What would be the best practices for this?
-
Onion TeX Slim enhancements:
- Dockerfile for local builds.
- Test and improve the LaTeX templates.
- Add more functionality (graphics etc).
- Localization support, at least for the Markdown/Pandoc version.
-
Add Onion TeX Slim support in a
slides/
ordocs/slides
folder.
-
Onion Reveal:
- Write a reveal.js compiler similar to Onion TeX Slim:
- Makefile that traverses a folder looking for
.md
files. - Then builds the HTML slides using a pandoc reveal template.
- With support for QR code generation.
- With CI/CD for automation.
- Related issues:
- Examples:
- Tor Project | Helping survivors of domestic violence
- Files · main · The Tor Project / Web / community · GitLab
- content/training/resources/helping-survivors/contents.lr · community
- templates/slideshow.html · main · The Tor Project / Web / community
- models/slideshow.ini · main · The Tor Project / Web / community
- assets/static/revealjs/dist/theme/tor.css · community
- Helping Survivors of Domestic Violence
- Makefile that traverses a folder looking for
- Write a reveal.js compiler similar to Onion TeX Slim:
Edited by Silvio Rhatto -
Onion MkDocs:
- Silvio Rhatto marked this issue as related to tpo/community/hackweek#5 (closed)
marked this issue as related to tpo/community/hackweek#5 (closed)
- Silvio Rhatto mentioned in issue tpo/community/hackweek#12 (closed)
mentioned in issue tpo/community/hackweek#12 (closed)