emilbaehr/automatic-app-landing-page

A Jekyll theme for automatically generating and deploying landing page sites for mobile apps.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Type:Template / ExampleCategory(s):CMS, Static Sites & ForumsWeb Development
Added to GitGenius on September 19th, 2026
Created on January 5th, 2019
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 1,789
Total Stargazers: 3,627 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 hours
Mean response time: 2.1 hours
90th percentile: 2.1 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 527 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Automatic App Landing Page is a Jekyll theme that generates and deploys landing page sites for mobile apps on GitHub Pages.

The tool solves the problem of creating a professional app landing page without writing HTML or CSS. It works by letting developers fork the repository, enter their iOS App ID in a configuration file, and the theme automatically fetches the app icon, name, price, and App Store link. Customization happens entirely through the `_config.yml` file, where developers can set colors, text, feature lists, social links, and other branding elements. The site deploys immediately to GitHub Pages with no additional setup required.

This tool suits indie developers and small teams launching iOS or Android apps who want a polished landing page in minutes rather than hours. It works best for straightforward app promotion sites where the standard layout and structure meet the need. Developers should choose it if they are comfortable with GitHub Pages hosting and want to avoid writing any markup or styling code. Those needing highly custom designs or complex layouts may find the configuration-only approach limiting.

The project shows infrequent commit activity with long gaps between updates. Issues and pull requests receive responses, though resolution timelines vary. The codebase remains stable with no active refactoring or major feature additions in recent periods.