Website development


Where should we discuss the website design? Here? GH wiki? Local pub?
 
Last edited by a moderator:
Where should we discuss the website design? Here? GH wiki? Local pub?
I own a pub. So that seems to be the most logical choice. Every other Thursday at 20:00 in Amsterdam?

We probably need a spot were the people actively working on it can fight among themselves and a spot where everyone can chime in. 
 
I'd say discussions should happen here at there boards.

In case too many chime in, we can always create another internal thread.
 
Let's see first things first.

Who is/are doing the design? And who are the coders? I'm sadly just a coder, I fail miserably at design.

If I recall correctly ED rather not have a cms and is happy to change the content in the code itself so we don't have to think about that.

Are we going to make the website responsive? And if so will we use a framework like Bootstrap3 for it? (http://getbootstrap.com/) If so I'll get that setup. Also happy to learn another framework or have a go at coding the responsive bits from scratch. 

Where do we keep track of who does what? Do we add a file to the repo with a todo list or use something like https://trello.com/ ?
 
Last edited by a moderator:
Who is/are doing the design? And who are the coders? I'm sadly just a coder, I fail miserably at design.
A few people volunteered in this thread and mentioned what they'd like to do.

I need to collect them and then see who wants to work on what.

I'll also create a thread where I mentioned what functions / ideas I have and where everyone can think about what he'd like to do.

If I recall correctly ED rather not have a cms and is happy to change the content in the code itself so we don't have to think about that.
That was for the minimal page - while I don't have problems to change the code directly, a multilanguage CMS-like system seems like a good idea.

We don't need to use an existing CMS though - we can create our own.

Existing ones have the issue that security issues exists, each update can break things and adding your own stuff is not always easy. 

Are we going to make the website responsive? And if so will we use a framework like Bootstrap3 for it? (http://getbootstrap.com/) If so I'll get that setup. Also happy to learn another framework or have a go at coding the responsive bits from scratch.
If it's not too complex, I think responsive web design is a good idea these days - especially as we could make a Pandora / Pyra optimized design as well ;)  

Where do we keep track of who does what? Do we add a file to the repo with a todo list or use something like https://trello.com/ ?
I think a file should be enough for the beginning, if it gets too complex, we can always change to something better as well.
 
Creating responsive websites is either really easy or really hard, depending on how you make the site.

If you have it text-only like http://motherfuckingwebsite.com or somewhat more complex like Wikipedia/MediaWIki, it is always responsive.
Or you use flexboxes (example) or some other frameworks, this works also fairly well. 


If you want to have certain elements at a certain width/height (in px), you'll have a lot of @media and/or need to provide lots of stylesheets. 
 
As long as it performs good, it is no problem if the site looks compared simple. The best looking site is useless when it performs bad. For example, this site: https://robertsspaceindustries.com/ 

Looks great but at least with my Opera 12 it performs horrible bad, not sure why, I'm not a website tech expert. :/  I wish that look is doable without performance issues but I guess that's the usual price you pay if you want a fancy website.
 
The most important responsiveness is IMO how often it gets updated in terms of how fast it is carried out.  Yes it can be dynamic and such, but there is always a need to go in and fix something, thats when complexion isnt the friend of time.
 
If you're stil looking for programmers, i would like to help, too. I'm not very experienced, but i can make CSS layouts, HTML documents and can program in PHP. I'm working at a company, which creates websites and i've recently made a responsive design (my first one).
 
I think we should start with clearing out some questions, with are still out here.

1. Existing CMS / Own CMS

2. Framework Front- / Backend (node.js, js, html, php, bootstrap ....)

3. Who are the Coders / Designers

4. Meetings

5. Some kind of team management / team leader

6. Basic design / layout / functionality

And everything what comes after that:

- Roadmaps

- Deadlines

- Milestones

- Sprints

- ...

IMHO planning ist the key for a good project. So we better clear at least some of these point out, before we even start.

- over and out - 

BTW:

GitHub user

Ponsen
 
Last edited by a moderator:
Hey guys,

Sorry to barge in on this thread.

I keep seeing the current site's specs list elsewhere.  This isn't a problem if people actually pay attention when discussing this stuff, but I see a problem that might come from bad reporting and such.  

Potential future owners are being told that the Pyra will have a 1080p screen.  On the Pyra site this is marked with an asterisk.  I get this, you get this, and if the readers of these other sites are smart they will go to http://www.pyra-handheld.com/specs.html and see this and know it isn't final.  Perhaps to avoid bad info getting spread around that should be changed to 720p, until the new site is up.  It may seem like a petty thing to us, however there may be people who get their hearts set on that and are later let down, or have bad things to say in response to "the change".

I don't want Pyra getting that tinge on her reputation over bad reporting, since Pandora already had to deal with problems, including those related to He Who Shall Not Be Named.
 
On the Pyra site this is marked with an asterisk.  I get this, you get this, and if the readers of these other sites are smart they will go to http://www.pyra-hand....com/specs.html and see this and know it isn't final.  Perhaps to avoid bad info getting spread around that should be changed to 720p, until the new site is up.  It may seem like a petty thing to us, however there may be people who get their hearts set on that and are later let down, or have bad things to say in response to "the change".
Agree, especially on the official site it should be marked as "TBC (undecided between 720p and 1080p at this stage)" 
 
I don't want Pyra getting that tinge on her reputation over bad reporting, since Pandora already had to deal with problems, including those related to He Who Shall Not Be Named.
One more thing on this. It's not just about "website development", it's communication development.

Website is just the "HOW", but "WHAT" to communicate is extremely important.

Personally I couldn't care less about the tech used (php, wordpress, django, etc...) because if the core message is not well structured and crystal clear, it won't matter anyway. 

I really hope that the person in charge of the overall development understands that.
 
Except we need a close tie between what the tech is designed to do, and what we need it to do.

Using canned website-building systems for the wrong kind of website is a perfect recipe for disaster.
 
Back
Top