-
Notifications
You must be signed in to change notification settings - Fork 5
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
Documentation #13
Comments
I can create a HOWTO page on the BioPerl wiki. I haven't contributed to the wiki before, is it considered acceptable for anyone to just go ahead and add a HOWTO? Do you think it would be ok to say that Primer3Redux is now the preferred wrapper for primer3 in BioPerl? If we place the documentation in the PODs and use a POD->wiki converter (do you have one in mind? I haven't done that yet), where should we put that, as a separate "HOWTO" in the distribution? |
I think it's better to include the docs with the distribution. Place the docs in the |
Forgot to mention the reasoning for that choice: I think it has become critical to tie in pure documentation to whatever version of BioPerl (or any related code) to the distribution, as POD, and on-line docs in the wiki or elsewhere can be updated automatically using the Mediawiki API and a perl library (I have tested this out before just on a query basis). I think we can lock pages for editing only by admins and have a bot run updates from POD to wiki markup. |
@fschwach Not sure if you planned on still doing this (it's been a while). Let me know, as the wiki is now a Github Pages repo so changes can definitely be made if you are still interested. |
Hi @cjfields , yes, it has been a while but I can still do this if it helps. Are we talking about a HOWTO now or the inline POD documentation? |
@fschwach I'm open for whatever's easiest for you, though I can easily add you to the github pages account so you can add the HOWTO there (just sent you the invite). |
We have at least two alternatives to add documentation.
.pod
extension has to be used for this. Alternatively, we can use aPOD->wiki
converter to automate updates to the BioPerl wiki, which (to me) is the best long-term solution. Disadvantage: doesn't allow rich markup.The text was updated successfully, but these errors were encountered: