Commit 7a1efc48 authored by julientaq's avatar julientaq
Browse files

add CI for automated deployment

parent 11fe91fa
Pipeline #382 failed with stage
in 6 seconds
image: registry.gitlab.com/pages/hugo:latest
stages:
- deploy
variables:
GIT_SUBMODULE_STRATEGY: recursive
test:
script:
- /home/linuxbrew/.linuxbrew/bin/hugo
except:
- master
pages:
script:
- /home/linuxbrew/.linuxbrew/bin/hugo
artifacts:
paths:
- public
deploy:
stage: deploy
environment:
name: production
url: https://www.pagedjs.org
only:
- master
- master
script:
- npm i
# your build command
- hugo
- npx netlify-cli deploy --site $NETLIFY_SITE_ID --auth $NETLIFY_AUTH_TOKEN --prod
\ No newline at end of file
......@@ -19,7 +19,7 @@ cover: "img/1139e889a554ab3a295840.jpg" #link to the printing machine we can upd
<!-- {{<img class="print-machine" src="img/1139e889a554ab3a295840.jpg">}} -->
**Paged.js** is an open source and free library to paginate content in the browser, to turn webpages in beautiful PDF. If it's your first encounter with the project, you may want to [read a bit about how it came to life](about). You may also want to [test the library in our Codepen](codepen) or [follow the documentation](doc).
**Paged.js** is an open source and free library to paginate content in the browser, to turn webpages in beautiful PDF. If it's your first encounter with the project, you may want to [read a bit about how it came to life](about). You may also want to [test the library in our Codepen](https://codepen.io/collection/nVbYGB) or [follow the documentation](documentation).
Or maybe, you want to read the [latest news](blog/) around Paged.js and CSS print.
---
title: "Long time no see Paged.js, where have you been?"
title: "And we’re back!"
date: 2020-01-27T15:56:54+01:00
draft: false
intro: "After a year of undercover work in the realm of printing HTML, we’re proudly introducing the new Paged.js website. Welcome to the new era of HTML to print"
intro: "After a year of undercover work in the realm of printing HTML, we’re proudly introducing the new Paged.js website."
tags:
- pagedjs
- update
......@@ -10,42 +10,32 @@ tags:
---
Paged.js is back folks, happy new year!
It’s been quite some time since we haven’t spoke, but truth is, we got a little bit busy to bring paged.js to new heights!
It’s been quite some time since we haven’t spoke, but truth is, we got a little bit busy to push paged.js to new heights!
First, we are now under the flag of the Cabbage Tree Labs,next to amazing projects: Wax, the word processing engine for the web, and Xsweet, the Microsoft .docx format to HTML converter. All of these tools are open source, under MIT licence, and you should definitely check what you can do if you use those together (you can check Editoria, which now takes everything from those three tools to make books in the same app!)
And that’s just the beginning: as we’re writing these words, we’re polishing the paperworks to be members of the W3C, to finally take part of the conversation regarding web design for print with HTML and CSS. We’ll be more involved in the future of the specifications for print, and we’ll do what we need to make those go the road we want.
And that’s just the beginning: as we’re writing these words, we’re polishing the paperworks to be members of the W3C, to finally take part of the conversation regarding web design for print with HTML and CSS. We’ll be more involved in the future of the specifications for print, and we’ll be happy to take the discussion further to handle things that print people need.
The team hasn’t changed at all, but what we’re doing a bit: Fred, our lead dev on Paged.js, is still doing all the development work to make sure Paged.js handles the content it gets, Julie keeps digging the specifications and is pushing us to write some specifications of our own (pretty sure that you’re gonna hear about margin notes pretty soon), Adam keeps looking at us, taking care of our needs, making sure that we’re all alright and I started to work full time on Paged.js: building the website, helping the new comers and the old friends -- we’ll have a lot to tell over the coming months.
As a good first move, Julie is writing down some specifications for side and margin notes, that we’d like to discuss with everyone involved.
There is a lot of lost content in the pagedmedia.org website. A lot of it are related to Paged.js so we’re gonna revisit a lot of those so it won’t get lost later on. And we also have quite some articles coming, so if you’re into baseline, pdf and printing, stick around for a bit.
We also now have a better and usable documentation. For the last year, we’ve been writing scripts and plugins for Paged.js in order to do specific things: table of contents, footnotes, fullpage images, spreads, etc. A lot of those comes from the community, and are part of the gitlab demo repo. But we believe that there should be a place to keep those up to date, and this website will be it. We still need to edit some a bit. If you’d like to make some edits in the documentation, or share your own demo, please do so, it’s all available on gitlab and we’ll be happy to merge new things. Everything related to paged.js will be in one specific place!
Each of those can be used in any publishing workflow.
We also want to show all the good that people using paged.js are doing: [Atla](https://www.atla.com) are now using Editoria as their only tool to manage workflow, content, editing, and publishing, and Paged.js is their main tool to generate the PDF they send to the printer. The people behind Atla has a high idea of what “open” means, thus they want to share their book templates as open source.
There has been quite a lot of content on the pagedmedia.org website, but most of it bein’ related to paged.js we’ll update those and reupdate them once in a while.
Our friends a [Booksprints](https://www.booksprints.net/) comissioned two designers to produce four CSS templates to be used with Paged.js. Agathe Baez and Manuel Vazquez worked closely with us to be able to produce good looking templates, and they’re open. You can download those and publish your own books. The collection keeps growing, which is pretty amazing.
We also now have a nice and usable documentation. For the last year, we’ve been writing scripts and plugins for Paged.js in order to do specific things: table of contents, footnotes, fullpage images, spreads, etc. A lot of those comes from the community, and are part of the gitlab demo repo. But we believe that there should be a place to keep those up to date, and this website will be it.
We also want to show all the goods that people using paged.js are doing: [Atla](https://www.atla.com) are now using Editoria as their only tool to manage workflow and editing, and are using Paged.js to generate their PDF. And since the folks behind Atla have a high idea of what Open Source means, they want to share their book templates as open source.
Booksprints comissioned two designers to produce four CSS templates to be used with Paged.js. Agathe Baez and Manuel Vazquez worked closely with us to be able to produce good looking templates for Paged.js. Those are mainly mainly to be used within Editoria, but the collection keeps growing, which is pretty amazing.
Our french friends at C&F editions uses paged.js to publish their collection named “Intervention”. Using only open tools, they manage to build a whole book production workflow that end up and libraries and bookshops, as physical books and a digital ones.
After two years of Paged.js, we’re also met great contributors around the place: Thomas Parisot, who gave quite some time to the project by helping us on the codebase, Guillaume Grossetie, who’s made a pretty impressive Asciidoc Paged.js plugin (make books out of asciidoc!).
Our french friends at [C&F editions](https://cfeditions.com/) use paged.js to publish all the book of their “Intervention” collection. This is a great exemple of how you can make book without any proprietary software! Using only open tools, they manage to build a whole book production workflow that end up in libraries and bookshops, as physical books and a digital artifacts.
Last, but not least, there has been quite some movement on the community side: our [mattermost](https://mattermost.pagedmedia.org) is now counting 150 people from all around the world. The [gitlab](gitlab.pagedmedia.org) is also becoming a place where users comes with needs, but also with solutions: the latest update to paged.js reduced the amount of time needed to produce a book by at least 20 times and this was a nice catch from Gregorio Roper. And it’s not finished: we also met great contributors around: Thomas Parisot, who gave quite some time to the project by helping us on the codebase, Guillaume Grossetie, who’s made a pretty impressive Asciidoc Paged.js plugin, Romain Lesur, Erik Schilling, Nellie McKesson. And those who came on the mattermost to share solutions to problem others discovered on the road.
So this is what this website will be about: keeping tracks on everything HTML to print related, and welcoming everyone would want to play ball with us.
See you soon!
{{< signature name="Julien Taquet" image="https://github.com/julientaq.png" >}}
From posters to interfaces, I’ve been designing user experiences for a decade, with a soft spot for books. If computers and networks are strongly asking “what is a book today?” I’d like to push the thinking further. And since I always like to do things in a different way, let’s turn off InDesign for a while and see where –and if– we’ll be stopped in the making of books.
{{< /signature >}}
Before we get back to regular articles about printing using web technologies, let’s take a bit of time to discuss what happened last year in paged.js world.
{{< /signature >}}
\ No newline at end of file
[build]
publish = "public"
\ No newline at end of file
......@@ -86,7 +86,7 @@ article {
figure {
grid-column: left/end;
}
p, ul, ol , h1, h2, h3, h4, h5, h6 , blockquote{
p, ul, ol , h1, h2, h3, h4, h5, h6 , blockquote {
grid-column: main/end;
}
pre, table, .highlight {
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment