Is it possible to define which exact pages to build?

[ar-arkhipov]

I wonder if it is possible (and how) to tell Eleventy to build only particular page or set of pages? For example build only particular page (specified via permalink ?), or build all (or define number) pages from the posts section (/posts/*), etc.

I can dig into Eleventy source code, but if someone already has an answer it would be great. Thanks!

[Ryuno-Ki]

Closest I can think of is the input parameter.

[pdehaan]

I think some people have cleverly used the .eleventyignore file in the past to only build a subset of their site during local development (where you might only want to build 10 blog posts vs 2000+).

[pdehaan]

#1123 might also have some tips. You could possibly use a global eleventyComputed file or data directory file which checks for an environment variable and optionally sets a bunch of templates to permalink: false.

[edwardhorsford]

Unfortunately setting permalink: false still results in the files being processed. As a result you don't actually save much time on a large site - the full site data is still being worked through.

[nhoizey]

What about setting eleventyExcludeFromCollections to false in addition? I think it might help.

[ar-arkhipov]

The idea is to be able to run parallel builds for the same website. For example, if I have website consisting of 100 000 pages I would like to be able to execute 20 parallel builds (for example in AWS lambda) where each build processes 5000 pages. But at the same time I want to keep the website structure, pagination, etc., where in the end I can upload all the final files from 20 workers in the one S3 bucket. That is what I am trying to achieve.

[coryasilva]

I am thinking this could work:
lambda to collect page data --> kinesis data stream --> lambda build page --> s3 --> cloudfront

What is the source of your data? Static files or API?