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

Use Github Pages to create a simple project website #4

Open
nicocvn opened this issue Jan 31, 2021 · 6 comments
Open

Use Github Pages to create a simple project website #4

nicocvn opened this issue Jan 31, 2021 · 6 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@nicocvn
Copy link
Owner

nicocvn commented Jan 31, 2021

We can keep most of the documentation in the repo but it is usually a good idea to have a simple page other than the plain repo view.

See: https://pages.github.com/ > project site

@nicocvn nicocvn added the documentation Improvements or additions to documentation label Jan 31, 2021
@nicocvn nicocvn added this to To Do in emDNA public release via automation Jan 31, 2021
@nicocvn
Copy link
Owner Author

nicocvn commented Jan 31, 2021

@rty10 I can take care of this one but you will have to make me an admin of the project; let me know if that is fine with you

@rty10
Copy link
Collaborator

rty10 commented Jan 31, 2021

@rty10 I can take care of this one but you will have to make me an admin of the project; let me know if that is fine with you

I'm happy with you becoming an Admin for this project. This isn't listed as one of my own Projects so I do not know how to make you an Admin.

@nicocvn
Copy link
Owner Author

nicocvn commented Jan 31, 2021

Not sure how it looks on your end but typically:

  • when you are on the landing page of the repo https://github.com/rty10/emDNA you should see a settings menu in the "menu bar" with Code, Issues, Pull Requests, ... the last one should be settings
  • in the settings there should be on the left menu a "Manage Access" section
  • there I should be listed as a collaborator and you should have a way to set my access permissions as admin

Ref: https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization

@rty10 rty10 assigned rty10 and unassigned rty10 Feb 2, 2021
@rty10
Copy link
Collaborator

rty10 commented Feb 2, 2021

@nicocvn I assigned this to myself however it appears I have to pay for this service while this repository is in Private. Once this goes Public I will start the website.

@rty10 rty10 moved this from To Do to In Progress in emDNA public release Feb 2, 2021
@rty10
Copy link
Collaborator

rty10 commented Feb 27, 2021

I created a How To page that refines the documentation.html from previous installations that we can use for the website but I cannot seem to add to the site. Let me know how I can add this somewhere.

@rty10
Copy link
Collaborator

rty10 commented Feb 27, 2021

@nicocvn if you go to branch "rty10-patch-1" you will see a file called "HOWTO.md" that I have markdowned similarly to your INSTALL.md file used on the website.
I don't think I handled the branch or the pull correctly and for that I'm sorry. However, I hope the HOWTO.md file is suitable for the site. It still needs information on three tools I've never used: check-collisions, force-probe, and (one I want to practice with) pro-bind

@rty10 rty10 moved this from In Progress to Finalize in emDNA public release Mar 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Development

No branches or pull requests

2 participants