Jalpc-A

Jalpc-A is an open-source blog theme that pairs a Jekyll static site generator with an AngularJS single-page front end, using Leancloud as its user-authentication and comment backend.

What is Jalpc-A?

Jalpc-A is a front-end web application written in AngularJS, with a visual theme similar to the author's Jekyll theme Jalpc. It runs on Jekyll, so article content is written in Markdown and built into static HTML, while client-side AngularJS renders dynamic views such as the blog list, detail pages, and comment threads. The backend platform is based on Leancloud, and the project states that Parse can be used as an alternative. The author is JiaKunUp, and the live demo is at http://angular.jack003.com.

Key Features

• GitHub login — Users can sign in with their GitHub account through the Leancloud engine, producing a username made of gh_ plus the GitHub username.
• Rich text editor — The angular-summernote editor lets authors write styled articles with images and videos; uploaded images are stored on Qiniu cloud service.
• Comments — Logged-in users can comment using the same summernote editor, reply to other comments, and delete their own comments.
• QR code sharing — Every blog post gets a QR code generated by angular-qrcode that encodes the absolute URL, letting readers open the post on other devices.
• Pagination — Blog listings use ui-bootstrap, with a custom fix that keeps the page number in the URL so browser back and forward work between pages.
• Web analytics — Google Analytics is integrated; replace the tracking snippet in website.html with your own account.
• Safe connections — Account and token connections run over https://api.leancloud.cn, while JSONP scripts for GitHub login and short URLs come from jalpc-a.leanapp.cn.

The main entry page is website.html, and the AngularJS application logic is located in js/app.js. The stack includes Bootstrap, ui-router, ui-bootstrap, angular-toastr, angular-summernote, and angular-qrcode, all listed in the project's acknowledgements.

Who is it for?

Developers who want a Jekyll site with an AngularJS single-page interface get a complete starting point with authentication already wired. Bloggers who need user accounts and comments without running their own server can rely on the Leancloud integration. Teams that want a blog where only the admin publishes posts while visitors write comments can configure it that way, or allow everyone to add blogs.

What can you do with Jalpc-A?

• Personal blogging: Write Markdown posts, publish them as an AngularJS single-page blog, and share each post via the auto-generated QR code.
• Community comments: Let visitors log in with GitHub and comment using the rich text editor, including reply and delete actions.
• Self-hosted deployment: Host the static output on GitHub Pages for free, point the CNAME file at your own domain, and keep the comments synchronized through Leancloud.

How does Jalpc-A work?

Start by forking and cloning the repository, then install Jekyll if you don't have it. Register a Leancloud application, copy its App ID and App Key into js/app.js, and run jekyll serve --watch to view the site at localhost:4000. For production, push to GitHub Pages or any static host; you can also serve website.html with npm or another local web server after removing the front matter.

FAQ

Is Jalpc-A free to use?

Yes, Jalpc-A is released under the MIT License, and the static output can be hosted for free on GitHub Pages. The open-source project accepts contributions via pull requests.

How do I set up user comments and login?

You need a Leancloud account; create an application and copy its App ID and App Key into js/app.js. GitHub login is handled by the separate Jalpc-A-engine Leancloud engine project linked in the repository.

Can I use Parse instead of Leancloud?

The project states that Parse can be used as an alternative because the backend platform is based on Leancloud and Parse is similar. You would need to adapt the API calls accordingly.

What should I do if I want a custom domain?

Edit the CNAME file in the repository root to include your domain, and configure the same domain in your GitHub Pages repository settings.

Which features are still missing?

The project's to-do list includes a search page, a donate button, a message system, and sending email. These are not yet implemented in the template.