https://github.com/radkick/serverlesssite
serverless website with custom headers and footers using bootstrap or framework of your choice
https://github.com/radkick/serverlesssite
Last synced: 4 months ago
JSON representation
serverless website with custom headers and footers using bootstrap or framework of your choice
- Host: GitHub
- URL: https://github.com/radkick/serverlesssite
- Owner: RADKick
- License: mit
- Created: 2019-06-09T13:54:21.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-06-09T14:26:12.000Z (almost 7 years ago)
- Last Synced: 2025-03-26T02:42:40.559Z (about 1 year ago)
- Language: HTML
- Size: 11.7 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
#serverless website - kicksite
Here you are going to use a lightweight js framework kickjs (See kick repo at https://github.com/radkick/kickjs) to host a website.
Also we will serverless framwork to deploy it on AWS S3 or Azure blob
Sample is at src/sample1
## Install
## Getting Started and Documentation
Serverlesssite or kicksite has following main components:
Themes (coming shortly) which will be hire than layouts
Layouts (can be multiple, like default layout, blog layout, category page layout etc)
|_ Widgets (pages which can be used to store pieces of html)
|_ Pages (page which are rendered to the users)
Every html page we create in kicksite is a clone of a layout html, default is _/_$layout.html
Root file is is index.html, which is a copy of _/_$layout.html
```html
kick.bind('', kickSitePageInfo);
```
## Building and Testing
Make sure you have nodejs and npm running
Clone the repository.
Install http-server if you don't have
```
$ npm -g http-server
```
Run http-server from the folder where you cloned the repo.
```
$ http-server src/sample1
```
#### Building
No building required
#### Publishing
You can use AWS Cli to publish, very soon I will post an article on that.
You can use serverless framwork to publish to AWS S3/Azure Blob, very soon I will post an article on that too.
## Contributing
#### Bug Reporting
1. Ensure the bug can be reproduced on the latest master.
2. Open an issue on GitHub and include an isolated [Stackblitz](https://stackblitz.com) demonstration of the bug. The more information you provide, the easier it will be to validate and fix.
#### Pull Requests
1. Fork the repository and create a topic branch.
5. Push your topic branch to your fork and submit a pull request. Include details about the changes as well as a reference to related issue(s).