-
Notifications
You must be signed in to change notification settings - Fork 3
Home
HereSay is a Content Management System, or CMS, with three objectives. Here are HereSay's objectives, in priority order:
- Search Engine Optimization (SEO) - Above all else, HereSay values SEO. The development team for HereSay constantly studies SEO and communicates with industry experts to build-in features that help enforce best practices and avoid common pit-falls.
- End-User Simplicity - Setup is automatic and most tasks in HereSay can be performed by pointing-and-clicking or dragging-and-dropping. HTML can be edited directly, or via the TinyMCE WYSIWYG editor.
- Extensibility - HereSay is built on the popular N2 CMS Framework, though which an infinite number of plug-ins and customizations can be made.
If you need more detail, check out the features list.
Ready to get started building your website in HereSay? Check out the getting started guide.
Version 0.1 is ready! This release contains only the baseline CMS. It is easy to download and get it running, but only contains minimal features. Check back frequently for updates!
- Version 0.1 - Baseline CMS.
- Version 0.2 - NuGet package.
- Version 0.3 - Initial plug-in set (self-rendering).
- Version 0.4 - Initial theme set from oswd.org.
- Version 0.5 - Upgrade management.
- Version 0.6 - Themeable plug-in support.
- Version 0.7 - Initial dashboard support.
- Version 0.8 - QA features: Notifications, link validation.
- Version 0.9 - Google ping support. (Ping-O-Matic?)
- Version 1.0 - Final tweaks & bug fixes; end-user documentation.
Geotagging support - You can already add geo meta tags on the "Advanced" tab of the edit screen. Additional support will probably include: Microformats and GeoRSS.
Pingbacks - Sending and receiving.
Right now we need feedback. Is the system usable? Are the surprises pleasant? Is there something you love or hate about your current CMS? Is there a feature you need for a website, and just can't seem to find an easy solution? Share it with us!
If you'd like to contribute a feature or bug fix - go ahead! Fork the code, write the feature, and create a pull request. We'll review the changes and pull them in based on where the feature falls in the development road-map and how complete (organized, tested, documented) your code is.