Skip to content
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.

Guidance and advice, if possible, please... #657

Open
graham2 opened this issue Mar 6, 2018 · 1 comment
Open

Guidance and advice, if possible, please... #657

graham2 opened this issue Mar 6, 2018 · 1 comment
Labels

Comments

@graham2
Copy link

graham2 commented Mar 6, 2018

Hi Bruno,
This seems the simplest way to send you a message - so -
I did say a few months ago that I was interested and could probably contribute and now that time has arrived. However while I have done plenty of coding (since the 70s) I've only just moved to Python. Having said that the first project (a Pyside application) does seem to work; I also had a look at Flask some months ago, so it's not completely new.
I have forked quokka and had a quick look at the code so my real request is, apart from asking if there is any program design documentation, is which 'issues' would be a reasonable place to start ? If you could offer some suggestions that would be relatively small and offer a good introduction to the code.

graham

@rochacbruno
Copy link
Collaborator

Hi @graham2

Nice to hear you are willing to contribute!

  1. Install the project locally

You may face some missing dependencies, if so, please comment for us to document, we already know that python3-dev is needed if you are on Ubuntu Linux.

git clone https://github.com/rochacbruno/quokka
cd quokka
python3 -m venv venv
. venv/bin/activate
make install
make adduser
make devserver

Then access http://localhost:5000 and http://localhost:5000/admin

With the project running you can start posting new articles and pages and exploring the admin UI and also the front-end theme, also you can hack the quokka/project_template/quokka.yml and play with different options there to see the result, for example, you can change the theme:ACTIVE for one of those in the themes folder (bootstrap3, malt, etc..) and then report new issues if you find some.

  1. Report issues you may find
  2. By exploring the CMS you can add some kind of documentation, how to install, how to create an article, how to change the theme, how to enable/disable the debug toolbar etc...

Then I think you will be able to pick some of the opened issues to implement.

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

No branches or pull requests

2 participants