Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve the "how to publish content" manual #244

Closed
vjpixel opened this issue Oct 4, 2019 · 14 comments
Closed

improve the "how to publish content" manual #244

vjpixel opened this issue Oct 4, 2019 · 14 comments
Assignees
Labels
artist documentation Creating documentation for users and artists, and formal reports enhancement New feature or request
Milestone

Comments

@vjpixel
Copy link
Member

vjpixel commented Oct 4, 2019

Create sections for "Markers", "Objects", "Artworks" and "Exhibitions", and detail more each of the steps.

@vjpixel vjpixel added the enhancement New feature or request label Oct 4, 2019
@vjpixel vjpixel added this to To do in Content/Outreach/Documentation/Translation via automation Oct 4, 2019
@vjpixel vjpixel added this to the Launch milestone Jan 4, 2020
@vjpixel vjpixel added artist documentation Creating documentation for users and artists, and formal reports labels Jan 24, 2020
@vjpixel
Copy link
Member Author

vjpixel commented Jan 24, 2020

@discombobulateme can you please have a look at this documentation and suggest some improvements?

@vjpixel vjpixel moved this from To do to Release backlog in Content/Outreach/Documentation/Translation Jan 30, 2020
@vjpixel
Copy link
Member Author

vjpixel commented Sep 22, 2020 via email

@MatheusBlanco
Copy link
Contributor

It's related to the actual documentation.

On Mon, 21 Sep 2020 at 21:54, Matheus Salles Blanco < @.***> wrote: Is this issue related to the actual manual documentation? Or to a in-application tutorial of how to publish that should be improved? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#244 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH4ULG6BN72GEWAOFVYY33SG7YT7ANCNFSM4I5SVXAA .
-- Angelo Pixel https://www.linkedin.com/in/vjpixel/

Got it! Thank you very much!

@vjpixel
Copy link
Member Author

vjpixel commented Sep 22, 2020

If you need any more help, ping me.

@MatheusBlanco
Copy link
Contributor

Hi, I wanted to check up on some doubts regarding this documentation.

First is about its language. We wrote this manual in english and would like to know whether it is ok or if portuguese would be more appropriate for the viewing users.

@MatheusBlanco
Copy link
Contributor

Secondly is about the document viewing framework. I believe Jandig is using Sphynx to compile and display its documentation, correct? When I ran the local build on my computer, DJANGO threw an error regarding the index.html file when I tried to access the "Help" page. This happened both on the develop branch and on the branch created for this specific issue.

Here's a screenshot of the error shown in the browser:
image

And when I tried to look it up on the code, there was an error on the index.rst file, inside the docs folder:
image

Is this an expected error? Does it require a specific configuration in order for me to access the help page?

@vjpixel
Copy link
Member Author

vjpixel commented Oct 1, 2020

Hi Matheus,

I see that you wrote the manual in English. It's amazing because we want to attract more international users.

But the majority of our users are Portuguese speaking, so it's good to keep both versions.

Do you think it's possible to translate the new version to Portuguese, so we have both?

@pablodiegoss can answer about Sphynx better than me.

@MatheusBlanco
Copy link
Contributor

Hi Matheus,

I see that you wrote the manual in English. It's amazing because we want to attract more international users.

But the majority of our users are Portuguese speaking, so it's good to keep both versions.

Do you think it's possible to translate the new version to Portuguese, so we have both?

@pablodiegoss can answer about Sphynx better than me.

Yes, of course. I will leave the Pull Request with the WIP tag for the time being so that I can translate it.

@MatheusBlanco
Copy link
Contributor

It's done! I have changed the tag to REVIEW.

@pablodiegoss
Copy link
Member

Secondly is about the document viewing framework. I believe Jandig is using Sphynx to compile and display its documentation, correct? When I ran the local build on my computer, DJANGO threw an error regarding the index.html file when I tried to access the "Help" page. This happened both on the develop branch and on the branch created for this specific issue.

Here's a screenshot of the error shown in the browser:
image

Your comment is right, we use .rst files to describe our docs and Sphinx to generate html files from them, which django-docs routes and make them linkable through "/docs".

Awesome that you noticed that error, we moved around some folders on some update and now Sphinx wasn't being able to find the index.html that it generated previously. I've found the problem and pushed a fix to the develop branch, can you verify if the error still happens after pulling this commit?

And when I tried to look it up on the code, there was an error on the index.rst file, inside the docs folder:
image

Is this an expected error? Does it require a specific configuration in order for me to access the help page?

This seems to be just an error from your editor that isn't being able to recognize the RST syntax... it seems that you are using VScode, right?
I'm using the reStructuredText extension to get syntax highlighting and suggestions for rst, maybe installing some extension fixes your problem
image

@shayanealcantara
Copy link
Contributor

Awesome that you noticed that error, we moved around some folders on some update and now Sphinx wasn't being able to find the index.html that it generated previously. I've found the problem and pushed a fix to the develop branch, can you verify if the error still happens after pulling this commit?

@pablodiegoss I tested here in our branch and your last commit fixed the problem 😄

shayanealcantara added a commit to GCES-Jandig/Jandig that referenced this issue Oct 9, 2020
@vjpixel
Copy link
Member Author

vjpixel commented Oct 18, 2020

Sorry for the delay. I've just commented on #330 .

vjpixel added a commit that referenced this issue Oct 20, 2020
@MatheusBlanco
Copy link
Contributor

Hello! Since this PR was already merged, could this issue be closed?

@vjpixel
Copy link
Member Author

vjpixel commented Dec 7, 2020

Yep!

@vjpixel vjpixel closed this as completed Dec 7, 2020
Content/Outreach/Documentation/Translation automation moved this from Release backlog to Done Dec 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
artist documentation Creating documentation for users and artists, and formal reports enhancement New feature or request
Development

No branches or pull requests

4 participants