[community] moving the tor browser manual to Lektor

[gus]

Hi, I started to collect bugs and changes here:
https://pad.riseup.net/p/tb-manual-updates-keep

Please, help to find more bugs!

Maggie, tell me if you need help to apply these changes. :)

We could make a new blog post announcing the manual update.

cheers,
Gus
 
On Mon, Nov 05, 2018 at 07:16:17PM +0100, silvia [hiro] wrote:
> Hi all,
> 
> I am going to give a patch to sys admin people and open the tickets
> needed for this.
> 
> Talk soon,
> 
> -hiro
> 
> On 11/5/18 5:15 PM, Alison Macrina wrote:
> > Hi all, just checking in about this. We talked in Mexico about Maggie
> > working on this. I believe what needs to happen now is that the current
> > manual needs to get replaced with this one, so what needs to happen to
> > make that a reality?
> >
> > Alison Macrina
> > Director
> > Library Freedom Project
> >
> > silvia [hiro]:
> >>
> >> On 09/19/18 16:28, emma peel wrote:
> >>> silvia [hiro]:
> >>>> Hey everyone,
> >>>>
> >>>> I have been chatting with Colin about moving the tor browser manual to
> >>>> lektor.
> >>>>
> >>>> This is completely possible, but I wanted to understand a few things.
> >>>>
> >>>> - Can we use the styleguide? Or do we have to keep the current design?
> >>>>
> >>>> I am asking this because we have been testing the styleguide a lot with
> >>>> Lektor and it would be the easiest thing for me to create a framework in
> >>>> lektor to which you can just port the content from the system you are
> >>>> using to Markdown.
> >>>>
> >>>> This will also be the same structure than the support portal, so it will
> >>>> be easier down the road, to port the manual to the support portal.
> >>>>
> >>>> How does it sound to you?
> >>> Yes, I like that idea!
> >>> Actually, I was pitching the move to lektor with the reasoning that we will
> >>> be able to share work already done for styling in the support portal, and all
> >>> the other things you are fixing with lektor (deb packages, l10n, etc)
> >>>
> >>>
> >> Hi all,
> >>
> >> Here is the skeleton of the new tor browser manual:
> >> https://gitweb.torproject.org/project/web/manual.git/
> >>
> >> It contains the structure, style and topic.
> >>
> >> Each topic has a folder in the contents folder under the root of the
> >> project.
> >> If you edit the contents.lr file inside each of the topic folders you
> >> will be able to edit title, description and body for the topic.
> >> Title and description are strings.
> >> The body is Markdown and it is where the actual content for each topic goes.
> >>
> >> Please fell free to try this out on your local machines. There will be
> >> things that will need to be changed, so feel free to collect bugs and
> >> issues.
> >>
> >> Talk soon,
> >> -hiro
> >> _______________________________________________
> >> tor-community-team mailing list
> >> tor-community-team at lists.torproject.org
> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team
> >>
> _______________________________________________
> tor-community-team mailing list
> tor-community-team at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-community-team/attachments/20181116/15b5e04b/attachment.sig>