Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature Request: Templating System #129
You Can customize the blade templates by editing them to your specs. A template Generator is a good idea but if it should be added, I'll suggest it as a plugin extention and not part of bookstack core. For now, you can edit the desired templates at Resources/views/* directory.
1 similar comment
referenced this issue
May 17, 2017
@skluthe No, not really, although it's high up in terms of thumbs-up so won't go ignored and is something I think would be greatly beneficial in a platform like this.
I've been thinking the sidebar on the page editor would be a good place to have a listing of templates. Ideally with a preview but that gets more complex.
The trickier part is defining templates. Easiest option would be a simple checkbox option on page created to 'Mark as template'. Then you could organise your templates into their own book if you wanted. Would be much more complex to develop a whole separate 'Template manager' area.
@davidPilkington Yeah, It would be a standard page in all other respects.
This is a fairly highly requested feature and something I think would be a good fit for BookStack so I have marked it for implementation in the major release after the next (v0.27). This schedule is based on the below proposal, If below does not meet most use-cases this schedule may have to change.
The below proposal defines the initial implementation to meet this feature request so is therefore simplistic but can be built upon in the future.
By utilising the existing page system it brings loads of useful things with it (Permissions, organisation, editor, revisions) reducing implementation effort greatly. One of the main concerns I can foresee is that people won't want template items like this visible in areas like 'Recently updated'.
We could maybe ignore pages marked as templates in various lists or alternatively we could maybe give chapters their own little feature of being able to mark themselves, and their contents, as being "Unlisted" which will hide content from such lists, Perhaps also prevent search-engine parsing. You could have a "Meta book" (Admins only) with chapters (Allow all to view) to hold templates/other bits but have their contents unlisted. More hassle to build and for admins to set-up but adds a system-wide feature that could be used for other bits and makes chapters a little more unique. Just throwing out ideas though. I'll have a think.
Feedback welcomed and appreciated.
Would the meta book be optional for templates?
The other ideas sound really great however.
Ah that would be great :) Dan Brown writes:…
@Nebucatnetzer Yeah, The "Meta Book" is only an example of how I'd imagine a lot of admins would do the set-up. You'd be free to set whatever permissions you'd want on it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
We have three teams using our Stack: Account, Dev, and QA. They all have their own Shelves.
I like the proposal as is, as I am in charge of document control, so being able to create an un-shelved book and restrict it to myself would make it where others can't edit the templates, but would be free to use the templates when creating pages in books on their shelves. That would be extremely useful.