Click here to Skip to main content
15,917,565 members
Articles / Web Development

GoogPress - Creating Websites with Google Docs

Rate me:
Please Sign up or sign in to vote.
5.00/5 (7 votes)
9 Sep 2023GPL34 min read 17.4K   5   5
GoogPress is a fun little web thing that turns Google Docs into websites. Here’s how a two-man team built it in a week.
This article describes the development of "GoogPress," a platform created using Google Apps Script that enables conversion of Google Docs into web pages, allowing for the publication of articles and papers online.


In my spare time, I work on the production team of the Young Scientists’ Journal. We oversee the journal’s distribution in both digital and print forms. When we took over from the previous team, we were tasked with moving the site away from the (now deprecated) WordPress Annotum and onto something more current, user-friendly and less prone to XML errors. Following much deliberation, we decided to move things onto Google Docs. This was super intuitive with unlimited (document) storage and people approved of it very much (Google Docs is basically MS Word) but did present one problem – how were we going to get all our articles and papers from documents into webpages?

We thus decided to build GoogPress – like WordPress, but using Google as a backend.

You can find our website (built with GoogPress, with more thorough documentation) here and all our code on GitHub.

General Workings

We used Google Apps Script as a means of grabbing all the docs. This meant that they didn’t have to be shared publicly and could all be stored in a Posts folder.

Image 1

The script is stored somewhere on the user’s Google Drive (doesn’t particularly matter where) and is called using POST requests from the client. The developer then sticks GoogPress.js into their website and calls it with the gp_Init function.

//Initialise GoogPress
gp_Init ("https://your-script-url-here");

//Load the 3 most recent posts
gp_loadPosts($("#post-container"),"postClass", "<​hr/>", 1, 3);

Once that’s done, the HTML that comes out looks a bit like this:

<div id="post-container">
    <div class="postClass">
        I am the latest post
    <div class="postClass">
        I am not the latest post
    <div class="postClass">
        I am also not the latest post

You can also load individual posts using:

//Load the post 'Hi World' into the post div.
gp_loadPost ("Hi World", $("#post"));

which returns something like this:

<div id="post">
  Content of 'Hi World'

or simply by using Google the data-googpress attribute:

<div data-googpress="postName"><​/div>

which loads the posts into the <div> on initialisation.

A Closer Look at the Server Side

The back-end is all Google Apps Script. It's basically JavaScript with some exiting Google-related integrations.

To start with, we check the parameters passed in the POST request. If they’re invalid, we return an error. Otherwise, we look for the post. We do this in the doPost method (which runs whenever we receive a POST request).

//This is how we'll interface with the outside world

function doPost(e) {

  var requestType = e.parameters.type;
  var id =;
  var asHtml = e.parameters.asHtml;
  var start = e.parameters.start;
  var end = e.parameters.end;

  if (requestType == undefined){
   return ContentService.createTextOutput("Failed to specify request type");



We search for the doc using the openDoc function.

//Find docName in containerFolder. 
function openDoc(docName, containerFolder) { 

  var file, files = (containerFolder == undefined) ? 
                     DriveApp.getFilesByName(docName) : 

  if (files.hasNext ()){
    file =;
  } else {
    return "Not Found";

  return DocumentApp.openById(file.getId());


We then convert the doc into HTML using a modified version of this snippet by Omar Al Zabir (he explains how it works on his blog). This essentially allows us to turn stuff like this:

Image 2

into stuff like this:

Image 3

As you can see, Google Apps Script allows easy interaction with Google Products with their DocumentApp and DriveApp classes.

Building an Installer

The basic request-making interface was pretty easy to build and was implemented over a few afternoons after school. What was surprisingly difficult, however, was building an installer. We first considered deploying on the Chrome Web Store but that seemed like too much effort (and not particularly prototype-friendly). We tried to write a script that would create a script file in the user’s drive and then copy over the code but that didn’t work either (and indeed for good reason).

In the end, after a day's pondering and a few beers, we settled on the devilishly convoluted system described below.

  1. The user runs a script which they must authorise. In this way, we are given permission to access the user’s drive.
  2. The script then sends a request to a script running on our end.
  3. The script on our end creates a copy of the GoogPress script and shares it with the user.
  4. The script on the user’s end adds the shared script to its own drive and then makes a copy of it. This ensures that the user is the owner of the file (and not us).
  5. There’s then some copying and pasting and arranging of files which means the installation is tidy and kept in a dedicated GoogPress folder. We also create a “Hello World” post.
  6. Once this is all done, we delete the shared file off of our drive.

(The scripts of interest are which runs on our side and which runs on the user's)

What are we Working on Now? (Current Challenges)

A cache system. If you send too many requests per second, Google thinks you’re trying to DDOS them (or something along those lines). While this won’t be a problem for smaller sites, it’s a problem and we’re going to try and fix it.

Dealing with images. Images load pretty slowly on GoogPress because the Google Doc to HTML converter converts them to Base64 before sending them over. There’s probably a faster way of doing it and, with some time, we’ll find it.


This below demo code loads a sample post onto a very basic HTML page. Copy the below markup into your favourite text editor.

        <title> GoogPress Demo </title> 
        <h1> This is GoogPress </h1>

        <div data-googpress="TestPost2"></div>

        <!-- Scripts -->
        <script type="text/javascript" 
         src=""> </script>

            //Replace the URL with whatever.
            gp_Init ("");


Open it up in your browser and it should look like this:

Image 4

And yes, they're notes from RS GCSE.


This article, along with any associated source code and files, is licensed under The GNU General Public License (GPLv3)

Written By
United Kingdom United Kingdom
Hipster classicist/computer scientist.

London, 16

Comments and Discussions

GeneralMy vote of 5 Pin
aarrgghhh11-Sep-23 11:35
aarrgghhh11-Sep-23 11:35 
GeneralNeat little project Pin
mbielski11-Sep-23 7:27
mbielski11-Sep-23 7:27 
Generalgood work Pin
Member 132705767-Feb-18 0:09
Member 132705767-Feb-18 0:09 
QuestionNice work Pin
Jan Wolniak13-Feb-17 10:17
Jan Wolniak13-Feb-17 10:17 
AnswerRe: Nice work Pin
chlohee4-Jun-17 2:02
chlohee4-Jun-17 2:02 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.