-
We currently have documentation from the Spring 2017 event about how the conference was planned. This docu
6 KB (880 words) - 18:18, 17 September 2024
-
* Streamline documentation so that it is using best practices and make it user friendly - Lisa Rabey
18 KB (2,911 words) - 15:15, 1 December 2014
-
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation
...Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.
10 KB (1,509 words) - 00:26, 9 February 2015
-
...PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manag
'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''
20 KB (2,997 words) - 22:07, 9 February 2015
-
...hat combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to cre
...documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes ofte
102 KB (15,718 words) - 01:03, 8 November 2014
-
We share common issues surrounding documentation, but we also have unique perspectives and expertise that both sides can sha
Remember, like metadata, documentation is a love note to the future.
3 KB (423 words) - 21:44, 6 February 2015
-
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experien
10 KB (1,435 words) - 13:54, 8 March 2016
-
.../17C5BGX62JmOXtNrVstROwD-bMCMeuokf7tp76L5Htss/edit#heading=h.da50bjnv3ujy| Documentation Group Recommendations]]
512 bytes (62 words) - 15:19, 2 September 2015
-
* Shared space for documentation - Getting lists of registrants to the workshop leaders
## Say we're working on core space for documentation and they will be notified.
21 KB (3,253 words) - 16:21, 23 February 2016
-
...//wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.
15 KB (2,365 words) - 14:29, 19 November 2015
-
# Using Sphinx for Documentation - Dan Gillean
3 KB (428 words) - 19:29, 22 March 2016
-
...ike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.
12 KB (1,802 words) - 04:04, 9 March 2017
-
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experien
15 KB (2,073 words) - 07:21, 22 June 2017
-
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experien
== Additional Documentation ==
2 KB (370 words) - 15:30, 11 September 2016
-
== Additional Documentation ==
762 bytes (107 words) - 15:23, 11 September 2016
-
== Additional Documentation ==
2 KB (319 words) - 19:01, 4 January 2017
-
== Additional Documentation ==
875 bytes (119 words) - 17:18, 28 September 2016
-
== Additional Documentation ==
3 KB (407 words) - 20:09, 14 December 2016
-
== Additional Documentation ==
490 bytes (65 words) - 15:36, 11 September 2016
-
== Additional Documentation ==
567 bytes (76 words) - 15:36, 11 September 2016
