Copying basic template/css files over as a starting point

[ragnarokatz]

I would like to get this project started by doing the following:

• copy the existing template/css files (just the simple one from the basic folder) from zenit and paste it into this repo
• activate github pages for this repo
• check it out at the github page

If people are okay with this, I can get it going by tomorrow (provided that I have sufficient privilege to activate github pages)

[humphd]

I love the idea of pulling the existing template/css from zenit and using it as a starting point. CC @ctyler, who has access to these files and could maybe help us access them?

I'm not sure if people will want to use gh-pages for deploy or not. I'd split this issue up into at least two parts, since doing an MVP with static HTML could well be another bug.

[ragnarokatz]

Hello, renamed the title of this issue appropriately to reflect the above recommendations.

[ragnarokatz]

reference PR #9

[ragnarokatz]

I did some reverse-engineering/hacking.

• did view-source on the current planet page here, cleaned it up, and replace texts with lorem ipsum
• stole the css from here
• managed to get the pictures here

[Reza-Rajabi]

Doesn't that lead us to make the same front-end? Maybe it is fine to stick on old stuff (nostalgia), though.

[ODAVING]

My thoughts exactly! I mean if it hasn't been updated since early 2000s maybe we should modernize it xD

…

On Thu, Oct 31, 2019 at 12:05 AM rare ***@***.***> wrote: Doesn't that lead us to make the same front-end? Maybe it is fine to stick on old stuff (nostalgia), though. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AFTFEL6GR4FE7Q7VVUCSKDDQRJKRLA5CNFSM4JGS5SV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWP6SY#issuecomment-548208459>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFTFELZKNDZWCZXYAJIQST3QRJKRLANCNFSM4JGS5SVQ> .

[ragnarokatz]

this is just a starting point, by no means it is what we are looking for or the end product itself.

this particular issue serves the following 2 purposes:

1. Just get going. this is to give people somewhere to start on, and get the project going. It's hard to get things going when all the talks are in the air without something solid to reference against. Once there's some basic materials in the repo, people can start filing very specific issues. such as:

• this icon needs to be changed
• this thingy's position is not right
• this page doesn't display correctly on mobile
  to something entirely even bigger:
• the whole layout need to be changed
• we want to replace it with react/angular/vue whatever

2. Capture existing requirements. before we incorporate any new functionalities, we need to analyse the current state and make sure all those requirements are gathered first. through looking at this prototype, I can deduct a few at least:

• posts are grouped by dates (day-group tag in html)
• posts within the same day grouped by user channels (channel-group tag in html)
• which means if a user has posted 2 entries in one day, they show up consecutively under one name. Their names does not appear twice in one day.
• however, if a user posts 2 different blog posts on 2 different days, their names will show up twice. once under each day.

now, whether we want to keep the existing requirements or modify them, that's another story. But, in the current state, this is how things are being done at the moment.