ServPub

https://ctp.cc.au.dk/pad/p/servpub_book

 

ServPub

The proposed book is an extension of the platform ServPub, a social and technical infrastructure for research and practice in experimental publishing. It is developed by a collective of scholars, artists, activists, designers, creative technologists, working together to develop a self-hosted and self-organised sustainable resource and workflow for book production that challenges normative open publishing paradigms. The resulting publication will be both a critical account of the process of production and at the same time detailed documentation that allows others/publishers to produce/fork their own versions.

See more info herefor the Launch of Experimental Book Publishing Pilot Project ‘Servpub – A Collective Infrastructure to Serve and Publish’

Servpub involves the following groups/collectives: noNames (aka Slade School of Fine Art, part of the University College London, and CSNI, a research centre at London South Bank University); SHAPE, a research project at Aarhus University focussed on digital citizenship; Minor Compositions, a publisher of books and media drawing from autonomous politics, avant-garde aesthetics, and the revolutions of everyday life; In-grid, a London-based trans*feminist collective of artists/educators/technologists working in and around digital infrastructure; Syster Server, an international collective run by feminists that offers internet-based FOSS tools to its network of feminists, queers and trans; Creative Crowds, a shared server for FLOSS publishing experiments to explore how different ways of working are shaped by (and shape) different realities.

wiki4print Environment

• Servpub wiki4print environment: PDF:ServPub
• preview the PDF: https://wiki4print.servpub.net/flask/pdf/ServPub

To get started

1. Make sure that you do not delete the line: <noinclude>[[Category:ServPub]]</noinclude>, as this will add your page to the Category:ServPub. It can be written anywhere on the page, the bottom is usually where most people put it.
2. For editing, please see the editing guide.
3. (NOTE: for discussion, are we using this feature?) For writing feedback/comments to each others contributions: go to the page of the contribution and click the double speech bubble on the top left corner (under the title, on the left side of the star). See the talk page section in the editing guide for more info.

Content Template

• Make sure the title of your chapter is formatted as a Header 2 / h2

• If your chapter has author/contributors please set these as h3

• All subsequent titles should be h4 no matter if your chapter has authors/contributors

• Can each chapter please choose 3 unicodes that identifies their chapter.
• Please include in-text references notes using the <ref> markup, here is an example:

This book is an intervention in these ongoing debates, emerging out of a particular history and practice of experimental publishing <ref> Janneke Adema, "Experimental Publishing as Collective Struggle: Providing Imaginaries for Posthumanist Knowledge Production", Culture Machine 23 (2024), https://culturemachine.net/vol-23-publishing-after-progress/adema-experimental-publishing-collective-struggle/ </ref> and etc ...

See Example Page for template example.

NOTE: This template is still under construction, we will let you know when it's ready to implement on your own chapters.

Debugging References

Please don’t use:

<ref name=":0">

Please just use standard <ref></ref> tags

Be careful about pairing up your ref tags correctly so for each opening <ref> make sure that there is a closing </ref> tag. For a first check if you can search for <ref> in your text, count how many you have and then search for </ref> and then count how many you have. Make sure the two numbers match.

This is not a guarantee that you will have correctly formed tags in your text, for those who need to debug / find malformed refs the best way to go about it is to use regex search in a text editor of choice. Here is one option for using Visual Studio Code: How to search using Regex in VS Code

This regex will search for all pairs of refs that are incorrect with any other html tags in between <> e.g. another <ref> or nowiki:

<ref>[\s\S]*?<\/ref>

This regex will search for correctly formed <ref></ref> pairs:

<ref>[^<>]*?<\/ref>

Extra Pages

• PublicationDetails
• Foreword (or something like it)
• Servpub images

etc

Editorial contributions / Chapters

0. Preface (Rebekka & Simon)
1. Being Book
2. Ambulant Infrastructure
3. Feminist Networking
4. Open Source Design & Processes
5. Praxis Doubling
6. Angels of Our Better Infrastructure
7. Referencing
8. Collective Statement
9. Bibliography
10. Contributors
11. Colophon

Glossary