Slate v3 Technology Preview 0 #1271
Replies: 4 comments 8 replies
-
|
Do we plan to add webpack to the mix to better handle the process of building out our dependencies, combining JS files, and minifying them? |
Beta Was this translation helpful? Give feedback.
-
|
Personally I'm not a huge webpack fan, but I'm open to it if it brings benefits. The TP already uses minified versions of the main JS libs and HTTP/2 is more prevalent now (including GitHub pages), making bundling less of a concern. Eleventy has an HTML minifying plugin which could be worth a look? |
Beta Was this translation helpful? Give feedback.
-
|
The current version is designed for the fork/template & clone workflow, but I have got a proof-of-concept working which would allow the |
Beta Was this translation helpful? Give feedback.
-
|
One of the things I think would benefit from bringing in webpack would be to also use it to install third-party JS libs that we would install via NPM, instead of having them be vendored within the source tree. |
Beta Was this translation helpful? Give feedback.
-
|
Already done (without webpack). |
Beta Was this translation helpful? Give feedback.
-
|
The As you can see from the |
Beta Was this translation helpful? Give feedback.
-
|
I'm keen on using this as a node shop. Is there anything one should be aware of as far as not yet implemented features? |
Beta Was this translation helpful? Give feedback.
-
|
Having issues running npm run serve.local. Something to do with the sass configuration. What tags are you using to track v3 if any? Serve seems to work just fine. |
Beta Was this translation helpful? Give feedback.
-
|
What are you trying to achieve with running When Slate v3 is published to npm, we will use tags such as |
Beta Was this translation helpful? Give feedback.
-
Slate v3 should be 100% compatible with latest Ruby Slate for the simple case of an input |
Beta Was this translation helpful? Give feedback.
-
|
Oh great. Also apologies in regards to the serve local. I didn't actually look into what it was doing before leaving that comment. I just noticed it hadn't run out of the box. |
Beta Was this translation helpful? Give feedback.
-
|
An issue with a GPL-licensed dependency which may have prevented us releasing this under an Apache-2.0 license (like Slate v2) has been resolved. |
Beta Was this translation helpful? Give feedback.
-
Two announcements today, first thanks to the hard work of my co-maintainers Matthew Peveler and Robert Lord, and many members of the Slate community, we are happy to present Slate v2.7.0.
Secondly, we have something we'd like lots of feedback on.
The Slate v3 technology preview (the
v3branch) is a ground-up reworking of Slate using pure Node.js and the eleventy static-site-generator.The Slate v3 technology preview uses the exact same CSS and client-side JavaScript (apart from a couple of compatibility tweaks) as Ruby Slate, so the output HTML should function exactly as in Ruby Slate.
Ports of Slate including to Node.js are nothing new and indeed Mike's own Shins project has been tracking releases of Ruby Slate since late 2016, however, this technology preview is not based on Shins or any of the other outdated ports, and leverages
eleventyto minimise the amount of custom code and dependencies required to build your documentation with Slate.The fact that three of our core client-side JS libraries can be included in the Node.js
package.jsondependencies makes the process of keeping them up to date much simpler. It also paves the way to potentially move thelunrsearch index generation to the server side, which would allow multi-page searches.The Future
It is important to be clear what the function of the technology preview is. It is primarily focused on getting feedback from the community.
eleventy-basedWe are saying that we recognise that the Ruby and
middlemaninfrastructure used by Slate has historically caused the community, and maintainers, a good deal of headaches over the years.We particularly want to hear your experiences of using the technology preview in these areas:
sourcedirectory structure or have a clean break?In addition to the concrete areas above, we would welcome feedback on the adoption of
eleventyitself; we note that the project is relatively young (circa two and a half years) and has not yet reached the milestone of a stablev1.0.0release. Also,eleventyhas a fair number of open issues and this is with it using the lodash style of issue management where enhancement requests and documentation change issues are closed, but still monitored.eleventywhile not being one of the most well-known static site generators, is actively maintained and it fits the requirements of supporting markdown andejstemplates while not including large unnecessary dependencies such asReactorVue.js, or being primarily focused on being a blog framework. We believe the Slate community could be beneficial to theeleventycommunity in terms of visibility and additional contributors.eleventyalso has a well thought-out plugin system.We know that the provided documentation is very bare-bones at the moment, but we would plan to copy over the remainder of the
READMEand start the process of updating the Wiki if the technology preview warrants moving to the next phase.One more thing to make clear, we are accepting Pull-Requests against the technology-preview branch, but these should be bug fixes and documentation improvements rather than new features at this stage.
Many thanks for reading, and we look forward to your feedback.
Beta Was this translation helpful? Give feedback.
All reactions