This is finally done:
https://github.com/stephenmcd/mezzanine/commit/73f6d0e39d6c634ce7fab7a38d806592b987ef2d
https://github.com/stephenmcd/mezzanine.jupo.org/commit/0b1e4590070752ba4574bcb0ab97159b72fcd592
Welcome to the more compact README:
https://github.com/stephenmcd/mezzanine
On Sun, May
Thanks Eduardo
That fixes it
Now I have lots of 'unexpected indentation' errors when parsing
README.RST with docutils 0.12
I have had a good Google but this problem remains unsolved. Will return
to this in the morning
Thanks again
g
On 26/05/15 19:47, Eduardo Rivas wrote:
Rename your
Rename your project folder to something without dots in the name. Python
uses dots to indicate file paths.
When naming stuff in Python, use underscores or simply join all the words
together. Avoid dots and dashes as they conflict with the language syntax.
--
You received this message because you
ok thanks
I am feeling a tad foolish because when I run python manage.py createdb
I get the stack trace below
I am in a virtual environment and have made sure that my current
directory is on the path using add2virtualenv
I am supposing that the problem is something trivial but it is eluding
It's just a regular Mezzanine project - there aren't any special
instructions.
On Sun, May 24, 2015 at 3:08 PM, Graham wrote:
> Thanks Brandon
> I will get going with the feedback I have.
> Stephen, could you please give me the instructions on how to install the
> 'project site' on my local dev
Thanks Brandon
I will get going with the feedback I have.
Stephen, could you please give me the instructions on how to install the
'project site' on my local development machine.
I can do the git clone but I am a bit hazy after that.
Thanks
g
On 24/05/15 21:41, Brandon Keith Biggs wrote:
Hello
Hello,
I believe most people who read the readme on github have already seen
the website.
So they would like to know technical stuff and how to get started and do
basic and essential things.
Perhaps a link to Dgango's guide and then instructions on how to get
started and instructions on how to
Hello all...
I am also interested in the 'who' and the 'why' and this may help us
decide what should go in the README...
*Who* are we designing the README for?
*Why* would the reader of the README choose to become involved, what
would 'hook them in'?
*Why* choose Mezzanine over any other 'sim
On Fri, May 22, 2015 at 11:14 PM, Mathias Ettinger <
mathias.ettin...@gmail.com> wrote:
> Why not swap it entirely with doc/overview.rst?
>
I think this will be the general approach - move stuff out of the README,
and directly into the docs, and adding links in the README back to the docs
for the
Why not swap it entirely with doc/overview.rst?
This way, what relies on README.rst today can rely on overview.rst tomorow
without breaking anything. Or is the point to shorten both?
Le vendredi 22 mai 2015 22:32:01 UTC+2, Stephen McDonald a écrit :
>
> It's a good idea.
>
> Please keep in mind
It's a good idea.
Please keep in mind there's some functionality of the project site
dependent on the format of the readme, particularly those lists we'll
probably remove:
https://github.com/stephenmcd/mezzanine.jupo.org/blob/master/demo/__init__.py
On Fri, May 22, 2015 at 1:26 PM, Geo wrote:
+1
Mezzanine's Readme is, at the time of writing, 795 lines long - pretty much
an essay! The GH Readme for Django itself is short and sweet at just 44
lines. That's a massive 94% reduction in lines.
If you are looking for a python CMS to use, you want to read about 3 key
features of Mezzanin
12 matches
Mail list logo
