Comments (5)
+1 for your implementation proposal of 4 for now.
Whatever we do, the resolution will have to somehow end up into the VCL (determine if template selector or content file name).
When we hlx publish
can't we just build the list of known template selectors and add it to the dynamic.vcl
. When parsing the request, if the selector is not in that list, than consider as part of content file name.
from project-helix.io.
DO you have a preference for 2 or 3?
2 could look like this:
strains:
- name: default
selectors:
- nav
- video
from project-helix.io.
oh sorry if this was not clear, I think it should be automatic, i.e. no extra config! You can compute this list based on the list of templates in the project folder and fallback to content if the selector is not part of this list.
Thus I assume this is 3 (but without a lookup, list is pre-computed on publish).
from project-helix.io.
Ah, inspecting the available templates is a good idea. We just have to find a way to carry that information forward.
from project-helix.io.
That was my initial proposal: generate a list in dynamic.vcl
(or a dedicated file for that). If selector in the list, use as template, otherwise append to content path. Something like that ;)
from project-helix.io.
Related Issues (20)
- smoke test deploy and publish
- Error when updating submodules HOT 1
- Update 60s guide to reflect changes in static file handling HOT 1
- Revisit structure and get rid of submodules
- Setup linting
- Remove usage of content.children
- Cannot install helix on Windows 10 HOT 2
- Error in adobeio runtime bleeds through to the browser HOT 1
- Debug instruction in documentation on https://www.project-helix.io/ website HOT 3
- Missing documentation how to build composed pages. HOT 1
- Documentation: clarification regarding dynamically rendered components HOT 1
- Publish fails due to expired Fastly token
- Cannot helix deploy the project HOT 3
- Invalid last modified date HOT 4
- update architecture diagram to reflect new dispatch flow HOT 1
- Fastly is not serving proper 404 or 500 error page
- /pipeline/README.html doesn't work anymore HOT 6
- Rename branch "master" to "main" HOT 2
- [project-helix.io] Clicking on anatomy of the pipeline results in 403 forbidden HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from project-helix.io.