[
https://issues.apache.org/jira/browse/JOSHUA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15261475#comment-15261475
]
Matt Post commented on JOSHUA-251:
--
Related to this: after trying to use it a little, I think the current
website-building approach is too much of an impediment to use. Recall that this
process requires maintaining two branches in the repo: one for the source files
(in Markdown format, mostly), and another for the generated website, which then
gets pushed up. When the website was on Github, we just needed the source
branch, because Github runs Jekyll for you.
Another nice feature of Github was you could easily edit the files in a web
browser on the site directly, and that would also trigger an update. It'd be
nice to remove any barriers to documentation, since it's already kind of hard
to get done.
I'm thinking about moving the website over to Joshua's Confluence page. Are
there any drawbacks to this? I'm a little wary of putting the site in a
proprietary CMS, but it seems that Apache is all-in on the software, and it
provides a good user experience.
matt
> Address Website Branding Issues
> ---
>
> Key: JOSHUA-251
> URL: https://issues.apache.org/jira/browse/JOSHUA-251
> Project: Joshua
> Issue Type: Task
>Reporter: Lewis John McGibbney
>Priority: Critical
> Fix For: 6.1
>
>
> We have a number of Website branding issues which we need to address.
> http://www.apache.org/foundation/marks/pmcs.html#introduction
> Lets work through them here. Please create child issues if appropriate.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
