Here are some of the advantages and disadvantages that come to my mind:
<strong> Benefits
- can be deployed on each server since it is just static html
- has partial ones that can be reused, unlike normal html, where you need to encode / copy all elements
- you can still use IDE code
- no developer can edit the code (sometimes at least)
disadvantages
- the template language is limited and sometimes a little uncomfortable / should get used to
- you have something new in your environment that has additional costs (more than one developer needs to know how to create a site, ...)
If you know your current toolkit well and you have no problems hosting another ASP.net project on your server, I donβt see the need to implement another tool in the tool.
If you want to do something where users can generate content - like github on github pages - this is what you might think.
As for Jekyll, we tried it in one project and are developers who like to code, we came across its limitations quite early. You can get around this, but if you know a programming language, you will be faster. It was still fascinating how far we could with Jekyll.
topek source share