Meta tags:
description= ...;
Headings (most frequently used words):
minimal, head, part, page, multiple, types, recent, blog, posts, on, coffee, coder, code, conclusion, layouts, and, components, refactor, list, all, results, more, field, pages, single,
Text of the page (most frequently used words):
the (22), content (18), page (16), and (14), one (13), hub (12), this (11), part (11), #minimal (11), experience (11), edge (11), blog (10), headless (10), posted (9), sitecore (9), head (9), series (8), post (8), posts (7), 2024 (7), pages (7), multiple (7), types (7), which (6), for (5), single (5), generate (5), thu (5), but (5), some (5), want (4), build (4), that (4), type (4), use (4), time (4), list (4), need (4), all (4), 2025 (3), more (3), far (3), can (3), static (3), using (3), previous (3), only (3), additional (3), field (3), been (3), script (3), also (3), html (3), codeflood (2), going (2), explore (2), how (2), site (2), generator (2), wed (2), showed (2), now (2), many (2), used (2), fields (2), text (2), has (2), extend (2), make (2), these (2), aug (2), processing (2), query (2), results (2), display (2), them (2), have (2), add (2), nov (2), duplicated (2), code (2), keep (2), with (2), different (2), layouts (2), components (2), bash (2), process (2), not (2), email, protected, copyright, 2010, multi, progress, building, ssg, cms, restrained, toolset, dependencies, jun, minimum, required, consuming, manage, delivered, via, exercise, jul, short, rich, tenant, date, select, output, tue, allblogpost, returns, items, point, hit, size, limit, won, rework, querying, able, over, each, had, are, generated, way, navigate, users, index, shows, provides, links, sep, kind, item, sites, rarely, files, new, sun, last, lot, file, clean, further, spend, refactoring, improve, structure, apply, dry, principal, don, repeat, yourself, extracting, logic, separate, functions, refactor, added, back, templates, duplicating, quite, bit, between, sure, boilerplate, consistent, create, any, specific, across, concepts, feb, reasons, chose, orchestrate, was, due, ubiquity, around, long, present, platforms, most, frequently, mention, dev, machines, wrap, wanted, run, github, bitbucket, may, conclusion, recent, coffee, coder, test, runner, revolver, home,
Text of the page (random words):
codeflood home blog revolver test runner recent blog posts on coffee coder code minimal head part 9 conclusion thu may 01 2025 posted in headless content hub one experience edge sitecore one of the reasons i chose to use bash to orchestrate the build process for my minimal static site generator was due to it s ubiquity bash has been around for a long time and it s present on the build platforms i most frequently use not to mention on my dev machines so to wrap up this series i wanted to have the build process run not only on github but also bitbucket minimal head part 8 layouts and components thu feb 27 2025 posted in headless content hub one experience edge sitecore i added multiple page types back in part 6 multiple page types of this series but with multiple different pages i m using multiple different html templates duplicating quite a bit of html between them i want to make sure i keep all that html boilerplate consistent which i ll do with layouts i also want to create some components which can be used on any page to display specific content across many pages i ll explore these concepts in this post minimal head part 7 refactor wed nov 20 2024 posted in headless content hub one experience edge sitecore in the last post of this series i duplicated a lot of code in the script file to keep the script clean as i extend it further and add more page types i need to spend some time refactoring to improve the structure of the script i can also apply the dry principal don t repeat yourself by extracting duplicated logic to separate functions minimal head part 6 multiple page types sun nov 10 2024 posted in headless content hub one experience edge sitecore so far in this series i ve only been processing a single kind of content item and that s blog posts but sites rarely have a single content page type it s time to add an additional page type and generate the static files for this new page type minimal head part 5 list page thu sep 12 2024 posted in headless content hub one experience edge sitecore in previous posts of this series i showed how to generate pages for each blog post i had in content hub one now the pages are generated i need some way to navigate and display the list of blog posts to users i need to generate a list page index page that shows all the blog posts and provides links to them minimal head part 4 page all results thu aug 22 2024 posted in headless content hub one experience edge sitecore in the previous posts in this series i ve been processing multiple pages by using the allblogpost query field which returns a list of blog post content items but at some point i m going to hit the page size limit and a single query won t do i need to rework my querying to be able to page over all the results in experience edge minimal head part 3 more field types tue aug 06 2024 posted in headless content hub one experience edge sitecore so far in this series i ve only used 2 types of fields short text and rich text but the blog post content type in my content hub one tenant has some additional field types which i want to use date and time and select in this post i ll extend the blog post output to make use of these additional fields minimal head part 2 multiple pages thu jul 18 2024 posted in headless content hub one experience edge sitecore in the previous post i showed the minimum required to generate a single page consuming content which i manage in content hub one and which is delivered via experience edge now i want to build on that exercise and generate many pages minimal head part 1 single page wed jun 19 2024 posted in headless content hub one experience edge sitecore in this multi part series i m going to explore how far i can progress building a static site generator ssg for a headless cms using a restrained toolset and minimal dependencies more blog posts copyright codeflood 2010 2025 email protected
|