[{"data":1,"prerenderedAt":584},["ShallowReactive",2],{"\u002Fblogs\u002Freview-of-popular-static-site-generators":3},{"title":4,"description":5,"coverImage":6,"timestamps":9,"body":11},"A Review of Some of the Most Popular Static Site Generators","Discover Static Site Generators (SSGs) like Jekyll for simplicity, Gatsby for JS speed, Pelican for Python ease, and Hugo for speed and versatility. Tailor your choice to coding preference and needs. Read the comprehensive review for insights.",{"url":7,"alt":8},"https:\u002F\u002Fik.imagekit.io\u002Fjarmos\u002Freview-of-static-site-generators.png?updatedAt=1702974989355","A review of the most popular Static Site Generators",{"publishedOn":10},"2021-02-04T00:00:00+00:00",{"type":12,"value":13,"toc":574},"minimark",[14,18,41,50,53,71,103,112,115,118,123,130,137,140,186,189,192,196,210,226,234,237,258,267,274,278,281,284,291,294,311,314,321,331,334,343,346,349,356,359,363,366,373,390,401,404,407,420,423,432,435,438,447,450,453,457,468,471,486,489,492,503,512,515,528,531,534,541,544,559],[15,16,17],"p",{},"So confusing! Which Static Site Generator should I use?",[15,19,20,21,28,29,34,35,40],{},"When I started blogging, I was looking for a platform to host my content on. I\nshared my dilemma in a previous article. Check it out at:\n",[22,23,27],"a",{"href":24,"rel":25},"https:\u002F\u002Fjarmos.netlify.app\u002Fposts\u002Freviewing-popular-static-site-generators\u002Fstatic-site-vs-medium.md",[26],"nofollow","Medium Vs Static Site Generators-A Computer Vision Engineer’s Dilemma",".\nSuffice to say, a year later I use both, ",[22,30,33],{"href":31,"rel":32},"https:\u002F\u002Fjarmos.medium.com\u002F",[26],"Medium"," &\na SSG to create ",[22,36,39],{"href":37,"rel":38},"https:\u002F\u002Fjarmos.netlify.app\u002F",[26],"my blog",".",[15,42,43,44,49],{},"But choosing the right\n",[22,45,48],{"href":46,"rel":47},"https:\u002F\u002Fwww.cloudflare.com\u002Flearning\u002Fperformance\u002Fstatic-site-generator\u002F",[26],"Static Site Generators","\n(SSGs) was never an easy task. I looked around. Tried a couple of available\noptions. And I figured something out. Each site generator was unique in some way\nor the other & will have some advantage over the other.",[15,51,52],{},"Keeping that in mind, I had to jot down my specific requirements. And the\nfollowing were my blogging needs:",[54,55,56,65,68],"ol",{},[57,58,59,60,40],"li",{},"Write content in ",[22,61,64],{"href":62,"rel":63},"https:\u002F\u002Fwww.markdownguide.org\u002F",[26],"Markdown",[57,66,67],{},"Focus on delivering quality content over aesthetics. Avoid spending time on\nhacking & setting up a dev environment.",[57,69,70],{},"Automate certain aspects of my workload as much as possible.",[15,72,73,74,79,80,85,86,91,92,96,97,102],{},"My lack of experience didn’t help either & my initial attempt to do so with\n",[22,75,78],{"href":76,"rel":77},"https:\u002F\u002Fjekyllrb.com\u002F",[26],"Jekyll"," failed. So, I jumped ship to\n",[22,81,84],{"href":82,"rel":83},"https:\u002F\u002Fwww.gatsbyjs.com\u002F",[26],"Gatsby"," & ",[22,87,90],{"href":88,"rel":89},"https:\u002F\u002Fpages.github.com\u002F",[26],"GitHub Pages","\nwhich didn’t work out either! ",[93,94,95],"em",{},"sighs",". So, I made another quick switch to\n",[22,98,101],{"href":99,"rel":100},"https:\u002F\u002Fblog.getpelican.com\u002F",[26],"Pelican"," & used it to work with some of my first\nfew articles.",[15,104,105,106,111],{},"Alas, I couldn’t stay faithful to Pelican either for long. I justified my\nreasoning to switch often from one tool to the other further in the article.\nBut, ",[22,107,110],{"href":108,"rel":109},"https:\u002F\u002Fgohugo.io\u002F",[26],"Hugo"," hasn’t disappointed me til now, so let’s see how\nlong can I stick with it.",[15,113,114],{},"Besides, if you read till here, you might wonder to yourself, how fickle-minded\nI’m. Perhaps I’m fickle-minded. But if there’s anything I learned from the\nexperience. It would be my unbiased opinion on how the various SSGs achieve the\nsame goal albeit in their own way. Hence, I wanted to share my learnings & leave\na detailed review of the software with my audience.",[15,116,117],{},"So, without further ado, let’s review some of the most popular Static Site\nGenerators, or at least the ones I used.",[119,120,122],"h3",{"id":121},"common-aspects-all-ssgs-shouldve-bydefault","Common Aspects All SSGs Should’ve (By Default)",[15,124,125,126,129],{},"Comparing one SSG with another is no easy task. They all serve one single\npurpose i.e to generate static contents. The static content ( ",[93,127,128],{},"think HTML, CSS &\nJS files",") are then served through a CDN over the Internet. Hence, there’s no\none site generator better than the other(s).",[15,131,132,133,136],{},"But, for the sake of brevity & a precise review, we need to review each site\ngenerators on common grounds. So, reviewing the site generators will be easier (\n",[93,134,135],{},"and relevant to individual needs",").",[15,138,139],{},"That said, following are the common aspects to review each site generators:",[141,142,143,150,156,162,180],"ul",{},[57,144,145,149],{},[146,147,148],"strong",{},"Easy installation process"," — Installing a site generator shouldn’t be\nrocket-science. It should be easy enough for even a non-technical person to\nset up with the least amount of roadblocks.",[57,151,152,155],{},[146,153,154],{},"Legible documentations"," — Can’t emphasis on this point enough! A seasoned\ndeveloper might hack around with insufficient instructions & still resolve\ntheir issues. The same can’t be said about a non-technical person. So, the\neasier the docs are to follow, the better the SSG is.",[57,157,158,161],{},[146,159,160],{},"Ease of use"," — While documentations ease using the tool, it’s not always\nthe case with certain tools. An example would be Pelican & its use of Jinja\ntemplates. Or Jekyll & Liquid templates for customizing the site’s aesthetics.\nThese extra tools can often increase the learning curve of using a tool.\nHence, in a hypothetical world an SSG with no extra tools is the perfect tool\nfor the job. So, if your preferences are to produce content, choose the tool\nwith little to no extra fluff.",[57,163,164,167,168,173,174,179],{},[146,165,166],{},"Availability of themes"," — I don’t see why a site generator shouldn’t\nprovide a wide range of themes to choose from. Especially when there’re\nalternatives like ",[22,169,172],{"href":170,"rel":171},"https:\u002F\u002Fwordpress.com\u002F",[26],"Wordpress"," &\n",[22,175,178],{"href":176,"rel":177},"https:\u002F\u002Fwww.wix.com\u002F",[26],"Wix",". Availability of themes is a must, doesn’t matter\nif they’re paid or free.",[57,181,182,185],{},[146,183,184],{},"Ease of customizing themes"," — What’s the point of having a ready list of\nthemes if you can’t customize them to your needs. Considering the importance\nof branding & personalization, not providing this option is a no-brainer.\nWe’ll see how easy it is to customize the themes of your choice. And extra\nkudos if the themes are open-sourced! ❤️",[15,187,188],{},"So, those were some common grounds all the site generators in question will be\nreviewed upon.",[15,190,191],{},"That said, lets dive into it & review the site generators.",[119,193,195],{"id":194},"jekyll-the-static-site-generator-that-powers-githubpages","Jekyll: The Static Site Generator That Powers GitHub Pages",[15,197,198,199,204,205,40],{},"Jekyll is\n",[22,200,203],{"href":201,"rel":202},"https:\u002F\u002Fdocs.github.com\u002Fen\u002Fgithub\u002Fworking-with-github-pages\u002Fsetting-up-a-github-pages-site-with-jekyll",[26],"advertised","\nas a one-stop solution for all your blogging needs. It’s expected to work\nout-of-the-box without much configuration & complicated setup. And by far it’s\none of the easiest to use among all the other SSGs mentioned in this article.\nCoupled with being too easy to install, the software is well documented. And the\nofficial documentation is available at:\n",[22,206,209],{"href":207,"rel":208},"https:\u002F\u002Fjekyllrb.com\u002Fdocs\u002F",[26],"jekyllrb.com\u002Fdocs\u002F",[15,211,212,213,216,217,221,222,225],{},"About its ease of use, things get interesting here. Well, you see, installing\nJekyll on your local machine isn’t needed in the first place. You could write a\nsingle-page site ( ",[93,214,215],{},"by hand","!). Save it as ",[218,219,220],"code",{},"index.html",", push it to a remote\nrepository named ",[218,223,224],{},"https:\u002F\u002F\u003CYOUR-USERNAME>.github.io",". And GitHub will serve your\nsite powered by a Jekyll theme of your choice.",[15,227,228,229,233],{},"Working with Jekyll is as easy as that. Check out the official\n",[22,230,232],{"href":88,"rel":231},[26],"GitHub Page"," landing page for more clarification.",[15,235,236],{},"But think to yourself, do you want to write the markup files, by hand? If that’s\nyou, heck you won’t even need a SSG in the first place then! But ask me, you’re\nbetter off using a SSG to generate the static files. You’ll find less errors in\nthe markup & besides, using a SSG enables good SEO practices by default.",[15,238,239,240,245,246,249,254,255,257],{},"That said, I observed Jekyll has the largest collection of themes. While some\nare free & maintained by the community, there’re premium ones as well. So, if\nyou’re looking to create a blog or a landing page for your business, there’s\nbound to be a theme for you out there. A great place to find some themes is the\nofficial ",[22,241,244],{"href":242,"rel":243},"https:\u002F\u002Fjekyllrb.com\u002Fdocs\u002Fthemes\u002F",[26],"Jekyll themes"," page ( ",[93,247,248],{},"they’re all",[146,250,251],{},[93,252,253],{},"free"," 😉). Perform a customary Google search for “ ",[93,256,244],{}," “ and\nyou’ll find more of them.",[15,259,260,261,266],{},"Customizing Jekyll themes isn’t as straightforward as using Jekyll is though.\nYou’ll need to learn using a templating language called\n",[22,262,265],{"href":263,"rel":264},"https:\u002F\u002Fshopify.github.io\u002Fliquid\u002F",[26],"Liquid",". On top of which, Jekyll even\nprovides more utilitarian tools to help you customize your site. So, if you’re\nunfamiliar with templates, you’ll have to make use of the available themes only.",[15,268,269,270,273],{},"But on a brighter note, there’s good news for JavaScript & frontend developers.\nYou might find better luck with the next SSG ( ",[93,271,272],{},"or rather a framework","), called\nGatsby.",[119,275,277],{"id":276},"gatsby-a-reactjs-framework-to-build-staticsites","Gatsby: A React.js Framework to Build Static Sites",[15,279,280],{},"Gatsby advertises themselves as that one SSG to create blazing fast modern\nwebsites. And they do live up to their promise with websites with seemingly\nnon-existent load times! But unlike most other SSGs mentioned in the article,\nGatsby is more of a framework. It’s based around React components, hence why\nit’s considered a framework rather than a SSG.",[15,282,283],{},"While it works out well for JavaScript developers other developers might feel\nleft out. You see, to make the most out of Gastby, you would’ve to be pretty\ngood at JS first. Experience with React components is also a plus point. But,\nnot every developer knows JavaScript. And besides, learning a new language isn’t\nsomething you can do overnight.",[15,285,286,287,290],{},"But on a brighter note, Gatsby is pretty easy to install. You can install it\nglobally with the ",[218,288,289],{},"npm install -g gatsby-cli"," & you're good to go. Nothing could\nget easier than installing Gatsby. No need to mess around with environment\nvariables.",[15,292,293],{},"Once installed, the CLI can download the themes as well as generate the static\ncontent. The whole process is one single step. There’s no manual steps involved\nwith setting up themes.",[15,295,296,297,302,303,306,307,310],{},"Gatsby ",[22,298,301],{"href":299,"rel":300},"https:\u002F\u002Fwww.gatsbyjs.com\u002Fdocs\u002F",[26],"documentations"," also appears revamped.\nAnd I’ve to confess their new site design looks pretty nifty & easy to use. With\nsections for “ ",[93,304,305],{},"Tutorials","”, “ ",[93,308,309],{},"How-to Guides"," “, etc, the docs couldn’t be more\neasier to navigate.",[15,312,313],{},"So, kudos to them for making their docs as accessible & appealing as possible.",[15,315,316,317,320],{},"But here’s the interesting part about reviewing Gatsby. It was built keeping in\nmind JS developers & their tool kit. So, if you’re a JS developer ( ",[93,318,319],{},"more so if\nyou’re a frontend developer","), look no further. You won’t find anything better\nthan Gatsby.",[15,322,323,330],{},[146,324,325,326,329],{},"It has an integrated GraphQL API (",[93,327,328],{},"and an web-based GraphQL IDE",")",". While\nit’s optional & if you find using GraphQL difficult, there’re options to opt out\nof it.",[15,332,333],{},"The GraphQL API powers Gatsby to source data from anywhere. Need your Markdown\nfiles sourced from a web-based CMS then Gastby got you covered? Or is sourcing\nyour content from the file-system your preference? Then Gatsby got you covered\nthere as well!",[15,335,336,337,342],{},"So, if you’re inexperienced working with backend systems, look no further. Heck,\nthere’re even ",[22,338,341],{"href":339,"rel":340},"https:\u002F\u002Fyoutu.be\u002FLk9Cj8a6QJg",[26],"tutorials"," to hook up a Firebase\ndatabase to your Gatsby Blog & you’re good to go. No longer do you’ve to set up\nbackend servers & what not. All you’ve to do is stick to what you’re already\ngood at, if you’re a frontend developer.",[15,344,345],{},"But things don’t end here either! The Gatsby ecosystem brings in more goodies\nfor the user. It’s plugin system & wide-range of available themes is\nincomparable. With the wide range of available themes & an extensive plugin\nsystem, what you could do with your blog is limitless.",[15,347,348],{},"And then there are people who say, “frontend developers aren’t real programmers”\n🤨. If you ask me, the Gatsby devs did a great job. Enabling backend\ncapabilities to a frontend software is pretty praiseworthy.",[15,350,351,352,355],{},"But, while everything appears good & dandy with Gatsby, there’s a caveat. As\nmentioned earlier it was built with a frontend developer’s point-of-view. So,\nunless you’re pretty good JavaScript ( ",[93,353,354],{},"and\u002For React","), you’re out of luck. And\nthat’s a major hit back to an otherwise awesome piece of software.",[15,357,358],{},"Suffice to say, being a Python developer, using Gatsby was too difficult to use.\nIf I had to customize the theme even just a bit, I had to be adept at\nJavaScript. And not to forget an in-depth understanding of React Components as\nwell. 😔",[119,360,362],{"id":361},"pelican-a-static-site-generator-built-withpython","Pelican: A Static Site Generator Built With Python",[15,364,365],{},"So, if frontend skills aren’t my forte, what’re the other available options?",[15,367,368,369,372],{},"This is where ",[22,370,101],{"href":99,"rel":371},[26],", a static site generator\nbuilt with Python shines. So, you’ll need to have Python installed on you\nmachine as well.",[15,374,375,376,381,382,385,386,389],{},"Besides, if you’re a backend developer chances are,\n",[22,377,380],{"href":378,"rel":379},"https:\u002F\u002Fwww.python.org\u002F",[26],"Python"," is already installed on your system. So,\ninstalling Pelican is only a ",[218,383,384],{},"pip"," command away. It's as easy as running the\n",[218,387,388],{},"pip install pelican"," command & you'll have Pelican working.",[15,391,392,393,396,397,400],{},"Out-of-the-box Pelican supports files written in ",[218,394,395],{},".rst"," format. But you can even\nwrite your articles in Markdown. You'll only need to install the dependencies\nwith the ",[218,398,399],{},"pip install \"pelican[markdown]\""," command. That should install the\nextra stuff for converting Markdown files to HTML.",[15,402,403],{},"But on the flip side, the software is over a decade old at the time of writing\nthis article. Hence, unlike the other site generators, Pelican appears bland.\nAnd I assume parts of it’s API might even be very difficult to peruse through\nfor the current developers.",[15,405,406],{},"Also Pelican’s age does show everywhere. It’s landing page looks like it was\nbuilt back in the early 90s. The themes & configuration system are primitive\ntoo. For some, it could be a major deal-breaker & unappealing. And they’re right\nto feel so.",[15,408,409,410,415,416,419],{},"Pelican sites are configured with\n",[22,411,414],{"href":412,"rel":413},"https:\u002F\u002Fdocs.python.org\u002F3\u002Ffaq\u002Fprogramming.html#how-do-i-share-global-variables-across-modules",[26],"global variables","\nin a ",[218,417,418],{},"pelicanconf.py"," file. Some of the variables are preset by Pelican while\ntheme authors can add their own variables as well. In other words, Pelican can\nmake use of an arbitrary range of settings! It might sound good right away but,\nfor Pelican, it didn't work out so well as you'll see soon.",[15,421,422],{},"Like most well-maintained Python projects, Pelican is also maintained by an\nactive team of developers. They’ve documented the software well enough but it\ncould be made better. It’s a problem other Python projects face as well. This is\nso because the authors rely on automatic generation of their docs off of the\ndocstrings from the source code. Hence, you might often notice a lack of\n“human-touch” with certain Python project documentations.",[15,424,425,426,431],{},"Regardless, most documentation issues can be handled. But I fear the same can’t\nbe said for the Pelican community. While there’s a ton of available themes for\nPelican, but guess what? Most of the themes aren’t maintained (\n",[22,427,430],{"href":428,"rel":429},"https:\u002F\u002Fgithub.com\u002Fgetpelican\u002Fpelican-themes\u002Fissues\u002F677",[26],"source",")!",[15,433,434],{},"So if you’re using Pelican with a theme, good luck if you come across an issue\nwith it. Remember how Pelican theme authors could add their own arbitrary\nsettings on top of the preset ones? Well this is where it came back to bite the\nPelican ecosystem.",[15,436,437],{},"Imagine you find a theme that you like. Install it for your blog, only for it to\nbreak with the latest Pelican installation. And there’s no way for you to fix it\nbecause the theme author hadn’t made a commit to the repo for 5 years now.\nSaddening, isn’t it?",[15,439,440,441,446],{},"On top of it, as mentioned earlier, most of the themes look aged & bland. You\ncould customize them or create one from scratch. But that requires knowledge of\nworking with ",[22,442,445],{"href":443,"rel":444},"https:\u002F\u002Fjinja.palletsprojects.com\u002Fen\u002F2.11.x\u002F",[26],"Jinja 2"," templates.\nAnd Jinja templates do have a slight learning curve to it as well. So, good luck\nworking with it when your time could be better spent blogging instead.",[15,448,449],{},"So, at the end of day when\u002Fwhy should you use Pelican? You’re a Python backend\ndeveloper with experience working on Jinja templates. And besides, if SEO &\nother aesthetic values of your site doesn’t matter to you, then Pelican is the\nright option for you.",[15,451,452],{},"But, what if you care about efficiency & proper time management? Then there’s\nHugo for you. The next section details a review about Hugo as an SSG.",[119,454,456],{"id":455},"hugo-the-fastest-static-site-generator-evercreated","Hugo: The Fastest Static Site Generator Ever Created",[15,458,459,464,465,40],{},[22,460,463],{"href":461,"rel":462},"https:\u002F\u002Fwww.jamstack.com\u002Fgenerators\u002F",[26],"Jamstack"," ranks Hugo, the second-most\npopular site generator. Its followed by Gatsby only by a fraction of ",[93,466,467],{},"GitHub\nStars",[15,469,470],{},"Besides, it’s also one of the few non-JS software in a domain filled by\nJavaScript framework(s). Its rise to popularity arose mainly due to it’s speed\nof generating static content. Plus its availability of pretty, modern &\nSEO-friendly themes is an underrated aspect as well.",[15,472,473,474,479,480,485],{},"Hugo was built with ",[22,475,478],{"href":476,"rel":477},"https:\u002F\u002Fgolang.org\u002F",[26],"Go",", so you only need to invoke a\nbinary file to start using Hugo. No installation required. You can find a\nverbose installation instruction at the “\n",[22,481,484],{"href":482,"rel":483},"https:\u002F\u002Fgohugo.io\u002Fgetting-started\u002Finstalling",[26],"Getting Started"," “ section of the\nofficial docs.",[15,487,488],{},"Also something to note here, the Hugo docs are the most detailed documentations\nI’ve ever seen anywhere else till now. And the devs are verbose with the rest of\nthe docs as well. So, extra kudos to them!",[15,490,491],{},"And if it’s not obvious by now, I can’t appreciate the Hugo dev’s effort in\nmaking their docs as inclusive as possible! The attention to verbosity they’ve\ngiven is praiseworthy. They left no corners untouched while articulating the\ndocs. So my fellow Python devs, take some lessons from the Hugo devs on how-to\nwrite good documentations. 😜",[15,493,494,495,498,499,502],{},"Besides, being able to invoke a single binary file, installing Hugo themes is\nalso a piece of cake. All you got to do clone your preferred theme(s) into\nthe ",[218,496,497],{},".\u002Ftheme\u002F"," directory. Ensure your Hugo knows which theme to use by updating\nthe ",[218,500,501],{},"config.yml"," file & you're set with a theme.",[15,504,505,506,511],{},"Also, trust me on it but, you’re going to spend a day or two perusing through\nthe available ",[22,507,510],{"href":508,"rel":509},"https:\u002F\u002Fthemes.gohugo.io\u002F",[26],"list of themes","! Not only are each of\nthem pretty & modern, most of them are well maintained & are SEO-friendly.",[15,513,514],{},"On that note, if you’re wondering how easy it is to customize the themes, I\nwould say, they’re not difficult. And besides, the official Hugo docs got your\nback in case you get stuck somewhere. 😉",[15,516,517,518,521,522,527],{},"All you’ve to know before going down the custom-shop lane ( ",[93,519,520],{},"or even building\nyour own theme",") is ",[22,523,526],{"href":524,"rel":525},"https:\u002F\u002Fgolang.org\u002Fpkg\u002Ftext\u002Ftemplate\u002F",[26],"Go Templates",". Hugo\nuses Go’s powerful templating language. Unlike Liquid and\u002For Jinja2, Go\ntemplates are very intuitive. And best of all, you don’t have to abandon your\nexisting frontend skills either. Coupled with Go templates you can build\nwebsites that won’t look like static sites at all.",[15,529,530],{},"So, if you ask me? I would say Hugo would be your best bet regardless of any\nspecific needs and\u002For you skill level. And that’s coming from a Python developer\nwith no experience working with Golang and\u002For JavaScript! With Hugo, I can focus\non producing more content rather than develop frontend stuff.",[15,532,533],{},"Well was it not hard for me to review each of those tools & decide which would\nsuit which kind of users. So, here are my final thoughts on choosing the right\ntool for individual needs. And to make it even easier for you to summarise a\nrather lengthy piece of article, I’ve made an infographic for it. So, the next\ntime you’re confused which site generator to use, the infographic will come\nhandy.",[15,535,536],{},[537,538],"img",{"alt":539,"src":540},"An infographic to help readers choose the right static site generator for their blogging needs.","https:\u002F\u002Fcdn.hashnode.com\u002Fres\u002Fhashnode\u002Fimage\u002Fupload\u002Fv1651823923459\u002FeBbXvICkX.jpeg",[15,542,543],{},"Infographic: Choosing the Right Static Site Generator | Source: Author",[15,545,546,547,552,553,558],{},"With everything said and done, do let me know if you enjoy reading these\ncontents. Find me on Twitter: ",[22,548,551],{"href":549,"rel":550},"https:\u002F\u002Ftwitter.com\u002FJarmosan",[26],"@Jarmosan"," and\u002For\n",[22,554,557],{"href":555,"rel":556},"https:\u002F\u002Fjarmos.ck.page\u002Fnewsletter",[26],"subscribe to my newsletter"," to get\npersonalized content delivered to your inbox.",[15,560,561,564,571],{},[93,562,563],{},"Originally published at",[22,565,568],{"href":566,"rel":567},"https:\u002F\u002Fjarmos.netlify.app\u002Fposts\u002Freviewing-popular-static-site-generators\u002F",[26],[93,569,570],{},"https:\u002F\u002Fjarmos.netlify.app",[93,572,573],{},"on February 4, 2021.",{"title":575,"searchDepth":576,"depth":576,"links":577},"",2,[578,580,581,582,583],{"id":121,"depth":579,"text":122},3,{"id":194,"depth":579,"text":195},{"id":276,"depth":579,"text":277},{"id":361,"depth":579,"text":362},{"id":455,"depth":579,"text":456},1789041548211]