Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Velocity: Define names for parts in config.wyam #637

Closed
onnotasler opened this issue Feb 27, 2018 · 3 comments
Closed

Velocity: Define names for parts in config.wyam #637

onnotasler opened this issue Feb 27, 2018 · 3 comments
Labels
General Enhancement New feature or request

Comments

@onnotasler
Copy link

At the moment, the booksite recipe requires manually editing the cshtml pages to rename the titles of different parts, like "blog", "chapters", or "introduction". In some cases (blog and chapters) I did not find yet all entries that I have to change to properly rename them.

I propose to instead define those names in the config.wyam, replacing the actual entries by variable placeholders. this would make the theme more versatile (as one could for example change easily rename the Chapters to Essays for a series of essays or Steps for a tutorial) as well as easier to translate into other languages.

@daveaglick daveaglick added the General Enhancement New feature or request label Feb 28, 2018
@daveaglick
Copy link
Member

That sounds totally reasonable. Just so I’m clear - you’re talking about the headers for different sections of the pages?

@onnotasler
Copy link
Author

I assume so, I am not sure what they are called. They are defined in the

and title: of the cshtml files, and probably in some other places as well (because, as I said, I have not yet found all of them).

@daveaglick
Copy link
Member

As much as I hate to, I'm going to close this as "won't fix". The BookSite recipe is going to be removed in the next version in preparation for combining all the recipes into a single omnibus static site generator application (see #668). Blog and Docs will stick around until vNext is ready, but there just isn't value in spending time supporting BookSite when it's usage is an order of magnitude less than the other two recipes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
General Enhancement New feature or request
Development

No branches or pull requests

2 participants