Skip to content

Commit 5fe56ec

Browse files
authored
docs: push docs on release (#468)
1 parent 9f0606b commit 5fe56ec

21 files changed

Lines changed: 142 additions & 118 deletions

File tree

.github/workflows/push-docs.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
on:
2+
release:
3+
types: [published]
4+
workflow_dispatch:
5+
6+
jobs:
7+
push-docs:
8+
runs-on: ubuntu-latest
9+
steps:
10+
- name: Checkout code
11+
uses: actions/checkout@v2
12+
13+
- uses: Jahia/github-to-academy@v1
14+
with:
15+
files: docs/**/*.md
16+
graphql-endpoint: ${{ secrets.ACADEMY_ENDPOINT }}
17+
graphql-authorization: ${{ secrets.ACADEMY_AUTHORIZATION }}

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
# Javascript Modules
66

7-
You want to build a JavaScript Module? [Read the documentation 📖](docs/)
7+
You want to build a JavaScript Module? [Read the documentation 📖](https://academy.jahia.com/tutorials-get-started/frontend-developer/introduction)
88

99
This project is designed to support Javascript developers working with _Jahia_. It consists of two components:
1010

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/introduction
4+
jcr:title: Introduction
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
9+
10+
Welcome to the JavaScript Modules documentation!
11+
12+
Currently in Beta, this technology is actively developed and the first stable version (v1) is scheduled for release in Autumn 2025. We actively support this new technology, and we consider it ready for production: you can build a production-ready Jahia website with JavaScript and React.
13+
14+
It is considered Beta as Jahia UI extensions and OSGi interactions can only be written in Java for now, these features are not yet available to JavaScript modules.
15+
16+
![JavaScript Modules Hello World](./hello-world.png)
17+
18+
Here is what you would get within minutes. The code is written in React/JSX and made interactive on the client; Jahia is the first Java CMS to support [partial hydration/island architecture](https://www.jahia.com/blog/leveraging-the-island-architecture-in-jahia-cms) on the market.
19+
20+
This documentation is meant for self-learning, but we also offer workshops and training sessions with our team. If you are interested in that, please [contact us.](https://www.jahia.com/contact)
21+
22+
If you're still reading this and want to get started—for real—[let's dive in!](/cms/{mode}/{lang}/sites/academy/home/get-started/front-end-developer/setting-up-your-dev-environment.html)
387 KB
Loading

docs/1-getting-started/1-dev-environment/README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
# Setting Up Your Dev Environment
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/setting-up-your-dev-environment
4+
jcr:title: Setting Up Your Dev Environment
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
29

310
This tutorial will guide you through the setup of your development environment to start a local Jahia instance and create a new project. We assume you have some familiarity with JavaScript and React, if that's not the case, we recommend you to follow a few tutorials to learn the basics:
411

@@ -96,4 +103,4 @@ Now that your _template set_ (that's how we call a module that provides page tem
96103

97104
Congratulations! You have successfully set up your development environment and created a new project in Jahia. In the next sections, we'll start building the project.
98105

99-
Next: [Making a Hero Section](../2-making-a-hero-section/)
106+
Next: [Making a Hero Section](making-a-hero-section)

docs/1-getting-started/2-making-a-hero-section/README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
# Making a Hero Section
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/making-a-hero-section
4+
jcr:title: Making a Hero Section
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
29

310
In this section, we'll create a hero section for our website. A hero section is a large, full-width section at the top of a page. It usually contains a title, a subtitle, and a background image.
411

@@ -264,4 +271,4 @@ You can add as many CTAs as you want to your hero section. This is why we haven'
264271
> For instance, you should be able to find the content you created at the `sites/<site key>/home/main` path.
265272
> It can be useful to remove buggy nodes or to understand how your data is persisted.
266273
267-
Next: [The "About Us" Page](../3-the-about-us-page/)
274+
Next: [The "About Us" Page](the-about-us-page)

docs/1-getting-started/3-the-about-us-page/README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
# The "About Us" Page
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/the-about-us-page
4+
jcr:title: The "About Us" Page
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
29

310
Our homepage is based on a "basic" layout: take a look at `src/templates/Page/basic.server.tsx`. It's a single column layout defined by an `<Area>` without any constraints. If a user wants to place many Hero sections on the page, they can do it. Most websites have a slightly more controlled layout: a navbar, a title, a footer, optional sidebars, etc. In this section, we'll create a page layout that suits a typical "About Us" page.
411

@@ -263,4 +270,4 @@ Try adding a few links to the footer that should be created at the end of the `s
263270

264271
If you create another page with **Single column**, you should be able to create a new Hero section, but the footer will be the same as the one on the "About Us" page.
265272

266-
Next: [Making a Blog](../4-making-a-blog/)
273+
Next: [Making a Blog](making-a-blog)

docs/1-getting-started/4-making-a-blog/README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
# Making a Blog
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/making-a-blog
4+
jcr:title: Making a Blog
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
29

310
So far we only considered contributing pages visually, directly in Page Builder. This is great for individual, unique pages but it's not the best way to manage a blog. In a blog, you want all your articles to have the same structure and style, and you want to be able to manage them all in one place.
411

@@ -205,4 +212,4 @@ We used `currentResource.getLocale().toString()` to get the locale of the curren
205212

206213
There are a lot of things to discover about JCR queries, as it allows you to query, filter, order and paginate contents in a tree-like structure. You can find more information in the [Jahia documentation](https://academy.jahia.com/documentation/jahia-cms/jahia-8.2/developer/leveraging-jahia-backend-capabilities/jcrsql2-query-cheat-sheet).
207214

208-
Next: [View Content in Full Page](../5-view-content-in-full-page/)
215+
Next: [View Content in Full Page](view-content-in-full-page)

docs/1-getting-started/5-view-content-in-full-page/README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
# View Content in Full Page
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/view-content-in-full-page
4+
jcr:title: View Content in Full Page
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
29

310
The goal of this section is to render a full-page view of a content node. We'll continue with our blog example, and instead of a 404 page, we'll create a page to display a single blog post.
411

@@ -141,4 +148,4 @@ In JCR, everything is a node, i.e. an entity of a tree designated by a path. The
141148

142149
There is a lot more to learn about URL building and JCR exploration, and it's the topic of the next section.
143150

144-
Next: [Building a Navigation Bar](../6-building-a-nav-bar/)
151+
Next: [Building a Navigation Bar](building-a-nav-bar)

docs/1-getting-started/6-building-a-nav-bar/README.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
# Building a Navigation Bar
1+
---
2+
page:
3+
$path: /sites/academy/home/get-started/front-end-developer/building-a-navigation-bar
4+
jcr:title: Building a Navigation Bar
5+
j:templateName: documentation
6+
content:
7+
$subpath: page-area/content
8+
---
29

310
A navigation bar is a common component in web development. It allows users to navigate between different pages of a website. In this section, we will build a navigation bar for our blog site.
411

0 commit comments

Comments
 (0)