Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace the default site .html file with some Symbiosis documentation #63

Open
patch0 opened this issue Jun 13, 2017 · 4 comments
Open
Assignees

Comments

@patch0
Copy link
Contributor

patch0 commented Jun 13, 2017

@jamielinux's good idea;

Replace:

screen_shot_2017-05-31_at_16 33 05

With help documentation in some form. Maybe full, maybe single page

Would a high level view of the steps required to setup a standard website work?

Originally reported on Bytemark's Gitlab by @steveu on 2017-05-31T15:46:37.274Z

@patch0
Copy link
Contributor Author

patch0 commented Jun 13, 2017

Yay!

So when this thought originally hit, I was thinking about mostly these two with the filezilla screenshots, and also possibly how to setup a DB:

All on one page, made much briefer so that's it's not so cumbersome, and people can click through to bytemark.co.uk/docs if they need slightly more in-depth instructions. (Could even include the hostname in the instructions, because that can be detected/done on install.) And signposting to other stuff etc.

So basically, a brief, easy to follow quickstart guide to getting a simple site up within minutes. Could possibly even use setting up a basic/empty WordPress site as the ongoing example (ie, install filezilla, upload wordpress site, create the appropriate database via phpmyadmin or something like that).

Originally posted by @jamielinux on 2017-05-31T16:14:41.073Z

@patch0 patch0 added this to the stretch release milestone Jun 13, 2017
@ianeiloart
Copy link

Why not just a page confirming you server is set up, and then an iframe that loads a page that we can fix when we find bad information.

@telyn
Copy link
Contributor

telyn commented Aug 15, 2017

@ianeiloart that's probably a good idea - seems like the complaints about iframes are purely SEO-based which doesn't matter for this. It could be part of the documentation repo then

@patch0
Copy link
Contributor Author

patch0 commented Sep 1, 2017

I think this could be solved by #35. Incidentally #79 fixed the "missing default page for SSL hosted domains".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants