hackforla / hackforla/knowledgebase-content

Create a Guide/Template: Landing page with mailing list (pre product launch) for your project

Abierto
#17 11 comentarios 0 reacciones 0 asignados Ver en GitHub
Complexity: Missing CoP label: checked CoP label: shortcuts added CoP: Product feature : guide creation Phase: 1 - Gather Examples Solo Ready for Bonnie Triage size: missing status: 1.1 needs wiki examples
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2
Forks
1
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Overview
We need to create a guide to making a Landing page with mailing list so that projects can have a place to part their domain name and gather interest in the project, so that they launch to an interested audience.

### Action Items
The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labelled 'Tasks' at the bottom of this issue, and complete each task listed.
- [ ] [Gather Examples Solo](https://github.com/hackforla/guides/wiki/How-to-Gather-Examples:-Solo) (open in a new tab)
- [ ] [Gather Examples Collaboratively](https://github.com/hackforla/guides/wiki/Phase-2-%E2%80%90-Gather-Examples-Collaboratively)
- [ ] [Create a Guide Draft](https://github.com/hackforla/guides/wiki/How-to-Draft-a-Guide)
- [ ] If needed, create a template
- [ ] [Have your guide peer reviewed](https://github.com/hackforla/guides/wiki/Peer-Reviews-for-Guides)
- [ ] [Present your guide for leadership review](https://github.com/hackforla/guides/wiki/Submitting-Your-Guide-for-Leadership-Review)
### Resources/Instructions
Google Drive Folder for this Guide’s documents and shortcuts (to documents in other locations) [0017[DRAFT]Landing page with mailing list (pre product launch) for your project ](https://drive.google.com/drive/folders/1uFJ2xd0KFL8Lxl89ROXLWIb7rMRUq3lu)
#### Examples
###### 100 Automations
- Hosting Plan after launch: gh-pages
- Landing page: https://100automations.org
- Repo: https://github.com/100Automations/landingpage
- index.html code used: https://github.com/100Automations/landingpage/blob/master/index.html
- Mail Chimp: https://mailchi.mp/6f150ef215c6/100automations
- Logistical details: We created a index.html page on a repo and pointed the domain name at the repo. The index.html page uses an iframe to display the mailchimp content. That way we get a customized url for our landing page, and when we are ready to turn on the actual site, we can point the domain name to the repo the developers have been working on.
- domain : managed by hfla's google domains account
- DNS is pointed at registrar interface with the following settings:

![Screen Shot 2021-02-19 at 1 14 26 PM](https://user-images.githubusercontent.com/37763229/108562306-82daf700-72b4-11eb-8d7d-99361e17f62a.png)

- GitHub settings are as following:

![Screen Shot 2021-02-19 at 1 21 43 PM](https://user-images.githubusercontent.com/37763229/108562897-6f7c5b80-72b5-11eb-9e3d-477b82a55d58.png)

###### Another project that plans to host on AWS or platform than Github's ghpages
Notes: we need an example of a project that is not live yet, but still needs a landing page. Can they turn on ghpages just for the landing page and point that a a specific folder (which github allows) without it affecting their repo in another way? Ask a new project like record clearance to test it.
### Projects to Check
### Tasks
- [ ] This is where you will copy instructions from the wiki page for the step you are currently on.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Empieza por las páginas wiki enlazadas para recopilar ejemplos, redactar una guía y realizar una revisión por pares y una revisión de liderazgo; después, inspecciona 100 Automations index.html, GitHub Pages, Mailchimp y el ejemplo de DNS. Copia las instrucciones pertinentes en la sección Tasks y completa cada fase. Se considera terminado cuando la guía y cualquier plantilla necesaria hayan superado la revisión por pares y la revisión de liderazgo.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
aws, github, html
Área
documentation, web-dev
Tipo de issue
Documentación
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.