[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-J4VId85O6KcEtZFzDEWsO007Jrw1SspoPZ9nPdUdbeU":3,"sanity-_iVgn3L8evFmiJ79UVArkT4jRVSfURHI2Z0XsknVXmg":310},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":285},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"4d0175f4-40a8-47eb-9bb3-a453b326aa7d","2026-07-03T07:40:00.000Z",{"_type":10,"current":11},"slug","the-good-the-bad-and-the-ai-apps",null,"The good, the bad, and the AI apps",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":61,"comments":259,"dateUrl":260,"excerpt":129,"image":261,"legacyBody":264,"product":12,"publishedAt":267,"slug":268,"sponsored":12,"tags":270,"title":284,"visible":259},"2023-05-25T09:37:04Z","wp-post-5114","dgl3SCUzppW3U2LvCoSK4S","blogPost","2023-07-13T14:55:01Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":57,"name":58,"slug":59},"2023-05-23T16:27:18Z","wp-author-121","uJtKC0FWGm7HBTFm4JLcEY","blogAuthor","2024-02-26T15:31:52Z",{"_type":53,"asset":54},"image",{"_ref":55,"_type":56},"image-23fa43faa7ab82a079c2ceec9c7028b6bb07a6d9-1024x1024-jpg","reference","former","Jon Chan",{"current":60},"jonhmchan",[62,85,94,113,125,130,141,145,153,161,169,173,177,181,189,193,223,231,239],{"_key":63,"_type":64,"children":65,"markDefs":80,"style":84},"d2ecf286180f","block",[66,71,76],{"_key":67,"_type":68,"marks":69,"text":70},"d2ecf286180f0","span",[],"Today, we're proud to announce the new Stack Exchange blog, all shiny and new! It's been ",{"_key":72,"_type":68,"marks":73,"text":75},"d2ecf286180f1",[74],"0b8ff33d686f","six to eight weeks",{"_key":77,"_type":68,"marks":78,"text":79},"d2ecf286180f2",[]," in the making and we're really happy our community can finally see it. Here's an overview of the major changes that we've made to the site:",[81],{"_key":74,"_type":82,"href":83,"reference":12},"link","http:\u002F\u002Fmeta.stackexchange.com\u002Fa\u002F19514\u002F242868","normal",{"_key":86,"_type":64,"children":87,"markDefs":92,"style":93},"b55f7f7ed5dc",[88],{"_key":89,"_type":68,"marks":90,"text":91},"b55f7f7ed5dc0",[],"Channels",[],"h2",{"_key":95,"_type":64,"children":96,"markDefs":110,"style":84},"6e7a19ad539d",[97,101,106],{"_key":98,"_type":68,"marks":99,"text":100},"6e7a19ad539d0",[],"The biggest change we've made is the introduction of channels on the blog. In the previous blog, we pretty much put everything in one column, organized by tags. We still have all the posts in chronological order on ",{"_key":102,"_type":68,"marks":103,"text":105},"6e7a19ad539d1",[104],"e8f8ab34917d","the homepage",{"_key":107,"_type":68,"marks":108,"text":109},"6e7a19ad539d2",[]," of the new blog, but we realized there are two big buckets of content that we want to post here: company news and engineering posts. We want to recast our blog not just as a place to post updates as they come, but to become an amazing source of news, technical knowledge, and insight into the communities we've built.",[111],{"_key":104,"_type":82,"href":112,"reference":12},"http:\u002F\u002Fblog.stackexchange.com\u002F",{"_key":114,"_type":64,"children":115,"markDefs":121,"style":124},"1a1d95bb90aa",[116],{"_key":117,"_type":68,"marks":118,"text":120},"1a1d95bb90aa0",[119],"dae307cef4d9","Company News Channel",[122],{"_key":119,"_type":82,"href":123,"reference":12},"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany","h3",{"_key":126,"_type":53,"alt":12,"asset":127,"caption":129,"markDefs":12},"e44586ae7297",{"_ref":128,"_type":56},"image-15b9ef748e9649ab44ffebefd1e8e51ff7d75288-800x534-jpg","",{"_key":131,"_type":64,"children":132,"markDefs":138,"style":124},"2e6f7f90a7f3",[133],{"_key":134,"_type":68,"marks":135,"text":137},"2e6f7f90a7f30",[136],"a8fbf484548e","Engineering Channel",[139],{"_key":136,"_type":82,"href":140,"reference":12},"http:\u002F\u002Fblog.stackexchange.com\u002Fengineering",{"_key":142,"_type":53,"alt":12,"asset":143,"caption":129,"markDefs":12},"24bd466ce18a",{"_ref":144,"_type":56},"image-e91d37c7ab87b470c92d63bed568192f42c2d86f-800x533-jpg",{"_key":146,"_type":64,"children":147,"markDefs":152,"style":84},"00c90835e16a",[148],{"_key":149,"_type":68,"marks":150,"text":151},"00c90835e16a0",[],"There's a subsection for each major part of our engineering team: developers, SREs, designers, and anyone else that touches our product creation process. As we grow, you can expect to see more content fill up here, and possibly bring in outside contributors as well.",[],{"_key":154,"_type":64,"children":155,"markDefs":160,"style":93},"a16832b9477a",[156],{"_key":157,"_type":68,"marks":158,"text":159},"a16832b9477a0",[],"An all new design",[],{"_key":162,"_type":64,"children":163,"markDefs":168,"style":84},"dc62e4df3843",[164],{"_key":165,"_type":68,"marks":166,"text":167},"dc62e4df38430",[],"The most notable thing that we changed is the overall design. We wanted to make something that people enjoy reading, exploring, and learning from. Most of all the things from the previous blog still exist: previous posts with archived comments, tagged posts sortable by category, and so on. We've also added some additional functionality here: new navigation that emphasizes our new channels and content, posts sortable by author, and better feeds with individual post pages for readability. Take a look around, there's a lot of changes we've made here.",[],{"_key":170,"_type":53,"alt":12,"asset":171,"caption":129,"markDefs":12},"ffe82c4f6554",{"_ref":172,"_type":56},"image-9517da44ae587020055f36760b6fd2ebb7c6cc0f-800x104-png",{"_key":174,"_type":53,"alt":12,"asset":175,"caption":129,"markDefs":12},"d4ef63b98aec",{"_ref":176,"_type":56},"image-5e08fb2251f1e13d01451002dcf5282a75000b4d-800x540-png",{"_key":178,"_type":53,"alt":12,"asset":179,"caption":129,"markDefs":12},"4e074772f666",{"_ref":180,"_type":56},"image-dc39628b641faa568ddc730fb496d7274d961c9a-800x473-png",{"_key":182,"_type":64,"children":183,"markDefs":188,"style":93},"19169b4ad84b",[184],{"_key":185,"_type":68,"marks":186,"text":187},"19169b4ad84b0",[],"Open source",[],{"_key":190,"_type":53,"alt":12,"asset":191,"caption":129,"markDefs":12},"722b0ba79c21",{"_ref":192,"_type":56},"image-a7cc91b46f9147829fbc4ac6aece843a50ef390a-800x606-png",{"_key":194,"_type":64,"children":195,"markDefs":218,"style":84},"d0840ac0d94d",[196,200,205,209,214],{"_key":197,"_type":68,"marks":198,"text":199},"d0840ac0d94d0",[],"If you have suggestions for how to make the new blog better, ",{"_key":201,"_type":68,"marks":202,"text":204},"d0840ac0d94d1",[203],"23ff64b7ba9d","create an issue",{"_key":206,"_type":68,"marks":207,"text":208},"d0840ac0d94d2",[]," and one of our developers will take a look at it (probably me). If you're a developer, we encourage you to take a look at the source code and make ",{"_key":210,"_type":68,"marks":211,"text":213},"d0840ac0d94d3",[212],"e4885cd6d0e3","pull requests",{"_key":215,"_type":68,"marks":216,"text":217},"d0840ac0d94d4",[]," for changes as well. If you want a walkthrough of how we built the blog, take a look at the engineering channel for an inside look.",[219,221],{"_key":203,"_type":82,"href":220,"reference":12},"https:\u002F\u002Fgithub.com\u002FStackExchange\u002Fblog\u002Fissues",{"_key":212,"_type":82,"href":222,"reference":12},"https:\u002F\u002Fgithub.com\u002FStackExchange\u002Fblog\u002Fpulls",{"_key":224,"_type":64,"children":225,"markDefs":230,"style":93},"19306d004b43",[226],{"_key":227,"_type":68,"marks":228,"text":229},"19306d004b430",[],"More to come",[],{"_key":232,"_type":64,"children":233,"markDefs":238,"style":84},"db06758b3ef6",[234],{"_key":235,"_type":68,"marks":236,"text":237},"db06758b3ef60",[],"There's so much more we want to do with this blog in the future. It's one of the few places we have as a company to talk directly to the community we've helped build and love so much. As always, sound off in the comments about what you think of the changes, ideas you have about how to make it better, or take an extra step and become a contributor writing code. Until next time!",[],{"_key":240,"_type":64,"children":241,"markDefs":256,"style":84},"c3c375c47dbd",[242,247,252],{"_key":243,"_type":68,"marks":244,"text":246},"c3c375c47dbd0",[245],"em","Jon is a developer and heads up evangelism efforts at Stack Exchange. You can follow him on ",{"_key":248,"_type":68,"marks":249,"text":251},"c3c375c47dbd1",[245,250],"95ccf311a53b","Twitter",{"_key":253,"_type":68,"marks":254,"text":255},"c3c375c47dbd2",[245],".",[257],{"_key":250,"_type":82,"href":258,"reference":12},"https:\u002F\u002Ftwitter.com\u002Fjonhmchan",true,"2015\u002F07\u002F01",{"_type":53,"asset":262},{"_ref":263,"_type":56},"image-1799207a456f9dd6bed1ee19382926cf1d20b220-800x534-jpg",{"code":265,"language":266},"\u003Cp>Today, we're proud to announce the new Stack Exchange blog, all shiny and new! It's been \u003Ca href=\"http:\u002F\u002Fmeta.stackexchange.com\u002Fa\u002F19514\u002F242868\">six to eight weeks\u003C\u002Fa> in the making and we're really happy our community can finally see it. Here's an overview of the major changes that we've made to the site:\u003C\u002Fp>\n\u003Ch2>Channels\u003C\u002Fh2>\n\u003Cp>The biggest change we've made is the introduction of channels on the blog. In the previous blog, we pretty much put everything in one column, organized by tags. We still have all the posts in chronological order on \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002F\">the homepage\u003C\u002Fa> of the new blog, but we realized there are two big buckets of content that we want to post here: company news and engineering posts. We want to recast our blog not just as a place to post updates as they come, but to become an amazing source of news, technical knowledge, and insight into the communities we've built.\u003C\u002Fp>\n\u003Ch3>\u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany\">Company News Channel\u003C\u002Fa>\u003C\u002Fh3>\n\u003Cp>\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002Fl5ilk.jpg\" alt=\"\">\nIf you've been visiting our blog regularly, this channel houses the kind of content you should already be very familiar with. This includes all of the \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany\u002Fpodcasts\">podcasts\u003C\u002Fa>, \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany\u002Fannouncements\">announcements\u003C\u002Fa> about the company, and updates about the Stack Exchange \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany\u002Fcommunity\">community\u003C\u002Fa>. In effect, this is exactly what the old blog was and will continue to be - with some added features. We've also decided to include more posts in this channel that we want to highlight: happenings in the office with explanations of our internal \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany\u002Fcommunity\">culture\u003C\u002Fa>, and all the amazing \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fcompany\u002Fdiversity\">diversity\u003C\u002Fa> efforts we've been pursuing. This is the place to learn everything about Stack Exchange the community and the company.\u003C\u002Fp>\n\u003Ch3>\u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002Fengineering\">Engineering Channel\u003C\u002Fa>\u003C\u002Fh3>\n\u003Cp>\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002FXLXZY.jpg\" alt=\"\">\nThe newest addition to the blog is the engineering channel. One of my favorite things about working at Stack Exchange is the amazing engineering culture we've built and our place in the developer community at large, especially with Stack Overflow. This channel gives you an inside look into that culture: how we build things, why we build them, and what we think about approaching technical problems. This includes technical walkthroughs of new features we've built, announcements of open source projects we're working on, and the public outreach efforts we're working on for the developer community. This blog even includes reposts of some of engineers' most popular posts on their personal blogs, as well as opinion pieces on technical practices. There's even a walkthough of how we built the new blog on the channel \u003Ca href=\"http:\u002F\u002Fblog.stackexchange.com\u002F2015\u002F07\u002Fhow-we-built-our-blog\u002F\">you can read now\u003C\u002Fa>!\u003C\u002Fp>\n\u003Cp>There's a subsection for each major part of our engineering team: developers, SREs, designers, and anyone else that touches our product creation process. As we grow, you can expect to see more content fill up here, and possibly bring in outside contributors as well.\u003C\u002Fp>\n\u003Ch2>An all new design\u003C\u002Fh2>\n\u003Cp>The most notable thing that we changed is the overall design. We wanted to make something that people enjoy reading, exploring, and learning from. Most of all the things from the previous blog still exist: previous posts with archived comments, tagged posts sortable by category, and so on. We've also added some additional functionality here: new navigation that emphasizes our new channels and content, posts sortable by author, and better feeds with individual post pages for readability. Take a look around, there's a lot of changes we've made here.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002FjfB91.png\" alt=\"\">\u003Cem>A new navigation that emphasizes the new channels and subsections we want to emphasize\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002FfdA9K.png\" alt=\"\">\u003Cem>Better overview look that's more photo heavy, provides an excerpt, and the ability to look through posts sortable by authors\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002Fgu34P.png\" alt=\"\">\u003Cem>A revamped individual post view with bigger text, more spacing, and more photo heavy\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch2>Open source\u003C\u002Fh2>\n\u003Cp>\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002FggOC0.png\" alt=\"\">\nThe last thing I want to mention is that we've made the code for our blog \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FStackExchange\u002Fblog\">open source\u003C\u002Fa>. One of the things we love doing as an engineering team is to work in the open when we can. We love involving the communities we build in almost everything we do as a rule, especially our technical community, and the blog is no exception to that rule. We've migrated our previous blog from a Wordpress site and rebuilt our new blog powered by \u003Ca href=\"http:\u002F\u002Fjekyllrb.com\u002F\">Jekyll\u003C\u002Fa>, which is also open source.\u003C\u002Fp>\n\u003Cp>If you have suggestions for how to make the new blog better, \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FStackExchange\u002Fblog\u002Fissues\">create an issue\u003C\u002Fa> and one of our developers will take a look at it (probably me). If you're a developer, we encourage you to take a look at the source code and make \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FStackExchange\u002Fblog\u002Fpulls\">pull requests\u003C\u002Fa> for changes as well. If you want a walkthrough of how we built the blog, take a look at the engineering channel for an inside look.\u003C\u002Fp>\n\u003Ch2>More to come\u003C\u002Fh2>\n\u003Cp>There's so much more we want to do with this blog in the future. It's one of the few places we have as a company to talk directly to the community we've helped build and love so much. As always, sound off in the comments about what you think of the changes, ideas you have about how to make it better, or take an extra step and become a contributor writing code. Until next time!\u003C\u002Fp>\n\u003Cp>\u003Cem>Jon is a developer and heads up evangelism efforts at Stack Exchange. You can follow him on \u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fjonhmchan\">Twitter\u003C\u002Fa>.\u003C\u002Fem>\u003C\u002Fp>","html","2015-07-01T12:00:00.000Z",{"current":269},"the-new-stack-exchange-blog",[271,279],{"_createdAt":272,"_id":273,"_rev":274,"_type":275,"_updatedAt":272,"slug":276,"title":278},"2023-05-23T16:43:21Z","wp-tagcat-announcements","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":277},"announcements","Announcements",{"_createdAt":272,"_id":280,"_rev":274,"_type":275,"_updatedAt":272,"slug":281,"title":283},"wp-tagcat-company",{"current":282},"company","Company","The New Stack Exchange Blog",[286,292,298,304],{"_id":287,"publishedAt":288,"slug":289,"sponsored":12,"title":291},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":290},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":293,"publishedAt":294,"slug":295,"sponsored":12,"title":297},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":296},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":299,"publishedAt":300,"slug":301,"sponsored":12,"title":303},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":302},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":305,"publishedAt":306,"slug":307,"sponsored":12,"title":309},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":308},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":311,"sourceMap":-1},{"count":312,"lastTimestamp":313},2,"2023-05-25T09:45:54Z"]